| 1 |
Chris Reffett wrote: |
| 2 |
> Dale wrote: |
| 3 |
>> Harry Putnam wrote: |
| 4 |
>> |
| 5 |
>>> Stroller <stroller@××××××××××××××××××.uk> writes: |
| 6 |
>>> |
| 7 |
>>> |
| 8 |
>>> |
| 9 |
>>>> On 4 Nov 2009, at 15:45, Harry Putnam wrote: |
| 10 |
>>>> |
| 11 |
>>>> |
| 12 |
>>>>> ... |
| 13 |
>>>>> Somehow the date of last fsck on /boot is seen as `in the future' so |
| 14 |
>>>>> fsck fails on /dev/had1 (/boot). |
| 15 |
>>>>> |
| 16 |
>>>>> |
| 17 |
>>>> The first thing I would want to check is the motherboard battery. Is |
| 18 |
>>>> the time correct if you reboot and immediately enter BIOS? |
| 19 |
>>>> |
| 20 |
>>>> |
| 21 |
>>> That was a pretty good help but apparently not all the story. |
| 22 |
>>> |
| 23 |
>>> When I checked bios, the clock was exactly 1 hr fast (didn't pick up |
| 24 |
>>> the end of daylight saving time I guess). |
| 25 |
>>> |
| 26 |
>>> Reset the clock and tested with 2 more reboots, each time mounting |
| 27 |
>>> /boot and fiddling around with files. |
| 28 |
>>> |
| 29 |
>>> Each time the same failure occurs. I check bios time again. Its |
| 30 |
>>> right. |
| 31 |
>>> |
| 32 |
>>> Here is the (edited) output form fsck |
| 33 |
>>> |
| 34 |
>>> Superblock last mount time (Wed Nov 4 18:05:13 2009, |
| 35 |
>>> now = Wed Nov 4 12:11:49 2009) is in the future. |
| 36 |
>>> Fix<y>? yes |
| 37 |
>>> |
| 38 |
>>> [...] |
| 39 |
>>> ------- --------- ---=--- --------- -------- |
| 40 |
>>> Superblock last mount time (Wed Nov 4 18:14:54 2009, |
| 41 |
>>> now = Wed Nov 4 12:18:01 2009) is in the future. |
| 42 |
>>> Fix<y>? yes |
| 43 |
>>> |
| 44 |
>>> [...] |
| 45 |
>>> |
| 46 |
>>> so still somehow, those last mount dates are way wrong. |
| 47 |
>>> |
| 48 |
>>> I hope I'm checking the right thing in bios. Its under cmos and shows |
| 49 |
>>> the time ticking away. You can adjust all columns. with +/-. |
| 50 |
>>> |
| 51 |
>>> |
| 52 |
>>> |
| 53 |
>> |
| 54 |
>> I can't recall exactly how I did this but there is a command to tell the |
| 55 |
>> OS to set the clock on the mobo to the system time when shutting down. |
| 56 |
>> That way everything should sync up when you reboot, except for that tiny |
| 57 |
>> little bit if you shutdown completely for a few days or something. The |
| 58 |
>> command is hwclock. I can't recall where I put the thing because I am |
| 59 |
>> logged into KDE 4 and I can't find nothing in here yet. It's pretty but |
| 60 |
>> it is different so I'm lost. |
| 61 |
>> |
| 62 |
>> I *think* I put it in the rc file or something. I remember the file is |
| 63 |
>> run during shutdown tho. That may help if you know which file that is. |
| 64 |
>> |
| 65 |
>> Hope that helps. |
| 66 |
>> |
| 67 |
>> Dale |
| 68 |
>> |
| 69 |
>> :-) :-) |
| 70 |
>> |
| 71 |
>> |
| 72 |
>> |
| 73 |
> It's in /etc/conf.d/clock (or /etc/conf.d/hwclock for baselayout |
| 74 |
> 2/openrc), and it's called CLOCK_SYSTOHC. Set it to yes to write the |
| 75 |
> system time to hardware on shutdown. |
| 76 |
|
| 77 |
I think I did it the hard way then. I put the command in a file |
| 78 |
somewhere that runs during shutdown. |
| 79 |
|
| 80 |
More than one way to skin a cat a guess. |
| 81 |
|
| 82 |
Dale |
| 83 |
|
| 84 |
:-) :-) |
Archives