PartyingChair

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.

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

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. I've attached them to this comment.

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.

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

It's now been over 12 hours, but 1) remote syslog server is already enabled and 2) I can pull the Diagnostics (and the server never actually went down - I just couldn't access the WebUI, docker containers, or VMs, They became unreachable but as far as I can tell never actually turned off). I have attached them here. I just don't know if it's too late since it was 12 hours ago. If it is, no worries, next time it happens I will absolutely do it quicker. megahub-diagnostics-20250701-1212.zip

Unfortunately, swap isn't an option if it requires btrfs. Without significant downtime, I have no way to switch it from xfs to btrfs to my knowledge. I'll look into options but it seems it's gonna be a pain, if possible at all.

My array is formatted as xfs. Cache is btrfs though.Also the plugin says its for 6.9 but I'm now on 7.1.4. Also: Just a gut check - I download a lot of stuff through qbittorrent and never have an issue so, although I really don't know, I'd be surprised in vnstat was killing it when everything else isn't.

Hello, I have an intermittent issue. It went away when I updated to v7 but now on 7.1.4 it is back. My server doesn't crash, but it does become completely unreachable (including docker containers, and VMs) for a period of time. Last night this happened from 8:50:33 pm to 9:05:29pm (logs from Home Assistant VM pinging unraid server attached as screenshot). During this time (including one log before and one log after), these are the logs: Jun 30 16:05:17 MegaHub sSMTP[3406899]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=788 Jun 30 20:59:01 MegaHub vnstatd[6004]: Warning: Writing cached data to database took 540.2 seconds. Jun 30 20:59:36 MegaHub vnstatd[6004]: Warning: Writing cached data to database took 31.7 seconds. Jun 30 21:03:27 MegaHub vnstatd[6004]: Warning: Writing cached data to database took 206.8 seconds. Jun 30 21:10:31 MegaHub vnstatd[6004]: Warning: Writing cached data to database took 330.5 seconds. Jun 30 21:14:26 MegaHub vnstatd[6004]: Warning: Writing cached data to database took 231.8 seconds. Jun 30 21:17:17 MegaHub vnstatd[6004]: Warning: Writing cached data to database took 136.9 seconds. Jun 30 21:45:33 MegaHub emhttpd: spinning down /dev/sdeWhen the server crashed, it was reporting ram usage at 86.2%, which I can't imagine is enough to crash the server. I have attached a photo of the graph of RAM at this time. Also, none of my drives seemed to be under heavy load. I do have 2 SMR drives, which are in the process of being phased out, so I am wondering if they could be the cause. However, they have no issues with SMART tests, and run perfectly fine during parity checks and mover operations. As of now, I have moved the vnstat.db to a specific share I hold on the cache, because idk.... seems like it's a smart thing to do if it is the SMR drives causing it. I'm not sure if there is anything else I can do/look into to see what is causing the issues. Any help confirming the issue/confirming the fix would be much appreciated.

Worked fine until it updated, can't get to the UI. Something broke. Container now stalls on "[info] NAME_SERVERS defined as....." Reverting to 5.0.3-1-01 got it working again for now.

Unfortunately, it's too late for that, been through many reboots, and now been 12 hours since it happened.

I made no config changes, but have been running into random issues. Now unraid itself and all dockers cannot see out into the world. Qbittorrent fails, jellyseerr fails, etc. if I try to ping 1.1.1.1 it just hangs. If I try to ping my gateway (10.52.3.1) it also just hangs. But Adguard home, running in br0, works fine. It can access the outside internet. Home Assistant VM can access the outside internet. Can anyone help point me to where the issue may lie? Thanks FIXED: Updating OPNsense fixed it. Not totally sure why, but it did.

Hey. Every once in a while, I suddenly can't access the unraid GUI, and all my dockers go down. Vms stay up. Often requires a restart to fix. Today that happened, and I finally caught some logs. The only logs around the time of this were: Dec 30 18:38:28 MegaHub php-fpm[13470]: [WARNING] [pool www] child 31144 exited on signal 9 (SIGKILL) after 23.052175 seconds from start Dec 30 18:38:55 MegaHub php-fpm[13470]: [WARNING] [pool www] child 31588 exited on signal 9 (SIGKILL) after 27.041666 seconds from start Dec 30 18:39:19 MegaHub php-fpm[13470]: [WARNING] [pool www] child 32006 exited on signal 9 (SIGKILL) after 17.648719 seconds from start Does anyone know what this is or how to fix it? I have set up a (hopefully) bandaid solution just now of having unraid restart once per week, but I'd rather get this fixed properly if I can Thanks

I just tested in another browser, I guess it's an issue in safari because it works fine in Chrome/Firefox. Would love for it to work in Safari if anyone knew what the issue was and how to fix it, but at the end of the day, not a deal breaker

In shinobi, when I click the drop down, it's just white. Not sure how to fix. Thanks