DJA wrote:
Ralph Shumaker wrote:
DJA wrote:
One very important question before you start pointing fingers: Is
this problem repeatable: can you duplicate the error?
If so, then that raises the probability that the drive is bad (to
some unknown degree). If the problem comes and goes, then you should
suspect /everyone/ in the box, except the case, as I said before. In
fact, I generally suspect everyone no matter what the symptoms are.
I've saved both time and money with that attitude.
memtest86 turns up *no* errors.
All eleven tests?
The version I'm using (v3.2) has only 9 tests. The change log said
something about eliminating a couple of them.
I've not yet tried getting motherboard bug lists, nor their
workarounds, nor drive diagnostics.
Next step: run the drive diagnostics. That should be pretty
conclusive, one way or the other. Remember to run it first *without*
the Promise card, then again with.
Tomorrow I will shut down and pull the drive to see the Manufacturer and
other info.
Well, here is some of root's mail (recently discovered). There were
a total of 187, but I deleted the ones that I was sure were nothing.
Most of the ones remaining denote dma problems. Here are the first 7
of them (although #4 seems unrelated):
All errors seem pretty clustered so the errors are isolated, so far,
to one small part of the drive. Most reports concern repeated errors
at the same sectors. If it's the drive, there's a good chance the
errors are correctable (that is, can be mapped out on by the drive
diag software).
You should enable SMART in your BIOS if it's supported. Also Linux
supports SMART.
If it turns out to be the drive and it's less than a year old, you can
return it to the merchant for replacement.
I'll have to find that receipt. It's not where it's supposed to be.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
