- Closed
This happened with 6.3.5. I'm sorry, I'm not going to upgrade unRAID while my array is in unprotected state, so I can only report this issue with 6.3.5.
I've had a power outage. After booting up, one disk was dead. I started the array, nevertheless. The missing disk is now being "emulated", which is nice. However, unRAID insisted on doing a full Parity check. Which makes no sense, whatsoever. I only have 1 Parity disk, and with one disk missing it means that a Parity check can't possible do any good. So unRAID shouldn't insist on doing a Parity check. Maybe unRAID should even disable the option to run a Parity check manually?
Should be easy for you guys to check if this was already fixed in the latest unRAID build or not.
It's not a dramatic problem, but it's more than an "Annoyance", because any disk accesses while the array is unprotected is "dangerous". So insisting on doing a useless full Parity check in this situation is a really bad idea, IMHO.