Hello,

unraid repeatedly went down over and over again. I could not access the UI at all but it seems the dockers I could sometimes, then not, then sometimes, then not. My VM stayd up the entire time, but we very slow. I have attached diagnostics here.

It's the middle of the night so I may not reply for a few hours, but wanted to get a head start on it. I've also attached the previous log separately since I can't find it in that zip, but I do have it. I have also added a screenshot of what netdata shows.

Note the final critical errors were me literally turning the computer off at the power switch because I couldn't even get in over ssh. So those are expected.

megahub-diagnostics-20250703-0450.zip syslog-10.52.3.36.log

Edited July 3, 20251 yr by PartyingChair
added info

Jul 3 04:40:59 MegaHub php-fpm[13246]: [WARNING] [pool www] child 2577324 exited on signal 9 (SIGKILL) after 56.194516 seconds from start

Jul 3 04:41:01 MegaHub php-fpm[13246]: [WARNING] [pool www] child 2577650 exited on signal 9 (SIGKILL) after 16.726131 seconds from start

Jul 3 04:41:15 MegaHub php-fpm[13246]: [WARNING] [pool www] child 2577038 exited on signal 9 (SIGKILL) after 136.618679 seconds from start

Jul 3 04:41:20 MegaHub php-fpm[13246]: [WARNING] [pool www] child 2577724 exited on signal 9 (SIGKILL) after 16.575999 seconds from start

Jul 3 04:41:38 MegaHub php-fpm[13246]: [WARNING] [pool www] child 2577849 exited on signal 9 (SIGKILL) after 14.843157 seconds from start

Jul 3 04:42:05 MegaHub php-fpm[13246]: [WARNING] [pool www] child 2578137 exited on signal 9 (SIGKILL) after 25.700162 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

My available RAM normally hovers around 2GB (I have 16GB total RAM) but it drops to 1GB during these moments. See attached screenshot. I could be wrong but I feel like 1GB free should be enough, and I worry that adding more RAM won't actually solve the problem.

I only have 1 VM and it is limited to 2GB of ram. I didn't know I could limit the ram on dockers, so will look into that.

Also will look into pinning CPU cores.

I have enabled the /boot/config/fastusr

My worry is the high I/O wait I saw, but my dockers and VMs are on NVMe SSDs.

Edited July 3, 20251 yr by PartyingChair
updating info

1 hour ago, PartyingChair said:

I could be wrong but I feel like 1GB free should be enough

It should, but in my experience, at least sometimes it's not.

Can you screenshot a list of your docker containers.

33 minutes ago, JorgeB said:

It should, but in my experience, at least sometimes it's not.

My worry with that though, is instead of going from 2GB down to 1GB, it's going to go from 5GB down to 1GB and still crash. It seems to just completely plummet at that point. I am happy to buy more RAM if it will fix my issue, but if it doesn't, I really don't want to spend that money.

24 minutes ago, MowMdown said:

Can you screenshot a list of your docker containers.

I've attached them to this comment.

Edited July 3, 20251 yr by PartyingChair
clarity

I found this, sde having a max disk wait of 8.3 seconds. That is my parity drive. Could that be the culprit?

And update again, now I found this, which points to my NVME drive causing it. I'm very confused

The extended smart test passed with no issues for the NVME, and is currently running for the parity drive from the above screenshot.

Edited July 3, 20251 yr by PartyingChair