-
Followed Shrink Array process - now have blank device slots
Thank you trurl. Worked as you described. Ah, that makes sense now. Appreciate you helping!
-
Followed Shrink Array process - now have blank device slots
Well thank you JorgeB. But that's just too simple. I promise you, I would not turn off autostart for any reason. Having said that, it was set to No. So I changed it, and now it works. So I'm not worried about autostart anymore. Is there any follow up for the 3 disks/devices that are empty? Or just roll with the disks being labelled Disk 1, Disk 2, Disk 5, etc?
-
Followed Shrink Array process - now have blank device slots
Diagnostics attached. kellserv-diagnostics-20241028-1501.zip
-
Followed Shrink Array process - now have blank device slots
HI. Ran across an issue with Shrinking my array. History ..... I had a server with 16+ disks. The drives were smaller/older - around the 4-5tb era. About a year ago I decided to migrate to larger drives, so I can reduce the number of overall drives. I swapped in 2 new 16TB parity drives, and replaced several other drives over the last year. I followed the documentation, and all of that has gone well. Zero issues. I decided to shrik my array by 3 drives (4tb, 4tb, 5tb). This is the first time I tried that. I followed the online documentation: https://docs.unraid.net/legacy/FAQ/shrink-array/#the-remove-drives-then-rebuild-parity-method Everything seemed to go well. Parity rebuilt. Data seems in tact. However, I now have 3 empty slots in my array, and the array doesn't auto start after reboot because of it. I read over the documentation again, and there doesn't seem to be a step to 'move the drives up' to fill those vacant slots. But that seems to be what I need to do. Maybe by way of a New Config. And possibly selecting that the Parity is valid, so it doesn't have to do it again. But I defintely don't want to mess up any data, so I'm asking experineced experts how to proceed. Thank you.
4unraid
Members
-
Joined
-
Last visited