On Sat December 17 2005 07:50 pm, Theodore Ts'o wrote: > On Sat, Dec 17, 2005 at 07:45:42PM -0500, Theodore Ts'o wrote: > > Sigh, I see what's going on. Unfortunately S22hwclockfirst.sh gets > > done *after* S10checkroot. So the system time is still incorrect when > > we check the root filesystem; it doesn't get adjusted to account for > > the fact that you're using a non-GMT time until afterwards. I run > > with my hardware clock set to UTC, so I didn't notice this problem. > > > > Could you try renaming /etc/rcS.d/S22hwclockfirst.sh to > > /etc/rcS.d/S09hwclockfirst.sh and see if this addresses your problem? > > Oops, I just realized, this won't work if /usr is a separately mounted > filesystem, since /etc/localtime is a typically a symlink to > /usr/share/zoneinfo/<timezome>, and at the time when the root > filesystem is checked, any other filesystems (such as possibly /usr) > won't be mounted yet.
Actually, I don't have /usr as a separate partition. I just have two partitions, one for / and one for /home. So I tried your suggestion. Interestingly, I had two symlinks to two different scripts in /etc/rcS.d which did the same thing. One was S22hwclock.sh and the other was S18hwclockfirst.sh. They were exactly the same scripts. So, I removed the symlink, S22hwclock.sh (as well as the script hwclock.sh in /etc/init.d). I then changed the S18hwclockfirst.sh symlink to S09hwclockfirst.sh. I then booted into Windows and then booted back into Debian Sid. Previously, doing so would trigger the Superblock error on bootup. However, this time, no error was triggered. Bootup went smoothly. So, this workaround was perfect for me. However, it would seem that a more general fix is necessary for others. I imagine this would mean having to change the boot setup for Debian. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
