[SOLVED] Parity drive error

[tuxbass]

Out of the blue got following notification:
 

Quote

Unraid Parity disk error: 06-06-2022 22:20
Alert [TOWER] - Parity disk in error state (disk dsbl)
WDC_WD40EFRX-68N32N0_WD-WCC7K1VRDCFN (sdc)

 

Starting SMART tests via UI does nothing, smart error log is empty.

Parity drive is WDC_WD40EFRX-68N32N0_WD-WCC7K1VRDCFN, sdc. Including diagnostics file:

tower-diagnostics-20220606-2221.zip

 

How should one proceed? Reboot and see if it's possible to run SMART test?

Edited June 9, 2022 by tuxbass

[JorgeB]

Jun  6 17:49:41 Tower kernel: ata4.00: disabled

Disk dropped offline, this is usually a power/cable problem, before it dropped there are several ATA errors logged, same for the SSD, check/replace those cables and post new diags after array start.

[tuxbass]

3 minutes ago, JorgeB said:

Jun  6 17:49:41 Tower kernel: ata4.00: disabled

Disk dropped offline, this is usually a power/cable problem, before it dropped there are several ATA errors logged, same for the SSD, check/replace those cables and post new diags after array start.

SSD/cache drive has been dripping those errors since almost day 1. Swapping cables around nor re-seating cable sockets hasn't improved it. Now looking, it seems the error count increase has sped up - used to be in the hundreds, now climbing into thousands...

 

So, I rebooted the server. It came back with no parity assigned to array at all.

- stopped array

- went to 'Array Devices' tab to re-assign it - but it's not even listed! Seems like a complete connection error? Attaching post-reboot diags (with array stopped though)

 

Guess best bet is to keep the array stopped, crack the case open and wiggle some cables?

tower-diagnostics-20220607-1139.zip

[itimpi]

It could also be a power issue - especially if you are connecting more than about 4 drives to a single cable from the power supply, or using splitter cables that can sometimes be problematic.

[JorgeB]

48 minutes ago, tuxbass said:

So, I rebooted the server.

Just rebooting usually won't help, a power cycle might, though as mentioned I would recommend replacing or at least checking the cables first.

[tuxbass]

After wiggling the cables for a 3rd (!) time the parity drive is listed again. Running extended SMART tests overnight, then rebuild the parity.

Is it possible the issue is caused by ageing setup? Living in a coastal subtropical zone and computer is now 6+years old - some metal bits on mobo are visibly corroded.

[tuxbass]

Parity rebuild was uneventful, array started back up a-ok!

Likely unrelated, but all docker world collapsed on me. Started another thread.