I am also getting this on my karmic upgrade from jaunty. I am running
with UTC=yes in my rcS. The problem in my case seems to arise from the
fact that the init scripts do not restore the system clock from the
hardware clock before launching into fsck.
I had to put the following into my /etc/init/mountall.conf
pre-start script
/sbin/hwclock -s
end script
However, that is a kludge, as mountall should really depend on getting
the hwclock read and the system clock updated through the regular
hwclock.sh script
--
fsck halts bootup when checked file has timestamp in the future from other
Ubuntu installation
https://bugs.launchpad.net/bugs/422869
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
