January 30, 20251 yr I have had a long blackout. I have a UPS which interfaces to unraid, and is supposed start a clean shutdown. I was not home but based on both parity drives showing disabled on restart I assume that is what happened. I did not have syslog server running, but after reading through threads here, I now do. Smart is fine on the disabled drives. I have had single data drives disabled before, and rebuilt ok. This is the first time I have had parity drives disabled, and can't find another thread that discusses both being disabled at the same time. They are a pair of 14tb drives, so will take a long time to rebuild, and I assume I now have an array without any parity protection, which is pretty crap considering I put the 2 drives in so I would not be in this position. I upgraded to V7 about a week ago if that makes any difference, it does look like it broke the UPS linking which I'll figure out. What is the best way to move forward from here? Bite the bullet and unassign one of the parity drives, re assign and rebuild, then the other or something different? Pete.
January 30, 20251 yr You can do a new config, check parity is already valid, then run a correcting parity sync, sync errors are expected, but the array should still be mostly protected.
January 30, 20251 yr 56 minutes ago, pete69 said: I have had a long blackout. I have a UPS which interfaces to unraid, and is supposed start a clean shutdown. Make sure you configure that to shutdown after a short blackout. The purpose of UPS isn't to allow you to continue to run on battery. The purpose is to allow it to run for very brief outage, and to allow a clean shutdown if power continues to be out for a short time.
January 31, 20251 yr Author 21 hours ago, trurl said: Make sure you configure that to shutdown after a short blackout. The purpose of UPS isn't to allow you to continue to run on battery. The purpose is to allow it to run for very brief outage, and to allow a clean shutdown if power continues to be out for a short time. Thanks it was previously set to shutdown at 80%, but the connection does not seem to be working after recent updates. I'll look into it when the parity issue is solved.
January 31, 20251 yr Author 21 hours ago, JorgeB said: You can do a new config, check parity is already valid, then run a correcting parity sync, sync errors are expected, but the array should still be mostly protected. Thanks, I'll give that a try.
February 4, 20251 yr Author Solution On 1/30/2025 at 10:50 PM, JorgeB said: You can do a new config, check parity is already valid, then run a correcting parity sync, sync errors are expected, but the array should still be mostly protected. I got scared with this option and ended up going the normal route, rebuilding each parity drive one at a time. But thanks for your help.
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.