December 26, 20241 yr Hey there everyone. I have been running into an issue with my server for several weeks or maybe even months now where my parity scan will just slow down to a crawl and causes my server to become unstable/unresponsive. Normal parity check speed is around 250MB/sec and shortly after starting(sometimes 3%, 5%, or 7 %. Its inconsistent) the speeds drops to KB/sec and never speeds up again. It continually but slowly drops and wont proceed. When this happens, some of my docker containers will crash while others remaining functioning. The ones that crash and the ones that work seem random between instances of this. Sometimes Plex crashes, sometimes its fine. I do have VMs but they are always off until I need to manually turn them on which is very rare and I haven't been using them when the parity check stops. I cannot cancel or pause the parity check. I cannot shutdown or reboot from the webUI or via "shutdown now" in command line and I end up having to force shutdown with the physical power button on the server. It seems as long as I don't run a parity check, the server works just fine. I have tried to run a disk speed test and all my array disks seem to be running at their usual speed but ran into speed gap detections on my cache SSDs so couldn't complete those. No SMART errors on any of my drives. I just finished extended SMART tests today. I have run memtest and found no issues with my RAM either. I'm kind of at a loss here. Any ideas what might be causing this? I do see some error about CPU tainted and call traces but have no idea what to make of them. Diagnostics attached. neonexusur-diagnostics-20241225-2310.zip
December 26, 20241 yr Community Expert Solution Unraid driver is crashing, this is almost always a hardware problem, RAM is the typical main suspect, CPU would also be in this case, since it's one of the most affected by the Intel 13/14 gen issue.
December 26, 20241 yr Author 3 hours ago, JorgeB said: Unraid driver is crashing, this is almost always a hardware problem, RAM is the typical main suspect, CPU would also be in this case, since it's one of the most affected by the Intel 13/14 gen issue. Thank you for that. I think I have a spare CPU lying around so I will try to swap it out.
December 27, 20241 yr Author Looks like it was the CPU. After swapping it out, I'm not at 45% through a parity check. Thank you!
.thumb.jpg.15d158039cb566ddee9b77f92ecb4bd3.jpg)
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.