July 18, 20232 yr 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
July 18, 20232 yr Community Expert Those and btrfs detecting checksum errors can be due to bad RAM, start by running memtest.
July 19, 20232 yr Author 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... 😕
July 19, 20232 yr Community Expert Solution Try running bare-metal, with only one stick of RAM, if the same try the other one.
July 19, 20232 yr Author 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.
July 19, 20232 yr Author 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! Edited July 19, 20232 yr by RTKing18 Formatting
July 20, 20232 yr Community Expert 15 hours ago, RTKing18 said: I am assuming this issue could also be the reason for the kernel panics? Quite possibly.
July 20, 20232 yr Author 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!
July 21, 20232 yr Community Expert I would run a correcting check first since a few errors are expected then a non correcting to confirm all is well.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.