October 20, 201510 yr I have recently ran a couple of parity checks without a single error. Today, while preclearing one drive and started to use MC to move files from one disk to another, received an error pointing to the parity disk. Diagnostics attached. Can someone shed a light on this? Is the Parity disk bad? tower-diagnostics-20151020-0100.zip
October 20, 201510 yr Community Expert What exactly do you mean by "received an error"? There is no SMART in your diagnostics for your parity drive.
October 20, 201510 yr Author I guess that at 1 AM in the morning I could have been a little more clear. The error message from the unRAID is "Parity disk in error state (disk dsbl)", pointing to the parity disk sdc. So perhaps something else has happened, other than the parity disk going bad, but the parity itself is bad. I see that disks ST32000542AS_5XW18GZS-20151020-010 and WDC_WD20EADS-00R6B0_WD-WCAVY5786566-20151020-0100 have errors in the SMART reports. Could those be causing the invalid parity? If yes, which of those drives caused the event and w's the best next option? Sorry if I'm still being a bit vague.
October 20, 201510 yr Community Expert I guess that at 1 AM in the morning I could have been a little more clear. The error message from the unRAID is "Parity disk in error state (disk dsbl)", pointing to the parity disk sdc. So perhaps something else has happened, other than the parity disk going bad, but the parity itself is bad. I see that disks ST32000542AS_5XW18GZS-20151020-010 and WDC_WD20EADS-00R6B0_WD-WCAVY5786566-20151020-0100 have errors in the SMART reports. Could those be causing the invalid parity? If yes, which of those drives caused the event and w's the best next option? Sorry if I'm still being a bit vague. If your parity disk is disabled it will have to be rebuilt. Maybe a screenshot of Main would help clarify.
October 20, 201510 yr Community Expert I guess that at 1 AM in the morning I could have been a little more clear. The error message from the unRAID is "Parity disk in error state (disk dsbl)", pointing to the parity disk sdc. So perhaps something else has happened, other than the parity disk going bad, but the parity itself is bad. I see that disks ST32000542AS_5XW18GZS-20151020-010 and WDC_WD20EADS-00R6B0_WD-WCAVY5786566-20151020-0100 have errors in the SMART reports. Could those be causing the invalid parity? If yes, which of those drives caused the event and w's the best next option? Sorry if I'm still being a bit vague. the fact that the diagnostics did not get a SMART report for the parity drive suggest that it dropped offline. unRAID will only have disabled it if a write to it failed. Whether that is a permanent error or a transient one is hard to determine at this point. A question is whether a reboot brings it online again so that a SMART report can be obtained. Other disks having issues should not cause the parity disk to be disabled unless they somehow affected the controller to which the parity disk is attached.
October 20, 201510 yr Author I guess that at 1 AM in the morning I could have been a little more clear. The error message from the unRAID is "Parity disk in error state (disk dsbl)", pointing to the parity disk sdc. So perhaps something else has happened, other than the parity disk going bad, but the parity itself is bad. I see that disks ST32000542AS_5XW18GZS-20151020-010 and WDC_WD20EADS-00R6B0_WD-WCAVY5786566-20151020-0100 have errors in the SMART reports. Could those be causing the invalid parity? If yes, which of those drives caused the event and w's the best next option? Sorry if I'm still being a bit vague. If your parity disk is disabled it will have to be rebuilt. Maybe a screenshot of Main would help clarify. Here is the screenshot of main. Does it help? Should I reboot and see if it comes back? . . . I've remotely restarted the unRAID. Parity disk did not come back. I guess I'll have to wait till I come home from work to find out why the disk was dropped. Maybe a loose cable or something on the motherboard. Unlikely as I have a Norco 4220 with a SATA to SF8087 cable connecting the parity row, and the other drives on that same cable are all registering. Tower_Main_failed.pdf
December 3, 201510 yr This is my very first build . The issue I am having ...... "parity is invalid" right at the start. this a new build .. 4- W.D. 6 TB. red nas drives Asrock c27504I M.B. 1- 120 GB. (ssd) drive 8 gig of ddr3 Also on the Main screen the total size is reporting only 6TB. You guys have any thoughts on what it wrong here?
December 3, 201510 yr Community Expert This is my very first build . The issue I am having ...... "parity is invalid" right at the start. this a new build .. 4- W.D. 6 TB. red nas drives Asrock c27504I M.B. 1- 120 GB. (ssd) drive 8 gig of ddr3 Also on the Main screen the total size is reporting only 6TB. You guys have any thoughts on what it wrong here? Don't hijack other user's support threads. Go to Tools - Diagnostics and attach the complete diagnostics zip to the first post of your own thread along with a description of your problem.
Archived
This topic is now archived and is closed to further replies.