January 8, 20251 yr Hello everyone, I'm new to Unraid and servers in general, and my system has been working good until recently. During a routine parity check, I have experienced just over 6Million sync errors within in the first 10% of the check. I did recently update my 2 parity drives, and moved 4 disks to a LSI card early Dec. I precleared the parity disks twice and then when adding it to the array it precleared again and rebuilt the parity. I also did a scan after installing the lsi card and all the drives and everything was fine. I did smart tests on all the drives and they all passed, and did a memtest which also passed. I have attached 2 diagnostic files, first one from last night when the array was running, and another this morning when the array was stopped. Any help as to why this is happening, and how it can be fixed would be greatly appreciated. Thank you wandertower-diagnostics-20250108-1251.zip wandertower-diagnostics-20250107-2243.zip
January 8, 20251 yr Author 1 minute ago, JorgeB said: Any recent unclean shutdown? No, the server is also connected to a UPS. The only shutdown there was, when installing the new drives and lsi card back in Dec, which was clean.
January 8, 20251 yr Community Expert Solution Log is being spammed with the mover, unless you are having issues with that, better to leave mover logging disabled. Don't see anything out of the ordinary logged, you can try running a quick memtest to rule out any obvious RAM issues, if nothing is found, run a correcting check and then run another one to confirm no more errors.
January 9, 20251 yr Author Sorry about the mover, I was having issues a few months ago and forgot to turn the logging off. It is now off. I finished multiple passes of memtest, and all tests passed with 0 errors. I also ran smart tests on all drives and they passed. I have attached another diagnostics file. Parity check is still running. As you can see, there are a LOT of errors. The 4, 4TB drives are on a Supermicro AOC-S3008L-L8E 12Gbps SAS-3 HBA P16 IT mode for unRAID , purchased from art of server. I am not sure if this is causing the issue. I have no idea on how to check. I can provide another diagnostics file once the parity check is finished if that helps. The suggestion currently is to run a correction parity check, and then again without the correction and hope there are no errors. My question is, can the parity even be trusted after correction at this point? and how could something like this happen out of the blue? Also, from my understanding, parity check simply checks if the parity drive is accurate based on the array. This doesn't necessarily indicate file corruption, but more so something went wrong and the parity is wrong? thank you wandertower-diagnostics-20250108-2251.zip
January 9, 20251 yr Author quick update... I am not sure if I am understanding this correctly. But the errors are still growing passed the 4TB mark. As you can see the 4, 4TB drives are no longer active. Does this rule out the HBA card, as errors are still growing passed the 4TB drives that are connected to that card?
January 9, 20251 yr Community Expert 4 hours ago, Deathmoney said: My question is, can the parity even be trusted after correction at this point? If the 2nd check finds no errors, it should be OK, if it does, there's still an issue.
January 11, 20251 yr Author just updating my progress so far... The first parity check finished. I have attached the diagnostics file after the first check. As you can see it has found a lot of errors. No errors found beyond 10TB which is to be expected since the largest disk in the array is 10TB. Correction is now in progress. I noticed that its only writing to one of the parity drives and not both. Is this expected, or was only 1 of the drives out of sync? beforeCorrection-wandertower-diagnostics-20250110-0551.zip
January 11, 20251 yr Community Expert 2 hours ago, Deathmoney said: or was only 1 of the drives out of sync? I would expect it to be this.
January 15, 20251 yr Author Thank you @JorgeB and @itimpi I ran the correction and it corrected all the errors. I then ran another parity check and it found 0 errors. I don't know why this happened, either something messed up during the parity swap, or it was turbo write, as those were the only things I changed before the errors started. But everything is back to normal now!
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.