Latest stable Unraid Pro.

Disk 3 (2TB) has failed, so have bought 1x 6TB to upgrade Parity from 4TB to 6TB.

Power off Array

Unplug cables from Parity Drive and plug into new 6TB.

Also unplugged cables and removed Disk 3 (faulty data disk).

Power up array.

Assign 6TB drive to Parity.

But Unraid is reporting "Wrong"

It's wanting the 4TB I unplugged and doesn't like the 6TB I've installed and assigned to Parity.

Probably a simple mistake on my part.

Any suggestions from the audience please ?

 

I've been following these instructions

https://wiki.unraid.net/The_parity_swap_procedure

 

Sounds like you missed step 12:

Quote

Assign the old parity drive in the slot of the old data drive being replaced

This is why it is a "swap". Old parity replaces failed data disk, new larger disk becomes parity.

 

Please read the whole procedure again and ask if you have questions.

Better yet,

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

 

It might be worthwhile to consider why exactly you think disk3 has failed instead of something else causing a problem accessing disk3.

1 hour ago, trurl said:

 

Better yet,

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

 

It might be worthwhile to consider why exactly you think disk3 has failed instead of something else causing a problem accessing disk3.

I deliberately skipped Step 12 because it seemed safer to me, to rebuild parity on new disk, then recycle old parity disk into data.

But having carried out Step 12 (array is now copying parity data now, all good), I can see that Unraid is much smarter than I gave it credit for.

Serves me right.

 

Disk 3 is about 5 years old, so I'm happy to bin it and replace it.

Diagnostics attached. 

Probably academic now that the array is rebuilding ok.

tower-diagnostics-20201121-1431.zip

And thank you for your help, much appreciated.

12 hours ago, MPR Files said:

Diagnostics attached. 

Mostly just wanted to take a look at SMART for the original disk3, which of course isn't in those diagnostics. And since the array isn't started until after the parity copy, many other things can't be known from those, such as whether disks all mount.

 

Let us know if you have any questions or problems.