January 4, 20188 yr So. I had a 1TB drive fail. The drive was empty (no files at all) so no real problem at all. I replaced it with a 2TB drive and started the array, rebuilding etc. Within a few seconds the replacement 2TB was grumpy so I stopped the array to pull the drive out. Here's where things get nasty. I had another spare 1TB drive so I stuck that in. Added it to the original position and it now won't let me start the array as the system thinks the 2TG was the original one and now complains " The replacement disk must be as big or bigger than the original." I can mount the replacement disk in slot #4, leaving #3 blank and restart as a new drive, but that will leave slot #3 complaining about a missing drive. What's the best way to resolve this? The "New Array" option appears to be in the help things but that kinda worries me. Any thoughts? Ta. Robert
January 4, 20188 yr Community Expert Tools -> New Config -> Retain: All -> Apply Then go back to main and assign/unassign the drives as intended, data on data disks woun't be touched, parity will need to be re-synced though on first array start.
January 4, 20188 yr Just make sure you really have disk errors with that slot, so you aren't switching around disk-after-disk because you have a cable error.
January 4, 20188 yr Author 5 minutes ago, johnnie.black said: Tools -> New Config -> Retain: All -> Apply Then go back to main and assign/unassign the drives as intended, data on data disks woun't be touched, parity will need to be re-synced though on first array start. As per here? The "Remove Drives Then Rebuild Parity" Methodhttps://lime-technology.com/wiki/Shrink_array
January 4, 20188 yr Author 5 minutes ago, pwm said: Just make sure you really have disk errors with that slot, so you aren't switching around disk-after-disk because you have a cable error. Yeah. Checked that. Cables/interfaces appear fine. The 1TB got what appears to be a bearing squeal and the 2TB was and old drive from another system. Checking with Spinrite it appears to be very unhappy. Wish I knew that before attempting but hey....
January 4, 20188 yr Author Oh well, here goes.... 4 hours to rebuild. Not too bad. Edited January 4, 20188 yr by Wisnaeme Adding further details.
January 5, 20188 yr Author Ok. All done, we're back up and running with that failed disk allocation removed. NEW replacement disk purchased and on its way to me now. I will test it externally again before trying to install. Thanks for all the assistance.
Archived
This topic is now archived and is closed to further replies.