Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I see that there are some other threads that mention this error, but I have tried the solutions with no luck.

When I log into my 12.04 Server, I get the message:

/dev/sdb1 will be checked for errors at next reboot
/dev/sdc1 will be checked for errors at next reboot

The problem is that the check is never done and I continue to get the messages. I ran a fsck on both drives and they are fine.

share|improve this question
I just rebooted again and didn't get the warning... –  dpbklyn Jul 13 '12 at 14:46
I tried a suggestion to do touch /forcefsck and reboot, but I'm still getting this warning. –  pcm Sep 5 '12 at 20:40
See if this helps you: askubuntu.com/questions/60249/… –  Takkat Feb 5 '13 at 7:30
The message in the message of the day (motd) about drives being checked doesn't go away even when the drives have been checked. This is a known bug in Ubuntu. This is caused because that message is cached in the file /var/lib/update-notifier/fsck-at-reboot so that it is not constantly recomputed. /usr/lib/update-notifier/update-motd-fsck-at-reboot checks the timestamp on the file and is supposed to regenerate it every so often. However, there is a bug and the timestamp gets set in such a way that it never regenerate –  Stephen Ostermiller Apr 20 '13 at 10:12
I have a similar warning on Ubuntu 14.04.1: *** /dev/xvda1 should be checked for errors *** No bad blocks. Log shows everything OK. Is this the same bug? –  plamtrue Jan 19 at 21:40

4 Answers 4

up vote 31 down vote accepted

This is a known bug in Ubuntu 11.04 and apparently still exists in 12.04 LTS. What happens is what you described: you keep getting the notification even though there is nothing wrong with your hard drive and no checks are scheduled/will be done.

It's caused by the /usr/lib/update-notifier/update-motd-fsck-at-reboot script generating a /var/lib/update-notifier/fsck-at-reboot file with a timestamp in the future. The previous link has a convoluted solution from one of the Ubuntu maintainers (Steve Langasek), but it may be simplest to just do this:

  1. Open a terminal with Ctrl-Alt-T
  2. Type:

    sudo rm /var/lib/update-notifier/fsck-at-reboot
  3. Exit the terminal and reboot (or logout/login).
share|improve this answer
In my case editing the file and removing the text resolved the problem. When I tried removed it at next login it would simply recreate the file so it the problem would persist. –  Savas Vedova Feb 14 '14 at 10:54
Here a command that will fix the problem without any sort of reboot or logout: sudo bash -c 'rm /var/lib/update-notifier/fsck-at-reboot && for file in /etc/update-motd.d/*; do $file; done > /var/run/motd' && cat /etc/motd –  Stephen Ostermiller May 9 '14 at 19:24
cat /dev/null > /var/lib/update-notifier/fsck-at-reboot

Fixed this for me....

Ubuntu 12.04.2 LTS.

3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24 20:18:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
share|improve this answer
Yeah, when I did rm fsck-at-reboot, it was recreated when I logged in again. So I had to edit fsck-at-reboot to delete the message. (This was for an AWS EC2 Ubuntu 13 machine) –  wisbucky Oct 21 '13 at 23:46
Same here, editing it instead of removing resolved the problem. Thanks. –  Savas Vedova Feb 14 '14 at 10:52

I had this same problem today - turned out in my /etc/fstab file, the line that had the relevant filesystem, had "0" in the last field, which means don't fsck it on boot. This should have been "1" for the root filesystem, or "2" for any other filesystem.

Also, my motd wasn't updated after the (successful) fsck. You can use this command:

tune2fs -l /dev/something

Then look for a line that says "Last Checked".

share|improve this answer
This is quite helpful. –  octopusgrabbus Feb 7 '13 at 16:41
I'm not sure you need to change fstab. I think this is managed elsewhere. –  beruic Feb 13 '13 at 23:52

This message is NOT a problem. It is an informational message, so you know that next time you reboot your system, Ubuntu will run checks on the filesystem, that's all.

What are the implications?

  1. Checking the filesystem may take a very long time if the partition is very large. For example if the partition is several terabytes, expect a very slow boot next time.

  2. If you are aware of hardware issues of your disk, you may have problems on the next boot if the filesystem check fails. In this case you may want to backup your important files before the next reboot.

If you have no particular concerns and you don't care that your next boot will be slower than usual, you can ignore the message.

Ubuntu does this filesystem check periodically, apparently every 30 restarts, according to the answer posted in a comment. Why does Ubuntu ask to check my hard drives every so often?

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.