Hello,
some additional information as far as I could gather.
I put some echo lines into hwclockfirst.sh so I could see that
hwclockfirst.sh is called *before* the fsck complains and seems to work
properly: Because /dev/.udev exists no actual call to hwclock is made in
the script, anyway.
Okay, trying to give more details, but unfortunately, there's no log file from
the failed boot attemps since the root partition is mounted readonly, and I
don't know what to look for. I'm giving it a try, tell me if there's anything
specific I should look for.
hwclock --localtime yields the
Hello,
unfortunately, I am experiencing the same behaviour with my laptop. On
my differently configured desktop computer there is no such problem,
which I tend to blame to the different UTC setting. Hopefully, the
following information on the two systems will help.
Best regards, Alexander.
Hi,
I have the same problem here since my last upgrade on september the 1st
(squeeze AMD64) : util-linux 2.16-3.
I can't boot my system : fsck is always complaining about a last mount time
in the future (+2hours), a manual fsck and reboot do not solve the problem,
last mount time is always
4 matches
Mail list logo
