using 16.04, it kept running fsck on boot-up. So I tried to find where all the fsck logs might be. Another askUbuntu thread suggested /var/log/upstart/mountall.log

But when I looked in /var/log/upstart/ there was no log files, only compressed files. It seems to be the case for all other types of log files in there. Even the compressed files only few bytes in size and can not be opened.

There seems to be a bug which covers this


Is there any way to get it to write to log

  • I upgraded from 14.04 LTS, the syslog file is empty nothing there. does systemd log files, does it handle fsck logs
    – pt123
    Mar 22, 2017 at 22:11
  • that link has no info on where the log file is or how to access it
    – pt123
    Mar 22, 2017 at 22:20
  • See my answer. :-)
    – Elder Geek
    Mar 22, 2017 at 22:47
  • Please open your tune2fs question as a new question as it's more likely to help others as a new question than tagged to the end of this already answered question. In this way we can be more efficient and help as many people as possible. For this reason I'm rolling back this question to what it was when it was answered. Thank you understanding.
    – Elder Geek
    Mar 23, 2017 at 1:44

1 Answer 1


16.04 doesn't use upstart anymore by default so unless you've done something clever, you are using systemd and you are likely looking at files left over from a previous version due to an upgrade rather than clean install.

If fsck has run recently on a non-root partition on yourr system you can confirm this by running grep fsck /var/log/syslog

Which in my case results in:

Mar 22 15:06:27 64bitUbuntu systemd-fsck[750]: /dev/sdb1: clean, 146223/121454592 files, 356711795/485818368 blocks

In 16.04 You can find what you seek in the file /var/log/boot.log

Here's an example from my 16.04 system created at last boot:

The boot fsck results are stored in var/log/boot.log

ll /var/log/boot.log
-rw-r--r-- 1 root root 96 Mar 22 15:06 /var/log/boot.log

Scanning for Btrfs filesystems
/dev/sda2: clean, 349091/1954064 files, 2379983/7814912 blocks


https://www.freedesktop.org/software/systemd/man/[email protected]

ls /var/log

  • Out of curiosity, do you see the same using journalctl -u systemd-fsckd? Mar 22, 2017 at 23:29
  • syslog is empty, bootl.log doesn't have the results of the fsck just only /dev/sda1: clean, 313673/673296 files, 2020820/2687988 blocks, checking tunefs it's not updating the last checked date
    – pt123
    Mar 22, 2017 at 23:35
  • @steeldriver that command reports when the file system check daemon was started, so no.
    – Elder Geek
    Mar 23, 2017 at 1:40

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .