elbobo Posted November 22, 2021 Share Posted November 22, 2021 (edited) I made a terrible mistake, still unsure how I did it. Background: Dual Parity system previously 4TB drives, now 6TB, only 6TB in system are the parity drives Did a swap for Parity 1 - Copy Successful, rebuild successful Did a swap for Parity 2 - Copy Successful, rebuild currently running Get alert that Parity 2 has raw read error (in the thousands) - Odd for a new drive... This is where I discover my terrible mistake, I've accidently placed a drive that had 3.5 years of spin time on it from my other Unraid box instead of the new 6TB. At this point I have paused the rebuild of the previous Parity drive (now a disk in the array) because I don't think I should trust the Parity 2. What's the best way to resolve this with the least risk to data? Everything important on the array is offsite backed up... but if I can avoid bringing it back (and losing the unimportant stuff) I would like that. Should I (and can I even) pull parity 2 and restart the data-rebuild of Disk 4 (the swapped disk) then once that is complete, add a new 6TB drive as parity 2 and have that start it's process? Still unsure how this drive made it from my "destroy/recycle" pile back to the "on hand to swap if necessary" stack... I will be putting some failsafes in place to prevent that going forward. I cannot believe I did this... I am certainly kicking myself... Edited November 22, 2021 by elbobo Solved Quote Link to comment
trurl Posted November 22, 2021 Share Posted November 22, 2021 Do you still have the original disk4? attach diagnostics to your NEXT post in this thread Quote Link to comment
elbobo Posted November 22, 2021 Author Share Posted November 22, 2021 Diagnostics attached. No, the original disk 4 does not exist anymore. Thank you tower-diagnostics-20211121-2043.zip Quote Link to comment
trurl Posted November 22, 2021 Share Posted November 22, 2021 I think if you unassign parity2 you should be able to rebuild disk4 from parity since it is the only invalid disk. Quote Link to comment
trurl Posted November 22, 2021 Share Posted November 22, 2021 2 minutes ago, trurl said: I think if you unassign parity2 you should be able to rebuild disk4 from parity since it is the only invalid disk. If it won't let you do that for some reason, we have ways to make it. Quote Link to comment
elbobo Posted November 22, 2021 Author Share Posted November 22, 2021 Thank you for your help! I have unassigned parity 2 and restarted the array, it is rebuilding Disk4 and I am optimistic that this will be successful. Once it is done (and I get a new 6TB in) I will readd my Parity2 removing the unassigned drive and marring/tagging/disposing of it so this never happens again. Quote Link to comment
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.
Note: Your post will require moderator approval before it will be visible.