rinukkusu

Ah, thanks - I heard about the Unbalance App! When swapping out the single disks I will probably need to let it sync in between each swap, right? (to rebuild the data on it)

Yeah, correct - I want to do a complete makeover Current setup: 2 parity, 7 data (all 4TB) My new setup to be: 1 parity, 2 data (all 16TB) As I go, I will probably add a new data drive and then again a second parity drive, but that's in the future

Thanks for your reply - how do I get the data from all old drives to the new drives with your proposed method? With a parity rebuild I'd only get 4TB of data of the old drive.

Hi, currently I have a config with 9 drives à 4TB (with 2 as parity) and I want to move to 3 drives à 16TB as to have a better upgrade path in the future. Now to my question, since I couldn't really find a conclusive answer: what's the best way to go about this? An idea I had was to use a second PC with a new UNRAID install where I create the config for the 3 drives, then I copy everything over network from the main server to this temporary one. After that's done I figured that could be the way of migration: Power down the main server Remove all 4TB drives Add the three 16TB drives Power on and create a new config Add the 3 drives in the same way as they were in the temp PC (regarding parity and data drives) Start array ???? Profit Could this work? What's the preferred way of doing this? Thanks and BR!

I face the same issue recently. Deleting a folder while restarting a Docker container that "uses" them makes /mnt/user go down.

Can confirm - wanted to install it right now, but got greeted with this error instead.