Hi all! On my server both parity drives have simultaneously failed. Though it's possible it's hardware and both drives happened to fail at the same time, that seems unlikely to me, especially since they're the newest drives in the server... but it's always possible the server was physically jostled or something.

 

I've tried removing them both from the array and re-adding them both individually and together, and swapping parity 1 and 2, but it always fails in the parity rebuild. It then does a read check, which passes.

 

Both drives pass SMART tests, though honestly I don't know how meaningful that is.

 

The rebuild seems to fail at a different point as well, sometimes getting several million writes on the parity drives, sometimes only a few thousand.

 

Any clues as to how to diagnose this, or confirm the drives have actually failed would be appreciated.

 

Thanks

 

 

Please post the diagnostics.

On 3/17/2024 at 8:44 PM, JorgeB said:

Please post the diagnostics.

 

 

Edited March 21, 20242 yr by Erasmus

It's not logged as a disk problem, and SMART looks fine for both, both disks dropped offline and reconnected, so most likely a power/connection issue, do they share anything in common other than the controller, like a power splitter?

Or maybe bad/loose data cable connection?

Maybe there's a firmware update?

It's also weird how unbalanced the writes are to the 2nd parity, 7M vs 675K writes.

I would expect they should always match exactly.

Here's what mine looks like:

 

Also, some of your drives appear to be running hot, heat is the no.1 HDD killer. See if you can get some more fans blowing on them.

Did you try to change their physical location in your case?

Recheck cables (data and cable) are fully seated.

On 3/17/2024 at 10:47 PM, JorgeB said:

It's not logged as a disk problem, and SMART looks fine for both, both disks dropped offline and reconnected, so most likely a power/connection issue, do they share anything in common other than the controller, like a power splitter?

I'm now pretty sure you're right and it was a power/connection issue. I don't know what the issue was... I had already tried re-seating all the cables and it hadn't helped, but I did it again and it's now happily rebuilding the parity drives so I guess we'll all good! Or rebooting just happened to fix the issue, I guess, but human error seems more likely. Thanks for the suggestions everyone!

 

 

Edited March 20, 20242 yr by Erasmus