A kludgey fix is to have in /etc/e2fsck.conf something like: [options] buggy_init_scripts = 1
The trigger for this seems to be an incomplete/faulty restore of the syetm time from the hardware clock before running the fsck -a. To the best I can see, hwclock is not being set/corrected at all before fsck (and it should be). As for the loopey effect, one possible theory is upstart attempting to bring up a whole bunch of stuff, each of those in turn have a dep chain (of various lengths) to mountall, so mountall keeps being attempted umpteen times, each time failing. -- mountall loops indefinitely on fsck failure https://bugs.launchpad.net/bugs/430713 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
