On Wed, Feb 4, 2009 at 5:46 PM, Mark Knecht <[email protected]> wrote:
> On Wed, Feb 4, 2009 at 3:00 PM, Paul Hartman
> <[email protected]> wrote:
>> On Wed, Feb 4, 2009 at 4:51 PM, Mark Knecht <[email protected]> wrote:
>>> On Wed, Feb 4, 2009 at 2:09 PM, Paul Hartman
>>> <[email protected]> wrote:
>>>> On Wed, Feb 4, 2009 at 12:05 PM, Mark Knecht <[email protected]> wrote:
>>>>> Recently my AMD64 machine has started displaying this message at boot
>>>>> time. I don't know exactly when it started but I suspect it was when I
>>>>> started testing a new kernel that didn't have the RTC enabled when I
>>>>> was first testing it.
>>>>>
>>>>> Anyway, what's the process of fixing this. It says it's 'fixed' at
>>>>> boot time but booting again does the same thing. I've got
>>>>> e2fsprogs/e2fsck but I'm not sure if it can be used on a mounted drive
>>>>> and I figured it best to ask first.
>>>>
>>>> check /etc/conf.d/hwclock and see if clock_systohc="YES" or "NO".
>>>>
>>>> I think default is NO, so your computer loses track of time until NTP
>>>> syncs over net again.
>>>
>>> I think it's /etc/conf.d/clock and mine has
>>>
>>> CLOCK_SYSTOHC="yes"
>>>
>>> Again, this is a relatively recent problem. Maybe a month ago it was
>>> fine, and then somewhere along the way it changed.
>>>
>>> I'm currently executing a 'shutdown -F -r now' command. It found the
>>> problem on the first partition, fixed it, rebooted, and that sector
>>> seems fixed. It's now working on the second sector. I'll have to see
>>> if that fixes all of them, and whether they stay fixed after a
>>> powerdown, etc.
>>>
>>> Thanks for the ideas.
>>>
>>> - Mark
>>>
>>>
>>
>> it is hwclock on my system. it belongs to sys-apps/openrc-0.4.2 which
>> you may not be using.
>>
>>
>
> Ah, OK, I'm not using openrc.
>
> Anyway, I've been trying to fix it with fsck. Trying different
> options. Letting fsck fix it automatically, etc. so far nothing is
> fixing these problems. I don't know how to tell if the problem is
> really on the drive or whether it's caused by the clock not working..
> the complaints are about 4 partitions:
>
> /dev/sda2 which is my root partition
>
> /dev/sda5, 7 & 9 which are partitions that are normally not
> automounted. I tried the fsck on reboot thing and I thought it fixed
> it - it said it had and had to reboot - but then on reboot it said it
> wasn't fixed. I also changed my fstab file to mount the 3 partitions
> that normally aren't mounted to be mounted and then did the fsck on
> reboot again. It runs through all the partitions, says it's fixing
> them, and then they still aren't finished.
>
> I'm leaning toward this being a clock problem but I've not run fsck by
> hand very often so I'm trying to be extra careful.

I used to get that same message every time I rebooted and I'm pretty
sure it was related to the hardware clock config. I changed from local
to UTC and I think that fixed it for me.

Reply via email to