-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-02-13 at 11:04 +1100, Basil Chupin wrote:
Carlos E. R. wrote:
That was 2007-02-12... I had a bad "system failure" and I have been busy recovering. I'm now fully on 10.2, and I can no longer check my original problem (was on 10.1).
Hi Carlos,
I wonder if what I am experiencing is in any way related to your situation.
Let's see. ...
What I did a couple of days ago was to run e2fsck on the 10.2 partition - and I got the following error messages which I have never seen even when using ext3 some years back:
Error message #1:
Superblock last mount time is in the future, Fix<y>?
Yes, I have seen that - but here in this list.
Error message #2:
/dev/hda9 has gone 49709 days without being checked, check forced
[that's 136 years!]
Probably a consequence of the previous one.
After the above was repaired by e2fsck the system shutdown OK.
BUT, this morning....... I had the usual trouble of booting.
I did the e2fsck check and.... Error message #1 came up again (but not #2). After the fs was repaired 10.2 booted without a hitch.
Ah, then #2 wouldn't be a consequence of #1.
Just to allay what the state of the clock is, the system clock *is* set to the correcttime and date and NTP runs everyday (and I also occasionally run NTPDATE manually just to 'keep NTP honest').
If this is not somehow related to your situation perhaps you (or someone) can offer a reason for Error #1 (and #2), how to avoid it, and what else to check to see what is causing it.
No, not related. But it was reported here, and the person having it solved by changing the time settings in Yast so that the hardware clock (or cmos, battery clock) uses UTC/GMT time - which will be very inconvenient for you if you double boot to windows, but the preferred method for a Linux only machine. I don't recollect the thread name, but it won't be difficult to locate. It appears that when the fs is checked the system clock is not properly set up yet and is using the bios clock, which if set to "local time" in you case would be 11 hours different from the UTC time that the fs probably uses... and thus the problem. Why this happens in 10.2 and not in 10.1 I can't guess; maybe the time check is new, or it is a new bug. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF18OStTMYHG2NR9URAlWpAJwJFk2Dj2CqSna7uRJ3hahkScudVQCcC2rl 3pdaIFAqjeKi7r1ceP2w80I= =bKhi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org