Greg Wallace wrote: > Here's all of the lines from the start-up log beginning right before the > fsck and ending with the mount of the file system. > > Waiting for device /dev/hda2 to appear: OK > fsck 1.39 (29-May-2006) > [/bin/fsck/ext3 (1) -- /] fsck.ext3 -a -CO /dev/hda2 > / (/dev/hda2): Superblock last write time is in the future. FIXED > / (/dev/hda2) clean, 34... files, 89... blocks > fsck succeeded. Mounting root device read write > Mounting root /dev/hda2 > > I don't understand the part about last write time being in the future. > Every time I boot I get that same message. When I booted from the DVD and > ran e2fsck I also got it. I followed with another e2fsck right afterward > just to see if it went away and it did. But, when I booted again normally > it showed right back up again. Do you think that's what's causing the fsck? > Yes, definitely. So to recap, you do not have a fsck problem, you have a time problem causing it to update the superblock (my guess is the writing of the dirty bit) with the wrong date, which causes it to fail the initial fsck and causing it to run to fix that problem. When you shutdown, it updates the hardware clock from the system clock (probably not the problem) and should mark the filesystem as cleanly shutdown. Something is writing the wrong date. Since you had a syslog-ng.conf.rpmnew file, is it possible there are other config files you have not updated since this was obviously an update install?
-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
