Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When working remotely I set a server to force an fsck at boot time with the sudo touch /forcefsck command and rebooted.

After it restarted I checked in /var/log/fsck for the results of the disk check.
Both checkfs and checkroot said: Nothing has been logged yet

So where is it saving the results?

share|improve this question
Having the same problem on Ubuntu 12.04 LTS. I found the fsck log in /var/log/boot.log. – user143312 Mar 25 '13 at 16:01
up vote 14 down vote accepted

Possibly you are affected by this bug: "Does not log fsck invocations in /var/log/fsck/"

share|improve this answer
Most likely. Shouldn't be surprised anymore that it's probably not going to be addressed... – Bart Silverstrim May 22 '12 at 15:33
This affects us in a very negative manner as well - we're on EC2 and when servers reboot we need details of things like this. How can this possibly be considered a 'wishlist' item? This is core functionality, and it's broken. – tamale Nov 13 '13 at 15:11
@tamale You're fully right. I got hit by this too. My / partition had a nasty quirk, and when entering recovery mode, it forced an e2fsck on it. This is perfect, but as it's really hard to remember which files to replace from backup, one must be able to track down the file names reportedly corrupt. – syntaxerror Aug 12 '15 at 20:48

For Ubuntu 14.xx:

I found some fsck logs in /var/log/upstart/mountall.log.

share|improve this answer
Welcome to Ask Ubuntu. ;-) There used to be a bug in 11.10 at the time, so your answer on a new system right now doesn't add any value to this 3 year old question. For the future: look at a question's date and whether there already is an answer. ;-) – Fabby Mar 30 '15 at 9:56
@Fabby but for future visitors it still might be useful, I think? The version is given (@Shay do you mean 14.04 or 14.10?) and therefore I would say it is a valid answer, although it might not help the OP (who found a solution 3 years ago...) – Byte Commander Mar 30 '15 at 15:00
I've added a tag to help search engines show this as an old question. – NGRhodes Mar 30 '15 at 15:18
Absolutely right! :-) That's why I just left a comment. For the record: I didn't down-vote! ;-) – Fabby Mar 31 '15 at 7:38
@Byte Commander This supposedly "old" question helped me a LOT indeed! I would never have guessed that fsck logs would be hidden away in /var/log/upstart/mountall.log resp. /var/log/upstart/mountall.*.log.gz. Fairly illogical. HOWEVER, it seems that the file names reported to be corrupt were not logged, just their inodes. – syntaxerror Aug 12 '15 at 20:52

Testing this with Ubuntu 12.04.5 LTS and I found the log on /var/log/boot.log

└❯ grep -A 1 fsck /var/log/*
/var/log/boot.log:fsck from util-linux 2.20.1
/var/log/boot.log-/dev/vda1: 209262/2621440 files (0.1% non-contiguous), 3239494/10485504 blocks
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.