| 1 |
On Wed, Feb 4, 2009 at 10:47 AM, Barry Schwartz |
| 2 |
<chemoelectric@×××××××××××××.org> wrote: |
| 3 |
> Mark Knecht <markknecht@×××××.com> skribis: |
| 4 |
>> Subject: [gentoo-amd64] "Superblock last mount time is in the future. FIXED" but it isn't... |
| 5 |
>> From: Mark Knecht <markknecht@×××××.com> |
| 6 |
>> Reply-to: gentoo-amd64@l.g.o |
| 7 |
>> Date: Wed, 4 Feb 2009 10:05:54 -0800 |
| 8 |
>> To: gentoo-amd64@l.g.o |
| 9 |
>> X-Text-Classification: gentoo |
| 10 |
>> X-POPFile-Link: http://127.0.0.1:50000/jump_to_message?view=127082 |
| 11 |
>> |
| 12 |
>> Recently my AMD64 machine has started displaying this message at boot |
| 13 |
>> time. I don't know exactly when it started but I suspect it was when I |
| 14 |
>> started testing a new kernel that didn't have the RTC enabled when I |
| 15 |
>> was first testing it. |
| 16 |
>> |
| 17 |
>> Anyway, what's the process of fixing this. It says it's 'fixed' at |
| 18 |
>> boot time but booting again does the same thing. I've got |
| 19 |
>> e2fsprogs/e2fsck but I'm not sure if it can be used on a mounted drive |
| 20 |
>> and I figured it best to ask first. |
| 21 |
> |
| 22 |
> You can get that message if you have the HW clock set to local time. |
| 23 |
|
| 24 |
In my case it must be local (AFAIK) as I'm dual boot with a Windows XP |
| 25 |
installation. |
| 26 |
|
| 27 |
Thanks, |
| 28 |
Mark |
Archives