Only a few weeks into my Unraid journey, so apologies if I'm doing something wrong.

 

I ran a scheduled Parity Check Sunday (yesterday) (starting at midnight), when I woke up it was still running and had found 70 errors. I quickly went to the forums and found similar posts. Those posts noted that it is not good to have "Write corrections to parity" enabled for scheduled checks. I checked mine and found that it was enabled, so I stopped that scheduled check and ran a new one without Write corrections to parity.

 

When it finished it found 329 errors.

 

In looking at other posts and general research I found that a couple causes of parity check errors are failing disks and memory errors.

 

While migrating some drives from my old TrueNAS server to this new Unraid server, one of the old drives died. I do not believe it was ever a part of the array, if memory serves it died while I was trying to format it and get it ready for preclearing. I RMA'd the drive and the replacement is in the array and working fine.

 

To be cautious I ran a SMART test on all my drives, including both parity drives. All drives passed.

 

A few days into setting up the server, I did have an issue where one of my two RAM sticks stopped responding and Unraid essentially locked/crashed and required a hardboot to come back. I believe this most likely caused the parity errors.

 

For a few days (can't remember the exact timing), maybe a week, the server ran on one RAM stick only. I swapped the RAM sticks around and this got both sticks back up and running. There have been no issues since.

 

I ran Memtest this morning and it passed with no errors.

 

This is where I'm not sure how to proceed. I feel the server is fine, but I'm not sure if I should run another Parity Check and tell it to write the corrections, or if there is something else I should do. Any advice would be greatly appreciated!

If you are not sure of the state of the server you could try running another non-correcting check.   If there are no issues it should report the same number of errors (but you could skip this check if you think the server is stable) and you can then run a correcting check to fix them.   Note that a correcting check reports as ‘errors’ every one it corrects so you should get the same count again.   Future checks should then report 0.

Sounds good, I'll run one more non-correcting check just to be safe. Thanks for the advice! 

7 hours ago, scorcho99 said:

I guess I'll glom on to this one

It would have been polite to ask the OP first if they mind if you hijack their thread. Normally you should start your own thread, since causes and fixes are rarely identical even if the symptoms match. If the OP has further issues and gets advice, it could be harmful to your situation to follow that advice.

 

A read check at this point is pretty useless, but you didn't post enough info to really be helpful.

 

You didn't post your diagnostics, and you cut off the part of the screenshot that shows whether the emulated drive is mounted correctly.