February 11, 20251 yr After upgrading to version 7, I am experiencing very frequent server locks. One even lasted longer than a week, and then the server came back online. Sometimes, Docker containers continue to run, but the web GUI is not available. Sometimes, everything is unreachable. Most of the time, SSH is not available. Tailscale is showing as online but unreachable. I have not made any configuration changes from version 6, which ran for months without any issues. I have tried open-source Nvidia drivers instead of the default ones. I believe I am on IPvlan and have the latest patches. The behaviour was the same during 7 betas and RC. Earlier today I had a hard lock which eventually resolved, and just now I had one that was semi hard, meaning that i could see open dashboard, but other pages would not load. I could access SSH, however: Prior to killing docker (semi hard lock I describe above): After reboot: CPU usage looks quite high with no VM or docker running. Any ideas where to look? tower-diagnostics-20250211-1554.zip
February 12, 20251 yr Community Expert Does it happen when you do some kind of operation, like a backup or any other high i/o situation? Also, there appears to be container(s) constantly restarting during several hours every day, is that expected? Check their uptimes.
February 12, 20251 yr Author 59 minutes ago, JorgeB said: Does it happen when you do some kind of operation, like a backup or any other high i/o situation? Also, there appears to be container(s) constantly restarting during several hours every day, is that expected? Check their uptimes. Thanks for your thoughts, as far as I can tell there is no pattern to it, and most of the time the server locks when I am not actively doing anything with it. I just think that CPU spikes and it feels like an out of memory issue, so something is starting to take up memory. The docker containers are restarting on purpose, to actually stop memory leaks, because the change detection container used to use a lot of RAM but with hourly restarts I don't observe that behaviour.
February 12, 20251 yr Community Expert Without anything specific logged difficult to guess what is causing the issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it doesn't crash like that start turning on the other services one by one, including the docker containers.
February 12, 20251 yr Community Expert Would also recommend enabling this, in case the server needs a little more RAM with the new kernel: https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down
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.