domenicsabol

I was worried that the logs would might been flushed on reboot, but I wanted to keep the server off while I acquired and prepared (using a 2nd unRaid) the new disk. Lesson learned. I'm going to delete the diagnostics now since this can be resolved. Thank you again!!

Thank you for getting back to me so quickly! Attached is the diagnostics zip. small update - Emulated disk contents appear to be correct.

Hello all - I was running a parity check on my sever, and it stopped itself due to errors. I shut down the array and did a smart test on the affected disk, finding no errors and the report said healthy. The disk still has the red X and I am trying to figure out the next best steps. Because of when it failed, I am concerned that the parity will not be valid, and rebuilding the disk( I got another identically sized disk and pre-cleared it) might corrupt my entire array (60TB). Could someone help with the best practice for dealing with this? I have seen some things on the forums about this, but never when parity is potentially incorrect. Many thanks!