May 3, 20242 yr I've been using unRaid since 2012 and have swapped out countless drives over that time. My 4TB WD HDD hard drive is on the way out, so I decided to replace it with a new Crucial MX500 SSD, others of which I've had in my array for years. For some reason I'm getting an error that "the disc must be as big or bigger than the original" even though both are 4TB. Is there any way to have my unRaid OS work through this? In all these years and swaps I've never encountered this before.
May 3, 20242 yr Community Expert The problem will be that Unraid uses a different start sector for HDD and SSD (for performance reasons) so the SSD will have a few less sectors available for data than the HDD had. The only easy way around this that I can think off is to use the New Config tool to get the SSD into the array, rebuild parity, format the SSD, and then mount the old HDD drive via Unassigned Devices to copy its data back to the array. This would not be ideal as if the HDD failed during this process (and you do not have a backup of its contents) you could end up with data loss.
May 3, 20242 yr Author Yikes, that sounds scary...so I'm not missing anything, is it: Shut down array. Remove HDD, add SSD, reboot array. Add SSD to array via New Config tool. Rebuild Parity - I'm not technical so forgive me, but why wouldn't parity write to the new SSD at this time? I think this is the part of how parity works that confuses me the most; can't the array see the SSD as a new drive replacing a dead drive and use parity plus the other drives to rebuild? Or is this where the start sector issue becomes the issue? Format the SSD - I assume in the dashboard? Mount HDD to the array via Unassigned Devices - though if I'm already at my max SATAs I'm blocked here... Copy data back, meaning, rebuild the array again? Shut down, remove HDD, reboot?
May 3, 20242 yr Author 2 minutes ago, trurl said: SSDs in the parity array cannot be trimmed. Apologies, I do not know what that means. Did I refer to that in one of my steps?
May 3, 20242 yr Community Expert 18 minutes ago, tomorrowsman said: Apologies, I do not know what that means. Did I refer to that in one of my steps? No you didn't mention it. I just thought you might be unaware of this limitation. Apparently so. https://www.google.com/search?q=why+trim+ssds This is not allowed in the parity array since it might invalidate parity.
May 3, 20242 yr Community Expert 52 minutes ago, tomorrowsman said: Rebuild Parity - I'm not technical so forgive me, but why wouldn't parity write to the new SSD at this time? Rebuilding parity doesn't write to anything except the parity disk.
May 3, 20242 yr Community Expert 53 minutes ago, tomorrowsman said: Mount HDD to the array via Unassigned Devices Not really "to the array". That is why it's an Unassigned Device.
May 3, 20242 yr Community Expert 54 minutes ago, tomorrowsman said: Copy data back, meaning, rebuild the array again? No, just means copy. The Unassigned Device isn't part of the array. At this point the SSD in the array is empty. You just need to copy the data back to it from the Unassigned Device.
May 3, 20242 yr Community Expert 56 minutes ago, tomorrowsman said: Format the SSD - I assume in the dashboard? Main - Array Operation. Make sure the only disk listed for formatting is the new SSD.
May 3, 20242 yr Community Expert 41 minutes ago, trurl said: SSDs in the parity array cannot be trimmed. Also, SSDs in the parity array can only be written at parity speed. Both of these limitations are why SSDs are not usually put in the array. You have discovered another with your current problem.
May 3, 20242 yr Author 46 minutes ago, trurl said: No, just means copy. The Unassigned Device isn't part of the array. At this point the SSD in the array is empty. You just need to copy the data back to it from the Unassigned Device. So I remove the HDD from the array, add the SSD to the array, mount the HDD as a UD, then copy to the SSD?
May 3, 20242 yr Author At the absolute most raw level, couldn't I add the SSD to the array, rebuild parity, then remove the HDD and rebuild parity again, with no data loss? I know that is a super ham-handed way to approach the problem, but wouldn't it work, given none of the drives are greater than half the size of my parity drive? I'm asking about alternatives because I do not see any "Copy" function in any of the menus that would enable me to copy the HDD to the SSD, so I'm guessing it's something above my very low level of expertise. Edited May 3, 20242 yr by tomorrowsman
May 4, 20242 yr Community Expert 13 hours ago, tomorrowsman said: At the absolute most raw level, couldn't I add the SSD to the array, rebuild parity, then remove the HDD and rebuild parity again, with no data loss? I know that is a super ham-handed way to approach the problem, but wouldn't it work, given none of the drives are greater than half the size of my parity drive? You can, but you would still need to copy the data from one disk to another, and it will be much slower because of parity, and it's also important to know what this means: 16 hours ago, tomorrowsman said: My 4TB WD HDD hard drive is on the way out Please post the diagnostics first so we can see SMART for that disk, that makes it easier to give advice.
May 6, 20242 yr Author Thank you everyone for your help; I will start a new thread with I think a much simpler question!
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.