July 27, 20241 yr I just replaced my flash drive (no issues there). While the flash drive was in read-only mode, I had a drive fail in my array. When I booted up, the array was labeled as "new configuration" or similar. Sure enough - 2 drives in the array weren't assigned correctly. So, I go to new config and hit the wrong button. It wants to rebuild the parity from scratch, which means that I'll lose the data on the drive that failed (new one is shipped). Is there any way to reload the array & pool config before it makes any changes? Will marking the "Parity is valid" checkbox before I start the array save it? All drives are in the exact same location, physically and in the config. The only drive not showing up at all is the one that died on me overnight. It won't let me assign the original drive to that slot because it's physically dead - won't read at all.
July 27, 20241 yr Community Expert 50 minutes ago, malaki86 said: I just replaced my flash drive (no issues there). While the flash drive was in read-only mode, I had a drive fail in my array. When I booted up, the array was labeled as "new configuration" or similar. Sure enough - 2 drives in the array weren't assigned correctly. So, I go to new config and hit the wrong button. It wants to rebuild the parity from scratch, which means that I'll lose the data on the drive that failed (new one is shipped). Is there any way to reload the array & pool config before it makes any changes? Will marking the "Parity is valid" checkbox before I start the array save it? All drives are in the exact same location, physically and in the config. The only drive not showing up at all is the one that died on me overnight. It won't let me assign the original drive to that slot because it's physically dead - won't read at all. Do you have a replacement drive assigned to the slot of the drive that failed? You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.
July 27, 20241 yr Author 2 minutes ago, itimpi said: Do you have a replacement drive assigned to the slot of the drive that failed? You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog. No diagnostics because the drive is physically dead. I don't have a replacement yet. The main issue was that I did the config wrong by having it not preserve the drive assignments.
July 27, 20241 yr Community Expert 3 minutes ago, malaki86 said: No diagnostics because the drive is physically dead. I don't have a replacement yet. The main issue was that I did the config wrong by having it not preserve the drive assignments. The diagnostics are a system level thing, not a drive level one. Having them allows us to see the current state of the system. You will not be able to bring the attach back as you want until you have a physical drive that can (temporarily at least) be put in place of the the failed one.
July 27, 20241 yr Author Solution I just started the parity rebuild. Sonarr & Radarr have some work to do, I guess.
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.