Re: [gentoo-user] Re: fsck date problem during boot
On Wed, Nov 04, 2009 at 06:20:25PM -0600, Dale wrote: > I can't recall exactly how I did this but there is a command to tell the > OS to set the clock on the mobo to the system time when shutting down. > That way everything should sync up when you reboot, except for that tiny > little bit if you shutdown completely for a few days or something. The > command is hwclock. I can't recall where I put the thing because I am > logged into KDE 4 and I can't find nothing in here yet. It's pretty but > it is different so I'm lost. > > I *think* I put it in the rc file or something. I remember the file is > run during shutdown tho. That may help if you know which file that is. I believe you are talking about the 'clock_systohc' setting in '/etc/conf.d/hwclock'. If none of these things help, you could always try disabling time-based forced checks using tune2fs's option '-i 0d'. You can read the man page for how to do it. Sincerely, Daniel Solano Gómez pgpbK1CzP1ptd.pgp Description: PGP signature
Re: [gentoo-user] Re: fsck date problem during boot
Dale wrote: > Harry Putnam wrote: > >> Stroller 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? 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? 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 +/-. >> >> >> > > I can't recall exactly how I did this but there is a command to tell the > OS to set the clock on the mobo to the system time when shutting down. > That way everything should sync up when you reboot, except for that tiny > little bit if you shutdown completely for a few days or something. The > command is hwclock. I can't recall where I put the thing because I am > logged into KDE 4 and I can't find nothing in here yet. It's pretty but > it is different so I'm lost. > > I *think* I put it in the rc file or something. I remember the file is > run during shutdown tho. That may help if you know which file that is. > > Hope that helps. > > Dale > > :-) :-) > > > It's in /etc/conf.d/clock (or /etc/conf.d/hwclock for baselayout 2/openrc), and it's called CLOCK_SYSTOHC. Set it to yes to write the system time to hardware on shutdown.
Re: [gentoo-user] Re: fsck date problem during boot
Harry Putnam wrote: > Stroller 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? 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? 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 +/-. > > I can't recall exactly how I did this but there is a command to tell the OS to set the clock on the mobo to the system time when shutting down. That way everything should sync up when you reboot, except for that tiny little bit if you shutdown completely for a few days or something. The command is hwclock. I can't recall where I put the thing because I am logged into KDE 4 and I can't find nothing in here yet. It's pretty but it is different so I'm lost. I *think* I put it in the rc file or something. I remember the file is run during shutdown tho. That may help if you know which file that is. Hope that helps. Dale :-) :-)
[gentoo-user] Re: fsck date problem during boot
On 11/04/2009 10:43 AM, Harry Putnam wrote: > Stroller 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? 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? 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)
[gentoo-user] Re: fsck date problem during boot
Stroller 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? 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? 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 +/-.
