On Fri, Jun 21, 2013 at 3:31 AM, Duncan <1i5t5.dun...@cox.net> wrote: > BUT RAID5/6 DOESN'T USE > THAT DATA FOR INTEGRITY CHECKING ANYWAY, ONLY FOR RECONSTRUCTION IN THE > CASE OF DEVICE LOSS!
Well, to drive this point home in the case of the thread that wouldn't die, I had put an entry in crontab a week ago to do a weekly forced check of all my arrays. Last week it passed. Today towards the end drive performance seriously deteriorated, and eventually smartd sent me an email about pending sectors (these are read errors). Long story short I ended up failing the drive out of the array (at which point my system stopped crawling), and tried wiping the bad sectors individually, and after self tests kept failing I even tried zeroing the drive. With sustained read failures under those circumstances I decided the drive had to be suitable for RMA. The drive was almost a year old. So, crossing my fingers that I don't suffer another failure and I'll be ginger with my clean shutdowns. Since the problem was discovered before I had dual failures the RAID should be recoverable without further loss. If you don't already, check your arrays weekly in crontab. Scripts for this can be found online or I'd be happy to post the one I dug up somewhere... Rich
