It seems like there are two main issues here. First, what is getting
the dates wrong so that fsck reports the inconsistency on the
filesystem. It sounds like that is covered in one of the other bugs
referenced.
Second problem, is why is mountall just jamming up and not dropping back
to a shell to allow manual fscks. I have defeintely seen this
behaviour. For some reason when I hit the timestamp inconsistency on /
and /boot, mountall died on the failing fsck and prompted for a root
shell. However on another (custom) mount from fstab, it seemed like it
jammed up mountall's fsck queue. mountall kept running, did not drop to
a shell, but never attempted to fsck anything after the thing which
failed - including /home.
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432070
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
