Mick wrote:
On Sunday 27 February 2011 17:15:40 Grant Edwards wrote:
On 2011-02-26, Dale<rdalek1...@gmail.com> wrote:
This appears to be a corrupt file somewhere.
In my experice, failing RAM often appears as a corrupt file
somewhere.
Yep, when I had a failing memory module I would often end up with corrupted
files all over the place. Think about it, when the memory gave up some write
on disk function was invariably foo-barred.
This was my logic tho. Reboots when using the OS on the hard drive.
Runs fine when booted from something else, memtest, system rescue or
even Knoppix. If it was memory, then it should fail on everything at
some point. Since it only failed when booted from the hard drive, I was
looking for issues with it.
What you are saying is completely correct tho. If I load a file into
ram that is bad, then it gets written back to the drive, that file is
broke. That will cause problems eventually and who knows what sort of
flakey issue that will be.
Anyway, recompiling everything gives me this:
root@fireball / # uptime
14:05:46 up 1 day, 5:29, 4 users, load average: 0.43, 0.24, 0.23
root@fireball / #
I think it is going to be OK now. Some file was having a bad hair day.
lol
Dale
:-) :-)
