February 15, 20179 yr Hi all. Noticed my server wasn't running, I hard reset it and once it started the two parity drives are broken but a parity check option isn't available. https://puu.sh/u4Ufp/9bf843ed42.png Has anyone seen this before? The drives seem to be in the system, as in not missing. I am not sure what is wrong. EDIT: Stopped the array, unassigned the parity drives and then re-assigned them. Started the array and its now doing a parity check. A little scary that it can just fall over like this. Attaching Diagnostics. damonster-diagnostics-20170216-1019.zip
February 15, 20179 yr Community Expert Red X means the disk is disabled. This is true whether it is a data disk or a parity disk. unRAID disables a disk when a write to it fails, because its contents are invalid due to the failed write. A disabled disk must be rebuilt by calculating its correct contents from the rest of the array and writing it. unRAID will not use a disabled disk until it is rebuilt. Since you rebooted after whatever caused the write failure, we don't see anything about it in your logs. The SMART for both parity disks looks OK. Often a bad connection is to blame for I/O errors. If it happens again, check connections.
February 15, 20179 yr SMART reports look ok but you have a lot of cable problems indicated in your syslog. Chances are your parity disks dropped offline as a result and the power cycle brought them back again. You need to check all data cables to disks or others will drop offline too. Controllers ata1 and ata2 are struggling in your log. They are controlling disks WDC_WD40EFRX-68WT0N0_WD-WCC4E0987147 and WDC_WD40EFRX-68WT0N0_WD-WCC4E1NL7TCD respectively.
February 16, 20179 yr Author I am aware I have bad cabling, I have wanted to replace my server for a while, this is a good push. Thanks lads.
Archived
This topic is now archived and is closed to further replies.