[Bug 510403] Re: Filesystem with last mount time in the 'future' halts boot with little help for user

[Sam Liddicott]

I'm having a similar problem on O2 Joggler hardware which does not have
a hardware clock, and so the clock is ALWAYS wrong until after the
network comes up and NTP can work.

Ubuntu Netbook Remix Lucid Beta 2 goes in an inifinite loop from
mountall of trying to fsck the driver but failing with exit code 4.

I can edit /etc/init/mountall.conf to make it fsck first (hard wired) by
why - there is nothing wrong with the disk, I don't want all the delay
of fsck, I just want the e2fsck tools to realise that the superblock
time being in the future doesn't always indicate something about the
file system but often something about the hwclock, or lack of.

-- 
Filesystem with last mount time in the 'future' halts boot with little help for user
https://bugs.launchpad.net/bugs/510403
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to util-linux in ubuntu.