Sunday, December 18, 2016

How do you replace/upgrade hard drives in a window storage pool?


I currently have a storage pool that consists 6 drives in parity. 3x4TB and 3x8TB. I just purchased three more 8TB with the intention of replacing the 3x4TB drives but am having trouble figuring out the best approach. My assumption was I could take one of the 4TB drives out of rotation and replace it with the 8TB as if the 4TB had "failed", then add the 8TB as a replacement, wait for rebalance and then do the same thing 2 more times. Is there a better approach? Also how would I even go about doing this? I assume if I plug the 8TB into the same SATA cord as the original 4TB its not going to magically become part of the pool on its onw so how do I actually handle that in the storage pools UI? Any pointers?


Answer



The storage management UI has options to add new drives to the pool and to remove existing ones. Storage Spaces remembers disks by their ID (stored within the disk itself), not by physical connection, so a disk can be moved or temporarily disconnected without damaging the pool.


The safest option is to first add a new disk to the pool, then prepare the old one for removal. Storage Spaces will "evacuate" data from the old disk, and the pool's redundancy requirements will be satisfied at all times. Once the transfer is complete, you will see an option to remove the physical disk entirely. (See official docs.)


(If you don't have enough SATA ports for both disks, you can temporarily connect one disk through a USB-SATA converter. As mentioned before, Storage Spaces won't care. Yes, the transfer will be slower but it's going to be temporary anyway.)


Meanwhile, disconnecting a drive while it still contains data and letting the new one rebuild from parity isn't a great plan; it means risking data loss if another disk happens to actually fail during the rebuild. (That's similar to traditional RAID rebuilds.)


No comments:

Post a Comment

hard drive - Leaving bad sectors in unformatted partition?

Laptop was acting really weird, and copy and seek times were really slow, so I decided to scan the hard drive surface. I have a couple hundr...