Public bug reported:
Updated my homserver from 14.04 to 16.04. Got a "/dev/sda1 will be
fscked on next reboot" hint in the MOTD. Did some reboots and the fsck
never happend. Tried with "sudo touch /forcefsck" but the message didnt
go away. Thought it was an error of the MOTD scripts and tried to fiddle
with them. But it reappeard ever time.
Looked at the syslogs logs and saw the fsck never happend.
Looked at the output from dumpe2fs and it showed several interesting
informations:
* the mount count was 12 and the maximum mountcount of 34 was not reached
* the timed fsck date was reached
* the last fsck was long ago (next confirmation the /forcefsck didnt work at
all)
i changed the mount count to 35 with "sudo tune2fs -C 35 /dev/sda1"
which made the fsck on next reboot.
So what works:
* mount count fsck on reboot
what doesnt work:
* setting /forcefsck manually
* timed fsck
what should work?
* all 3 of them should work.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608880
Title:
systemd doesnt work with timed fsck, only with counted mount fsck
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1608880/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
