[Bug 1797282] [NEW] fsck not running at all on reboot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD
that says:

*** /dev/xvda1 should be checked for errors ***

I added "fsck.mode=force" to GRUB_CMDLINE_LINUX_DEFAULT in
/etc/default/grub before running 'sudo update-grub'. I also verified
that fsck was present in /boot/grub/grub.cfg afterwards, before
rebooting the server.

Surprisingly I was met with the same error message in MOTD when logging
in. I then ran tune2fs to see when the last check was performed and this
is the output:

$ sudo tune2fs -l /dev/xvda1  | grep checked
Last checked:             Wed Sep 12 16:17:00 2018

I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1,
but after another reboot I was still met with the same error message and
the timestamp for last checked was unchanged.

I have the same problem on all the servers that was upgraded from 16.04
to 18.04, but also on a new server installed directly with 18.04.

In should be mentioned that the servers are AWS EC2 instances, so I have
no way of trying to run fsck from a liveusb.

Another user has reported the same issue here:
https://ubuntuforums.org/showthread.php?t=2403368

I'm not quite sure what information is needed, but attached are some
basic information about the system.

Please let me know if you need any any other outputs or logs.

Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1 LTS
(Xubuntu) and it works fine. Seems to be related to the server edition.

** Affects: e2fsprogs (Ubuntu)
     Importance: Undecided
         Status: New

-- 
fsck not running at all on reboot
https://bugs.launchpad.net/bugs/1797282
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to e2fsprogs in Ubuntu.