Array has 2 disks with read errors

[j.w.l]

Hello,

 

Today when I got up I was greeted with alerts from my Unraid server that 2 disks had read errors.  One was my first parity disk and the other was one of my data disks.

 

Quote

 

Parity disk - HUS724040ALS640_PCJA9HBX_35000cca05c837974 (sdb) (errors 1024)

Disk 1 - HUS724040ALS640_PCJEZBTX_35000cca05c8a2780 (sde) (errors 211)

 

 

Apparently, the parity disk had enough errors that it was automatically disabled, while Disk 1 is still up and running.

 

Quote

Parity disk in error state (disk dsbl)

 

So I'm not sure if both drives decided to go bad at the same time or if something else is going on.  I've attached my system’s diagnostics zip file as well.

 

Any help with this would be greatly appreciated.

 

Thank you.

tower-diagnostics-20221021-0754.zip

Edited October 21, 2022 by j.w.l
remove link

[JorgeB]

Disks look OK, parity issue started right after spin up, but it spun up many times before, so maybe a one time thing, though if it happens again you might want to try disabling spin down, with SAS disks especially it's not always 100% supported.

[j.w.l]

Thanks! Just started the parity sync. I'll keep an eye on it and if any more issues arise, I'll try disabling spin down.

[j.w.l]

So based on what happened last time, I disabled spin down on the two parity drives by setting their 'Spin down delay' to 'Never'.  However, when the parity check started for this month, Parity Disk 1 was disabled again.  Parity Disk 2 remained in a normal state with no errors this time.

 

It seems to only happen when a parity check is running, and not during normal operation.  I've attached a new set of diagnostics.  Any help would be appreciated again.

 

Thanks.

tower-diagnostics-20221202-0752.zip

[JorgeB]

It's not logged as a disk problem and SMART looks OK, suggest swapping cables/slot between the two parity disks and see if the issue follows the disk or not.