[Bug 1797282] Re: fsck not running at all on reboot

[Theodore Ts'o]

This is probably not assigned to the right package.   It's not an issue
with e2fsprogs, but whatever component is running fsck.   This might be
systemd, or upstart, or whatever the heck Ubuntu is using these days.
I lost track a while ago.  :-)

I can tell, you as the Debian maintainer of e2fsprogs, that fsck runs
*just* *fine* on Debian testing.   With Debian, using systemd (which is
the default), the systemd units which run fsck are generated by the
systemd-fstab-generator program which is part of systemd.

So the main issue is whether anyone on the Canonical/Ubuntu team is
paying attention.   I pay attention in case people report e2fsprogs
bugs, but this is not an e2fsprogs issue.   And I don't use Ubuntu so I
can't really help.

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

Title:
  fsck not running at all on reboot

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1797282/+subscriptions