October 7, 20241 yr I recently upgraded an array drive. Running single parity. While the system was rebuilding the new drive, the parity drive died. Now my array won't start because the new drive wasn't finished being rebuilt. It's now saying invalid configuration. I still have the drive that was replaced. Since it hadn't finished rebuilding, is there a way I can put that drive back so I can start the array? Do I just swap them back and use the new config option?
October 7, 20241 yr Author I appreciate the help. Here is the current diagnostics. sohbackup-diagnostics-20241007-0902.zip
October 7, 20241 yr Community Expert Device Model: HUH721212ALE601 Serial Number: 8DJPJEHH Diags show issues detecting this disk, was this the old disk that was being replaced?
October 7, 20241 yr Author 8DJPJEHH was the "new" disk. it was a certified refurbished drive and is likely a bad drive. The parity drive is connected, but it is not being exported in the diagnostics so... double whammy. I tested both drives before attempting to add them and the parity drive has worked fine for a couple weeks now, but came back to it today after letting it rebuild the 8DJPJEHH drive overnight to find that the parity drive wasn't showing and the "new" drive didn't get rebuilt. The parity drive and the replacement drive are secondary concerns at the moment. I am trying to get the array started and was hoping I could swap that "new" drive (8DJPJEHH) with the original drive to get it going again. Nothing new would have been written to the array overnight. Then I could deal with everything else going on. I'm fairly sure I can use the new config option with the original drive in place, but I came here to make sure before I did it and screwed up my array further.
October 7, 20241 yr Community Expert Solution 22 minutes ago, themoodyhousehold said: I am trying to get the array started and was hoping I could swap that "new" drive (8DJPJEHH) with the original drive to get it going again You can do a new config: Tools - New config Recommend disconnecting the drive causing the issues.
October 7, 20241 yr Author 3 minutes ago, JorgeB said: Recommend disconnecting the drive causing the issues. 100%. I actually did this and then went back and reconnected everything like it was in the state I found it in before running the diagnostics, just in case. Thanks for the confirmation! Fingers crossed!
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.