Well, I was unable to boot up because it got so bad. Knoppix to the rescue!
I would like to upload a log file I made of all that I did and the
errors I got but IIRC the list strips large attachments. The file is
about 30K. I remember someone mentioning that files could be uploaded
somewhere to the KPLUG web site and served up with a link. The
following paragraph is a brief summary of what I did.
I did several things, starting with doing my best to copy off the most
important stuff from hde to hda (too small to hold much more than /home
and /root). Then I did "mke2fs -c -c -j -v" and "e2fsck -c -c -v" on
the previously untouched remainder of hde (/dev/hde10) and copied just
about all of / over to it. (I left out at least /dev and /proc.) Then
I used both of these commands on the swap partitions, and the "e2fsck -c
-c -v" on all the other Linux partitions of hde. hde10 covers the
majority of the drive and had no errors. No other partitions had errors
either *except* hde6 (which is / <- everything but /boot (hde2)).
hde6 was the *only* one with errors and ended with 189 bad blocks. But
from all the errors found, I got the distinct impression that it was
mostly a bad case of crosslinked files getting worse with time, although
that would not account for the bad blocks. And I do not claim to be
able to really understand the error messages. I just chose the default
answer to all the questions.
I have not yet run the Hitachi HDD diagnostics program because I
couldn't boot up to go online, at least not until after I did the
"e2fsck -c -c -v" on hde6. Even as I type this, I am downloading it.
Ralph Shumaker wrote:
Ralph Shumaker wrote:
DJA wrote:
Ralph Shumaker wrote:
DJA wrote:
(snip)
I am also assuming that you are using the same RAM which was
installed in the "fried" motherboard. And what about the CPU? I
generally don't consider CPU's because, in my experience, they're
either on or off. But RAM is a bit more forgiving; that is, it is
more prone to dying a slow death.
I think I transfered one or two of the RAM sticks, though memtest86
has not detected any errors. I am only aware of the standard 8 tests
and the 9th (bit fade) test.
Oops. Make that "the standard *9* tests (0-8) and the *10th* (bit
fade) test".
Then I had to figure out why I was still unable to launch Mozilla
(some
lock file that had to be hunted down and destroyed). Then, things
were
back to normal, for a while.
Mozilla can and does do this all on its own without any help from
errant hardware. OO.o puking starts to look suspicious. Suspiciously
like RAM. Both programs like lots of healthy RAM.
Perhaps the RAM was flaky on system #3, but it passes memtest86 tests
1-9 flawlessly.
Oops. Make that *0*-9.
o Download and use the manufacturer's diagnostic software for your
drive. AFAIK, all of the major brands (IBM, Maxtor, WD, etc.)
have such a program available on their Websites.
I'll check on this after memtest has its run.
Good.
I think it's Samsung, but I guess I'll have to power down to check.
"dmesg" only tells me
hde: HDS722516VLAT80, ATA DISK drive
I don't know why I was thinking Samsung. It is a Hitachi. And their
web site is even noted on the drive.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
