I was following the directions for a failed disk parity swap and the server was saying too many wrong disks no matter what I did. 

 

Pulled failed disk.

Added new bigger parity.

Put parity in the failed slot.

Too many wrong disk errors.

Ran new config..

 

I did a new config to get the disks to cooperate and now I don't have the option to copy the old parody to the new one.

 

Did I screw everything up?.

Do I start the Array?

Do I have to start from scratch? (I hope not)

 

 

EDIT:

 

I am going to start the array with no parity and see what it does. I have the failed disk and it is still readable in UD. I am hoping I can start the array, and copy the contents to the old parity disk. OR do I take the old parity disk out and add a new disk in its place then copy the data over and let it update parity???

Edited November 1, 20232 yr by Juscuz17
Spelling and added to it

SOOO, the disk I was replacing had a read error that unraid took it offline for. I put all the drives back in where they were and started the array with parity turned off. All drives are showing healthy.

 

Should I mount the new parity drive and let it update the parity? The drive is reading fine right now. or should I try and copy the failing drive to the old parity drive then mount the parity disk?

 

What would be less stress on a questionable drive, coping files off it, or mount the parity drive and let it update.

 

Any input at all guys???

Edited November 1, 20232 yr by Juscuz17

Just in case my post helps someone later.

 

I got lucky because my drive was still working. I was able to put the array back the way it was, mount the new bigger parity and let parity do its thing.

So far so good. in 17 hours I will know if it worked.