On 11/04/2009 10:43 AM, Harry Putnam wrote: > Stroller <strol...@stellar.eclipse.co.uk> writes: > >> On 4 Nov 2009, at 15:45, Harry Putnam wrote: >>> ... >>> Somehow the date of last fsck on /boot is seen as `in the future' so >>> fsck fails on /dev/had1 (/boot). >> >> The first thing I would want to check is the motherboard battery. Is >> the time correct if you reboot and immediately enter BIOS? > > That was a pretty good help but apparently not all the story. > > When I checked bios, the clock was exactly 1 hr fast (didn't pick up > the end of daylight saving time I guess). > > Reset the clock and tested with 2 more reboots, each time mounting > /boot and fiddling around with files. > > Each time the same failure occurs. I check bios time again. Its > right. > > Here is the (edited) output form fsck > > Superblock last mount time (Wed Nov 4 18:05:13 2009, > now = Wed Nov 4 12:11:49 2009) is in the future. > Fix<y>? yes > > [...] > ------- --------- ---=--- --------- -------- > Superblock last mount time (Wed Nov 4 18:14:54 2009, > now = Wed Nov 4 12:18:01 2009) is in the future. > Fix<y>? yes > > [...] > > so still somehow, those last mount dates are way wrong. > > I hope I'm checking the right thing in bios. Its under cmos and shows > the time ticking away. You can adjust all columns. with +/-.
Is your bios clock set to UTC, and do you have /etc/localtime pointing to your correct timezone? e.g. /etc/localtime -> /usr/share/zoneinfo/PST8PDT. If all that is correct, then I'm guessing the problem will fix itself if you just wait an hour :o)
