[Bug 1574707] Re: / and /usr not fscked during boot

[Martin Pitt]

Can you please attach your /etc/fstab? Or at least check yourself that
the last number in the / and /usr entries is greater than "0"? (if it's
zero, then fsck is disabled).

If it is greater than "0", please boot with "debug" on the linux kernel
command line, and then attach  /run/initramfs/initramfs.debug and give
me the output of "cat /run/initramfs/fsck.log" and "ls -l
/run/initramfs/". Thanks!

** Summary changed:

- update-motd-fsck-at-reboot notify checked for errors at next reboot even after reboot
+ / and /usr not fscked during boot

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

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

Title:
  / and /usr not fscked during boot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I had the following message on Ubuntu 15.10
  *** /dev/sda10 will be checked for errors at next reboot ***
  *** /dev/sda1 will be checked for errors at next reboot ***

  This was displayed even after rboot.

  I pgrade to 16.04 and still the same problem.

  
  I took a look at the /usr/lib/update-notifier/update-motd-fsck-at-reboot and for /dev/sda10, I had something like this :
  Mount count	28
  Maximum mount count	30
  Check interval	15552000
  Next check after	Tue Jan 12 23:11:26 2016

  The message was not displayed anymore after 2 reboot, in order to
  reach Mount count to 30, and greater or equals to Maximum mount count.

  It seems that the file check was not until the Mount count >= Maximum
  mount count


  More over, on the platform, I have two partitions with following "name" :
  /dev/sda1
  /dev/sda10

  When the first one is verified by the script, the command "mount | grep "^$part" | cut -d ' ' -f 3" does not give te right result.
  mount | grep "^/dev/sda10" | cut -d ' ' -f 3 give result :
  /

  But 
  mount | grep "^/dev/sda1" | cut -d ' ' -f 3
  /
  /usr

  
  May be not a big deal, because, the mount point is only used to find value in the file /etc/fstab, in order to specialize the message, but many be there is an error anywhere else.

  Regards

  Etienne

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