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

[Etienne JOUVIN]

The /etc/fstab content.

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda10 during installation
UUID=4b116dd4-8bae-475f-9bf1-8344e5844a08 /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda6 during installation
UUID=4fee39df-8166-4af3-8036-8bf48c59ddc7 /boot           ext4    defaults        0       2
# /opt was on /dev/sda8 during installation
UUID=b11ca971-924e-45a0-9be9-59ce1efdc8ec /opt            ext4    defaults        0       2
# /srv was on /dev/sda5 during installation
UUID=96d9be39-cc11-46f0-bf43-f451ff0eb9fc /srv            ext4    defaults        0       2
# /tmp was on /dev/sda7 during installation
UUID=ff94cff0-2e8e-449f-9473-da7caa63a93f /tmp            ext4    defaults        0       2
# /usr was on /dev/sda1 during installation
UUID=8f557a3a-c4c8-4166-8e71-dd7451969a56 /usr            ext4    defaults        0       2
# /var was on /dev/sda2 during installation
UUID=de58b6c5-2e6f-4efe-8e09-6554d2457cf4 /var            ext4    defaults        0       2
# swap was on /dev/sda9 during installation
UUID=c86bebd8-c323-4f24-86e2-6a530e185595 none            swap    sw              0       0


For the debug starting mode, unfortunately, the message is no more displayed because I did reboot many time and the maximum mount count was reached. Then the scan was done.

Now, I do not have anymore the message. But I submit my first message because I touch two case :
* Scan was only done when the max mount count was reached. And I saw that only for partitions /sda1 and /sda10
* Find something wird about the command "mount | grep "^$part" | cut -d ' ' -f 3" in the /usr/lib/update-notifier/update-motd-fsck-at-reboot script, and this is the reason why I submitted it to update-notifier first

Regards

-- 
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