I needed to replace both parity drives in my perfectly healthy system with larger ones.  So I got two new drives and put them both through preclear to stress them a bit first.  They finished successfully.  I then stopped and shut down, pulled the old (valid) parity drives, moved the precleared drives to the slots that contained the old parity drives I just pulled.  I then booted the system, assigned the new drives to the parity and parity 2 slots, and started the array to rebuild the parity drives.

 

The rebuild stopped almost immediately with the new parity 2 drive 'X'd out with a bunch of errors.  Obviously I'm skeptical because it just got through a preclear.  So I shut down again, rechecked cabling and seating of things, and tried again.  Now the system is rebuilding Parity 1 but (what I should have thought of earlier) the second parity drive remains 'X'd out.

 

So I'm basically accidentally building a single-parity drive system.  Being a bit paranoid, I am (1) going to let that finish and (2) not touch anything else so the old parity drives remain valid for the time being.  When the rebuild finishes, I will then want to un-"X" that other drive and get it added again as the second parity drive. 

 

How do I do that?  If possible, I'd prefer a solution that doesn't involve magic "don't mess this up or you're dead" command line commands.

 

Thanls!

Edited December 27, 20232 yr by jhyler

Please post the diagnostics.

Diagnostics attached, sorry about that.

 

Things may be worse than I thought. The array operations page shows the elapsed rebuild time increasing, but the current position (0.3%) and speed are not changing.  The array devices page shows no disk activity on any disk.  Help!

tower-diagnostics-20231227-1003.zip

Parity2 may be failing, it's not even giving a valid SMART report, to rule out a power/connection issue swap cables/slot with parity1 and try again.

I moved the drive to where parity1 was and tried, it got a bunch of read errors almost immediately.  I've since pulled it out, put the other new drive in its place, and restarted a single-parity rebuild.  So far it's working, it at least got past the 0.3% point where it had stopped before.

 

How - HOW - does a disk get through an almost 2-day long preclear, all those pre-clear and post-clear reads succeeding, and then fail with read errors immediately thereafter? The only difference I can think of is that when being precleared it was connected directly to a SATA port, and then I moved it to an HBA.  That shouldn't matter, though - right?

 

Come to think of it, something like this happened to me not long after the WD Red 10TB disks first came out, there was something in how the disks spun down that something in Unraid or Linux didn't like, it took another couple Unraid releases before they were working reliably.  These new disks are the new red 22T models, I wonder if something like that could be going on.  Of course the new disk that is working is 22T also, so that seems unlikely.  Though now that I'm looking I see other people in the forum having issues with 22T drives.

 

Thanks for the help, I appreciate it.

Edited December 27, 20232 yr by jhyler