December 9, 20178 yr one of my WD Red drives (a 4TB EFRX), which is only 4 months old, shows thousands of errors (8384 of'em) during a parity rebuild (after changing physical disk-order, re-assigning drives in unRAID, and doing a New Config). what's the best order of action now to determine whether this disk is repairable and if so, repair it...since I'm in Germany and the drive's warranty is out of region (USA only) and I don't wanna buy another 4TB drive, alternatively I'd have to move all the data off it and replace it with a 3TB drive...which would require me to do yet another New Config and parity Rebuild, if I read the Wiki correctly (since disks can't be downgraded in size). to hopefully avoid that, I'd now have to... ?
December 9, 20178 yr Author sorry I didn't immediately attach them. unraid-diagnostics-20171209-1332.zip
December 9, 20178 yr Community Expert It's a bad disk:197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 30 Best option if your parity is invalid would be to move all the data you can to another disk(s) and resync parity without that disk or a new one in its place.
December 9, 20178 yr Author Man, when I look at my shelf with failed WD Green and Red drives, I wonder whether WD is still even remotely within their claimed MTBF's...unbelievable, but thanks for confirming so quickly! I'll know whether parity is valid in about an hour, but either way, I'll have to downgrade that drive to a 3TB and then do a New Config *again*, followed by a parity rebuild...hope that all drives will make it through this next one alive...jeeze!
December 9, 20178 yr Community Expert 4 minutes ago, tillkrueger said: I'll know whether parity is valid in about an hour Even if the current parity sync completes it will never be 100% valid due to the read errors.
December 9, 20178 yr Author good to know and thanks for warning me...then back to a New Config with a 3TB drive in its place it is...so it goes.
Archived
This topic is now archived and is closed to further replies.