Seven days ago I received notice that my Parity disk is in error state. After some research, I stopped the array, unassigned the disk, started the array, stopped the array, then assigned the disk and started it back up and rebuild the parity drive. The parity drive re-built with no errors and the whole server was working just fine up until today, 7 days later. I've attached a screenshot of the main page and the diagnostics log.

 

Any thoughts on what to do next? Could it be just a loose wire? Or is the disk faulty (hopefully not the case since it's my newest drive, only about 1.5 years old)?

 

tower-diagnostics-20190206-2125.zip

Parity isn't reporting SMART. Check connections and post a new diagnostic.

Okay, I did a clean power down. Secured all the connections and then re-booted. Attached is the new diagnostics log. 

 

Note: while doing this I got the same looking main page (with a red X on my parity drive). I'm not sure a full parity check occurred. Would you recommend a stopped the array, unassigned the disk, started the array, stopped the array, then assigned the disk, and do a full re-build?

tower-diagnostics-20190206-2149.zip

Disk looks OK. I think you must have meant a parity sync (rebuild) instead of a parity check. In any case, you have to rebuild as before since it is disabled and that red X isn't going away until you do.

Sounds good. I now stopped the array, unassigned the parity drive, started the array, stopped and re-assigned the parity drive, and started it back up for a parity sync rebuild. Crossing my fingers that fixed it.

It finished rebuilding with no sync errors. So if I get another "Parity disk in error state" warning in the next couple of days, do you think I need to start replacing wires?