Now that I think about it, I don't think fsck package is the problem.
mountall is.
If you issue a 'sudo touch /forcefsck', after it fails to complete, your
left with forcefsck file still intact.
Its mountall duty to remove it. It can't because it doesn't finish.
====
mountall.conf:
exec mountall --daemon $force_fsck $fsck_fix
end script
post-stop script
rm -f /forcefsck 2>dev/null || true <<never gets here. <<< It needs to get
here.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
