Just doing some sanity check before replacing my old 10TB parity drive with something larger.

 

1. disable docker and array auto start
2. stop the array
3. unassign old parity drive from parity slot
4. start the array & stop the array
5. power down, remove old parity drive & install new parity drive
6. power on
7. assign new drive to parity slot
8. hit Copy and wait

 

Is this about right? Also...is it possible to reduce the downtime (I expect it to be fairly long since parity is about 100TB) by adding parity2, and replacing the parity1? If so, what would by my steps?

Edited October 14, 20223 yr by truthfulie

9 minutes ago, truthfulie said:

• power down, remove old parity drive & install new parity drive
• power on
• assign new drive to parity slot

Just need these steps, then start the array, there's no downtime.

12 minutes ago, JorgeB said:

Just need these steps, then start the array, there's no downtime.

 

Thank you for the quick response. I was referring to https://wiki.unraid.net/The_parity_swap_procedure, has things changed since the entry was last edited? So power down, physically replace the drive, assign the new drive as parity and start the array. The parity rebuild process runs in the background while the array is operational (assuming without parity protection until rebuild is done)?

Yep.

 

Honestly if your watching videos are accessing data it should feel just like normal. I normally limit my writes while I'm adding/rebuilding Parity, but you still can. 

Good to know! And thanks for the confirmation! Just a bit unnerving doing something like this and want to double/triple check. 😅

15 minutes ago, truthfulie said:

I was referring to https://wiki.unraid.net/The_parity_swap_procedure,

Parity swap if for when there's a disabled disk and the replacement is larger then current parity, you just mentioned doing a parity upgrade.

Gotcha. I see the difference now. Thank you.