Help, my disk array has one dead member

[Karl Auer]

On Sun, 2017-03-26 at 12:57 +0200, Xen wrote:
> Yes yes, I just meant to get some clarity on the actual risks for 
> personal reasons.

The BER is one quantified risk.

Other risk factors are vibration, heat (though less than you might
think), electrical failure (overcurrent, undercurrent, surges, sudden
loss, static discharge), mechanical shock, thermal shock, and
manufacturing consistency (chassis, drives, PCBs, cabling, firmware,
software). 

That doesn't count natural disasters or all the various ways that
humans can screw up the data on a properly functioning NAS :-)

Regards, K.

> If there is corruption happening on the copy level, that is a matter
> of concern to me.

Calculate hashes, store them in a database, compare on read. They won't
help you fix the corruption but they can tell you it has occurred.

> I have now read 33x 10GB = 3.3TB and there is no discrepancy yet
> between these reads :p.

Nor should you expect one. It'll happen at 12.5TB! (<--joke) And
anyway, Murphy's first corollary says it will happen at the worst
possible time.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: A52E F6B9 708B 51C4 85E6 1634 0571 ADF9 3C1C 6A3A
Old fingerprint: E00D 64ED 9C6A 8605 21E0 0ED0 EE64 2BEE CBCB C38B