At the start of last week, I upgraded the Unraid OS from 6.10.3 to 6.11.5.
Other the next few days I did some extra tasks. I added a second cache pool with an NVME drive.
I added a VM running Win10 with a GTX1060, which pointed to the NVME drive.
I changed my RAM from the default 2100mhz to XMP native 3600mhz speeds.
My parity check runs on the last Friday of every month and Saturday morning, my server was on but the UI was inaccessible. I rebooted and started to run the parity check. A few hours later, it had frozen up again. I another try and another crash, I noticed that you would see from the dashboard there was an issue, as after an hour a few cores would lock to 100% and the time left of the check would freeze.
I read over the forums and saw someone had an issue kind of like this in the past. It was determined there was a hardware issue… so I started rolling back and trying a parity check after each step. As you can guess this took all weekend.
Blew away VM, still crashed on parity check.
Removed NMVE Cache pool, still crashed on parity check.
Rolled back XMP, still crashed on parity check.
Lastly… rolls back the OS. This seems to have worked, I have about three hours to go until it is complete.
Anyway, it would seem as if the OS was the issue, but is there a way I check the points of failure?
The parity check says there are 90 sync errors, I unticked the box to correct them because I don’t know what they are. Can untick correction by default?