June 3, 201610 yr So after my monthly parity check, disk1 came back with 127 errors, which is the first time I've ever seen any errors on any disk. Since then, I've run a parity check with "write corrections" checked and it came back with 0 errors, but the 127 still shows next to disk1 (screen shot of main attached). I also ran a full SMART report (attached) and included the diagnostics file. Are these errors something I should be worried about? Is there something I can do to clear them? Thanks in advance. smart.txt
June 7, 201610 yr Author Anybody? Is this something that is well documented that I'm missing? If so please point me in the right direction and I'll do the needed reading. Thanks.
June 7, 201610 yr Community Expert SMART for disk1 looks fine, but that by itself does not rule out a bad disk, on the other hand it can also be a bad/failing cable or sata port. What I do in these situation is replace both cables and connect the disk to a different controller/port (trade with another if none is available), if there are errors on the same disk again then replace it.
June 7, 201610 yr Can I ask? I'm still getting used to Unraid... If disk1 had the errors then why not rebuild disk1 from parity (and the rest) rather than just write corrections to parity. I'm trying to get my head around the logic. If disk1 showed the errors then hasn't write corrections to parity just compounded the errors on disk1 so that the 127 errors are now not recoverable? How do you know that disk1 or parity is the wrong or right data? V Sent from my iPhone using Tapatalk
June 7, 201610 yr Can I ask? I'm still getting used to Unraid... If disk1 had the errors then why not rebuild disk1 from parity (and the rest) rather than just write corrections to parity. Actually, that's what happened. There was an error reading from disk1. Unraid calculated what should have been in that spot from parity and the rest of the drives, and wrote the result back to disk1. That write succeeded, so unraid just noted the error, and moved on. The subsequent parity check was able to read that rewritten data successfully, and it matched what was supposed to be there, so no corrections were needed at that point. Had the initial write after the read error failed, unraid would have red balled the disk, and ignored it for all subsequent operations, using the rest of the disks to emulate the drive.
June 8, 201610 yr Author Thanks for the reply johnnie. I'll try to get the drive moved over to another port tonight and get the parity check started. I'll post back when its done. Thanks.
Archived
This topic is now archived and is closed to further replies.