- Minor
I tried searching around but couldn't find much on this. As long as I don't reboot Unraid, it won't have parity errors. Most recently, I ran the parity three times in a row without rebooting, and it reported 0 sync errors each time. I then rebooted (safely, stopping the array and then rebooting) and started another parity check, and now there are errors. I see a consistent 1025 errors on this particular Unraid box when errors do pop up, which is suspicious. Looking at the parity check history, there are only ever errors after a reboot.
Parity History, showing the last three runs had zero errors:
I then immediately rebooted and started another parity check, taking this screenshot:
This is a Supermicro motherboard with ECC RAM. Unraid is running as an ESXi 6.7 VM, with the Intel SATA controller passed through to the VM
I have a second Unraid server with the same setup (albeit newer hardware and newer ESXi), and it does something similar: 0 errors on repeated Parity Check operations, but the second I reboot and try to run a parity check, it'll start finding errors.
Both Unraid systems have been running as VMs for a few years, and did not always have this issue.
I've tried running New Permissions just in case something wacky happened to some of the files, but that did not help.
Diagnostics from both systems attached. The parity check errors can be seen in one of them. I can grab new/better diagnostics later if need be.
I'm looking for help in troubleshooting next steps, as this leaves me less confident in restoring valid data should a drive fail.
I did find this blog post https://blog.insanegenius.com/2020/01/10/unraid-repeat-parity-errors-on-reboot/ which has the same errors I did, "Jan 3 10:03:07 Server-2 kernel: md: recovery thread: P corrected, sector=1962934168"
but I don't think it's relevant in this case as I'm just using the SATA ports directly on the motherboards, without using any LSI or SAS/HBA cards.