You have been subscribed to a public bug:

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

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

-- 
update-motd-fsck-at-reboot notify checked for errors at next reboot even after 
reboot
https://bugs.launchpad.net/bugs/1574707
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to systemd in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to