April 7, 20251 yr Just to spell it out for the next time: the GUI way would have been to leave it with 2 slots, unassign the first (smaller) drive (with a red cross in front as a missing drive), and then start the array (confirming that there is a missing pool device?). This would have automatically detached the smaller device and also reduced the GUI slot numbers, correct? EDIT: Just checked the release notes for 7.1.0-beta3 So I guess, the GUI way is not yet fully ready. Generally, it would be really nice, to perform such an operation (including resilver etc.) via choosing the new (larger) drive in the existing single drive slot for the pool. Unraid could then perform the temporary mirror creation, resilvering and detach of the smaller drive internally (with a progress notification). This way, Unraid would always know that it should treat this pool as a single drive vdev. Edited April 7, 20251 yr by HumanTechDesign
April 7, 20251 yr Community Expert 2 hours ago, HumanTechDesign said: Just to spell it out for the next time: the GUI way would have been to leave it with 2 slots, unassign the first (smaller) drive (with a red cross in front as a missing drive), and then start the array (confirming that there is a missing pool device?). This would have automatically detached the smaller device and also reduced the GUI slot numbers, correct? Correct, with 7.0.x there's an issue with btrfs pools, but still works with zfs.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.