March 9, 201511 yr I replaced Disk 10 in my array, which had lots of errors and was going downhill fast. Ran a parity check afterwards and all was well for a while, but finished the check with errors on Disk 5 and a red ball on that drive. Syslog attached. I intended to just switch cables and try again, but though I'd check here first. Thank you! Dave syslog_DPC_MAR_9.zip
March 10, 201511 yr Your syslog is showing read and write errors to disk5. A redball on a disk means unRAID has disabled it due to a write error. It does this because the data is no longer considered reliable. Your parity will have the correct data though, so you can rebuild to get the data reliable again. You cannot do a parity check with a redball. Even after fixing any cabling problem, the drive will still be disabled. The best way to proceed is to rebuild the drive onto a new drive that you have already tested with the preclear script. The next best way to proceed would be to make unRAID forget about the disk and rebuild it onto itself. The last possibility is to do a new config and rebuild parity instead, but this is not recommended because your parity data is probably more reliable than the failed drive. There are also some things in your syslog that might indicate a flash drive corruption but that is unrelated.
March 10, 201511 yr I replaced Disk 10 in my array, which had lots of errors and was going downhill fast. Ran a parity check afterwards and all was well for a while, but finished the check with errors on Disk 5 and a red ball on that drive. Syslog attached. I intended to just switch cables and try again, but though I'd check here first. Thank you! Dave You have a bad / loose sata and/or power cables to WD-WMC1T1495377 (disk 5) This is the root cause of the redball This entry is in your syslog prior to the errors: Mar 8 19:45:51 Tower kernel: ata13.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 8 19:45:51 Tower kernel: ata13.00: failed command: READ DMA EXT Mar 8 19:45:51 Tower kernel: ata13.00: cmd 25/00:00:58:ff:a1/00:02:41:01:00/e0 tag 0 dma 262144 in Mar 8 19:45:51 Tower kernel: res 51/40:8f:c8:00:a2/00:00:41:01:00/e0 Emask 0x9 (media error) Mar 8 19:45:51 Tower kernel: ata13.00: status: { DRDY ERR } Mar 8 19:45:51 Tower kernel: ata13.00: error: { UNC } While it also does state "media error" which implies a bad sector, I have a feeling that it is merely a by-product of the power / sata connection. Since you just replaced disk10, you probably knocked loose the connections to that drive. You should reseat all of the connections to the drives and try it again. Problems like these are why I'm a huge fan of hot-swap bays for large arrays.
March 16, 201511 yr Author I replaced Disk 10 in my array, which had lots of errors and was going downhill fast. Ran a parity check afterwards and all was well for a while, but finished the check with errors on Disk 5 and a red ball on that drive. Syslog attached. I intended to just switch cables and try again, but though I'd check here first. Thank you! Dave You have a bad / loose sata and/or power cables to WD-WMC1T1495377 (disk 5) This is the root cause of the redball This entry is in your syslog prior to the errors: Mar 8 19:45:51 Tower kernel: ata13.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 8 19:45:51 Tower kernel: ata13.00: failed command: READ DMA EXT Mar 8 19:45:51 Tower kernel: ata13.00: cmd 25/00:00:58:ff:a1/00:02:41:01:00/e0 tag 0 dma 262144 in Mar 8 19:45:51 Tower kernel: res 51/40:8f:c8:00:a2/00:00:41:01:00/e0 Emask 0x9 (media error) Mar 8 19:45:51 Tower kernel: ata13.00: status: { DRDY ERR } Mar 8 19:45:51 Tower kernel: ata13.00: error: { UNC } While it also does state "media error" which implies a bad sector, I have a feeling that it is merely a by-product of the power / sata connection. Since you just replaced disk10, you probably knocked loose the connections to that drive. You should reseat all of the connections to the drives and try it again. Problems like these are why I'm a huge fan of hot-swap bays for large arrays. Thank you! I ran a smart report and found no issues, so switched cables and rebuilt the disk and all is well.
Archived
This topic is now archived and is closed to further replies.