linux-os (Dick Johnson) wrote:
> On Wed, 16 Nov 2005, Eyal Lebedinsky wrote:
[report of hwclock breakage trimmed]
>
> If your machine was being heavily swapped when the disk problems
> occurred, this __might__ explain the corruption. However, I would
> first check RAM, do not overclock, etc. It might be that bad
> RAM, in fact, is the reason for all your problems and you don't
> really have disk or driver problems at all.
I will now keep watching for q while quietly. Earlier today I had
another such hard lockup, identical errors claiming a disk failure.
This time I went into the BIOS on bootup and the clock was set
correctly. Good. Booted and it did the usual fscks but then dropped
into a shell when errors were found on /. I did the necessary fscks.
On a hunch I did 'date' and the clock was 11h ahead (we actually
are +11 now). So the problem is during the boot, not during the
crash. I consider that the boot thinks that I am running a UTC
hwclock and adjusts for this, when in fact I run a local time
hwclock. There must be something in the scripts that goes funny
if / does an fsck and then drops into the recovery shell.
I will start looking in this direction.
This is Debian Sarge in x86.
Thanks
--
Eyal Lebedinsky ([email protected]) <http://samba.org/eyal/>
attach .zip as .dat
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
