Hi, mdadm wrote:
> ATM I am still not sure about what caused the crash, maybe you are right
> and there is a hw problem. I assume it is the memory.
Personally I would, if I saw such an error, immediately stop the system,
run memtest86+ on it, and either replace the faulty RAM or, if no problem
is found, do the reconstruction on a different mainboard.
Bit errors scare me. The idea that the problem will propagate to some
unknown area of a presumed-good array scares me even more. (I speak from
painful experience here.)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@xxxxxxxxxxxxxx
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
The price of seeking to force our beliefs on others is that someday
they might force their beliefs on us.
-- Mario Cuomo
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
