RTKing18

One of four RAM sticks had three errors. Currently running MemTest86 on the new RAM sticks. When I boot back into unRAID, I am assuming that I should run a non-correcting parity-check first and if sync errors are reported, then run a correcting check? Thanks again!

Quick update, Ran MemTest86 on the first stick twice with three errors total coming back. Assuming that is at least part of my problem, I have ordered additional RAM. Plugged all four RAM sticks back in to test them all bare-metal. If there is some benefit to doing one at a time I certainly can. I am assuming this issue could also be the reason for the kernel panics? Thanks for your help!

Good morning, I have removed all four sticks of RAM and I am currently testing each stick individually, bare-metal. Not sure if this assists in the diagnosis at all, but over the past month unRAID has had a few kernel panics as well. I have remote syslog setup but it hasn't been able to capture anything of interest.

Hi @JorgeB, sorry for the delay, has to get MemTest86 on a flash drive for secure boot. Results came back clean, 0 errors. Any additional thoughts or ideas? I looked through each drives SMART data as well, didn't see anything concerning there... 😕

Hi everyone, I have recently run into a problem where each time I run a parity-check, the system finds sync errors. I am running the parity-check with `Write corrections to parity` checked. Each run seems to find one or two errors less than the previous run, as seen in the screenshot below. I parity-check finished this morning, and I started another check. Not even 5% complete and it has found 5 sync errors already. I do not have any VM or Docker containers. I have also attached my unRAID Diagnostic logs. Any insight would be greatly appreciated. unraid-diagnostics-20230718-0916.zip