I had 3 drives (WD 3TB, Seagate 4TB & 2TB) in external enclosures and decided to shuck them in order to put them in an external enclosure for a cleaner and leaner pool.
When I shucked them, I realised they didn't work without their controller (WD was encrypted and Seagates appeared as not initialised). I reconnected them to their controllers and I am currently copying the "poolpart" folders to a spare 8TB drive. When copying finishes I will do a clean disk operation from diskpart in order to make the original drives available to the enclosure and liberate them (sic) from their HW controller.
[Edited for clarity]
My question is: after cleaning the disks and copying back the "poolpart" folders, will Drivepool recognise them as if nothing happened? In other words, will the clean command affect volumeID?
Question
ZagD
I had 3 drives (WD 3TB, Seagate 4TB & 2TB) in external enclosures and decided to shuck them in order to put them in an external enclosure for a cleaner and leaner pool.
When I shucked them, I realised they didn't work without their controller (WD was encrypted and Seagates appeared as not initialised). I reconnected them to their controllers and I am currently copying the "poolpart" folders to a spare 8TB drive. When copying finishes I will do a clean disk operation from diskpart in order to make the original drives available to the enclosure and liberate them (sic) from their HW controller.
[Edited for clarity]
My question is: after cleaning the disks and copying back the "poolpart" folders, will Drivepool recognise them as if nothing happened? In other words, will the clean command affect volumeID?
Thanks!
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.