j.w.l

So based on what happened last time, I disabled spin down on the two parity drives by setting their 'Spin down delay' to 'Never'. However, when the parity check started for this month, Parity Disk 1 was disabled again. Parity Disk 2 remained in a normal state with no errors this time. It seems to only happen when a parity check is running, and not during normal operation. I've attached a new set of diagnostics. Any help would be appreciated again. Thanks. tower-diagnostics-20221202-0752.zip

Thanks! Just started the parity sync. I'll keep an eye on it and if any more issues arise, I'll try disabling spin down.

Hello, Today when I got up I was greeted with alerts from my Unraid server that 2 disks had read errors. One was my first parity disk and the other was one of my data disks. Apparently, the parity disk had enough errors that it was automatically disabled, while Disk 1 is still up and running. So I'm not sure if both drives decided to go bad at the same time or if something else is going on. I've attached my system’s diagnostics zip file as well. Any help with this would be greatly appreciated. Thank you. tower-diagnostics-20221021-0754.zip

Sure, here you go. TOWER-unassigned.devices.preclear-20220826-1926.zip

Currently running Memtest86+ and so far after 5 passes there have been no errors. Is there anything else that I can look into that may cause this error?

I just recently installed the UD Preclear plugin to run on a few new drives that I wanted to add to my array. No matter what options I select, I always get the following error on any of the new drives. RESULT: FAIL! /dev/sdd DOESN'T have a valid Unraid MBR signature!!! I'm running Unraid version 6.10.3 and have installed version 2022.08.19 of the plugin. Any ideas on what might be going wrong?