Been having this issue for the past month or so. Starting unraid without docker seems to work fine (have not run it like this for an extended period). Starting docker is where the problems start. There hasnt been a pattern I've recognized but a few (2-3) containers will work fine but the more containers I start, the more unraid starts slowing down and feels sluggish until the whole system will hang and crash. Can't access the gui locally via ssh or webui, and cant access it directly through the computers output at that point.

I ran 2 x Memtests for 10 hours each (~20 passes) and found 2 out of 4 ram sticks were bad (2 separate kits, one kit went bad together). I ran the remaining two sticks for another 10 hours and no errors but the problem with unraid is still happening (I think something to do with corrupted data from my googling). I did get a "crc error count is 1" after removing the two faulty sticks on my cache drive but nothing since then.

diag.zip

Were the diags saved when you were having the issue?

Unraid crashed, I hard rebooted and then downloaded diagnostics. Since the UI freezes theres no way for me to download it during the problem so I'm not sure how to get more "up-to-date" diagnostics. Im gonna attach another earlier diagnostic, maybe something will show up in that one. All these downloads were after a crash.

clinton-diagnostics-20250806-2351.zip syslog-192.168.1.10.log

Enable the syslog server and post that after it happens again.

syslog server is active, I've posted the log above.

Missed that.

Aug 7 00:12:51 CLINTON php-fpm[10836]: [WARNING] [pool www] child 34299 exited on signal 9 (SIGKILL) after 88.168518 seconds from start

In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.

It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid.

Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

Made a crash happen again by trying to update a container, rebooted into safe mode and downloaded these.

clinton-diagnostics-20250807-1151.zip syslog-192.168.1.10_new.log

1 minute ago, JorgeB said:

Missed that.

Aug 7 00:12:51 CLINTON php-fpm[10836]: [WARNING] [pool www] child 34299 exited on signal 9 (SIGKILL) after 88.168518 seconds from start

In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.

It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid.

Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

Ok, I will try all of these things when I get home. I have 32GB ram on the way, so I'll let you know if that fixes it. Thanks for the help

On 8/7/2025 at 11:55 AM, JorgeB said:

In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.

Added more RAM and that fixed the issue, thanks