From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-user+bounces-103079-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1N5qD3-0004WZ-IL
	for garchives@archives.gentoo.org; Thu, 05 Nov 2009 00:28:17 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 0AEB8E0B1E;
	Thu,  5 Nov 2009 00:28:16 +0000 (UTC)
Received: from vms173017pub.verizon.net (vms173017pub.verizon.net [206.46.173.17])
	by pigeon.gentoo.org (Postfix) with ESMTP id D94A6E0B1E
	for <gentoo-user@lists.gentoo.org>; Thu,  5 Nov 2009 00:28:15 +0000 (UTC)
Received: from [192.168.1.2] ([71.178.24.39]) by vms173017.mailsrvcs.net
 (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit))
 with ESMTPA id <0KSM00F3Z1AM5ES8@vms173017.mailsrvcs.net> for
 gentoo-user@lists.gentoo.org; Wed, 04 Nov 2009 18:27:59 -0600 (CST)
Message-id: <4AF21C11.5030702@verizon.net>
Date: Wed, 04 Nov 2009 19:28:01 -0500
From: Chris Reffett <mellitussum@verizon.net>
User-Agent: Thunderbird 2.0.0.23 (X11/20091101)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-version: 1.0
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: fsck date problem during boot
References: <871vkethtc.fsf@newsguy.com>
 <3530633A-B2B8-4A81-A565-83EB65CE85A9@stellar.eclipse.co.uk>
 <87bpji2ksc.fsf@newsguy.com> <4AF21A49.5080409@gmail.com>
In-reply-to: <4AF21A49.5080409@gmail.com>
X-Enigmail-Version: 0.96.0
OpenPGP: id=42618354;
	url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x42618354
Content-type: multipart/alternative;
 boundary=------------000303000708000309000707
X-Archives-Salt: cc1889bc-0e1d-4885-83ae-55060dd5eb2c
X-Archives-Hash: a8f188473a3743de9e9b69a6d48f2ec2

This is a multi-part message in MIME format.
--------------000303000708000309000707
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Dale wrote:
> Harry Putnam wrote:
>   
>> Stroller <stroller@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 +/-.
>>
>>   
>>     
>
> 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.

--------------000303000708000309000707
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Dale wrote:
<blockquote cite="mid:4AF21A49.5080409@gmail.com" type="cite">
  <pre wrap="">Harry Putnam wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Stroller <a class="moz-txt-link-rfc2396E" href="mailto:stroller@stellar.eclipse.co.uk">&lt;stroller@stellar.eclipse.co.uk&gt;</a> writes:

  
    </pre>
    <blockquote type="cite">
      <pre wrap="">On 4 Nov 2009, at 15:45, Harry Putnam wrote:
    
      </pre>
      <blockquote type="cite">
        <pre wrap="">...
Somehow the date of last fsck on /boot is seen as `in the future' so
fsck fails on /dev/had1 (/boot).
      
        </pre>
      </blockquote>
      <pre wrap="">The first thing I would want to check is the motherboard battery. Is
the time correct if you reboot and immediately enter BIOS?
    
      </pre>
    </blockquote>
    <pre wrap="">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&lt;y&gt;? 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&lt;y&gt;? 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 +/-.

  
    </pre>
  </blockquote>
  <pre wrap=""><!---->
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

:-)  :-) 


  </pre>
</blockquote>
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.<br>
</body>
</html>

--------------000303000708000309000707--