TheEyeTGuy

Apologies for the delayed update. Its been stable for the past several days, with 0 changes. I want to give it a couple more before I close it. But thanks for the support from both of you!

Thanks, I do have a local syslog server setup. I found where the logs are being stored and attached the ones from yesterday and today (rolls over at midnight). Cursory glance does not seem to show any detail of what may have happened. But I'll let more familiar eyes take a look Thanks for the quick reply! Logs.zip

Hi all, I've recently had my unraid server crash a few times this past week. Recent changes: new NVME drive installed. Flash drive replaced. I do not think the nvme drive is a culprit, as this was stable for well over a week after the install. After the first couple of crashes, I received a notice in the web ui that there appeared to be an issue with my flash drive. Then the server stopped booting entirely. Yesterday (4/29/25), I replaced it with a brand new drive restored from a backup downloaded from unraid connect (life saver btw!). This was around 11AM CT. At some point between 11:45 PM and 12:30AM CST the server went offline (Received an email alert that a scheduled google app script failed). Briefly tried troubleshooting around 8AM this morning, and noticed that it seemed to be locked up. (No ping, no web ui, no ssh, no display from HDMI). I had to hard power off and power on. I collected diagnostics but these were done AFTER the server came back online. I'm not sure they will contain any relevant information. I did turn off C-States a couple of years back when I moved to a ryzen based system, these should still be disabled to the best of my knowledge. dxsunraid-diagnostics-20250430-0846.zip

Perfect. I'll stick with what I know, haha. Thank you for the quick responses!

I have my docker containers log to loki/promtail. I was wondering if this would be the case. Interesting it was working prior to the upgrade. What do I need to add to it to make this work? Looks like the daemon.json should be the following: { "runtimes": { "nvidia": { "path": "/usr/bin/nvidia-container-runtime", "runtimeArgs": [] } } } So maybe a better way would be to use sed? I'm a complete novice to sed, but modifying what you gave a previous user, the below should work? sed -i '0,/{/a\ "debug": false,\n "live-restore": true,\n "log-driver": "loki",\n "log-opts": {\n "loki-batch-size": "400",\n "loki-max-backoff": "30s", \n "loki-url": "https://loki.darkxshadows.net/loki/api/v1/push",\n "max-buffer-size": "5m",\n "max-file": "5",\n "max-size": "5m",\n "mode": "non-blocking"\n },' /etc/docker/daemon.json

I'm having trouble after upgrading from 6.12.13 to 7.0.1. I keep getting an error that states docker: Error response from daemon: unknown or invalid runtime name: nvidia. I have uninstalled, reboot, and re-installed, reboot. Nothing seems to help. Here is the full output from trying to spin up a container (frigate): docker run -d --name='frigate' --net='dxsproxy' --ip='172.18.0.226' --pids-limit 2048 -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="DXSUNRAID" -e HOST_CONTAINERNAME="frigate" -e 'FRIGATE_RTSP_PASSWORD'='enterpassword' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-52a8c529-6891-5577-59e0-4b5aab1807c4' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/yayitazale/unraid-templates/main/frigate.png' -p '5000:5000/tcp' -p '8554:8554/tcp' -p '8555:8555/tcp' -p '8555:8555/udp' -p '1984:1984/tcp' -p '8971:8971/tcp' -v '/mnt/user/appdata/frigate/config':'/config':'rw' -v '/mnt/user/media/frigate':'/media/frigate':'rw' -v '/mnt/cache/swap/':'/swapfile':'rw' -v '/etc/localtime':'/etc/localtime':'rw' --device='/dev/apex_0' --shm-size=512mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --memory=8g --restart unless-stopped --runtime=nvidia 'ghcr.io/blakeblackshear/frigate:stable' docker: Error response from daemon: unknown or invalid runtime name: nvidia. See 'docker run --help'. The command failed. Nvidia-smi and diagnostics attached. Please let me know if you need anything else. nvidia-smi.log dxsunraid-diagnostics-20250309-2304.zip

Thanks for your response. Sorry if I offended you with some of my wording, did not mean any offense. Docker can't control memory either now though, which regardless of swap, I think is something that could be considered a bug. Cgroup stuff is also above my head. I appreciate your quick responses. On an unrelated note, is your source code published anywhere? I'd just like to poke around, for my own curiosity. Thanks!

If it does work, its not working for my docker containers, I can also confirm the docker container is not respecting its memory limit configuration (limited to 8 gigs, but uses more than that). Bug in 6.12.x?

Has anyone had success with swap working in 6.12? I've got a docker container that I use it for and I get the following when updating the container: WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.

*Bump*

Hello, I've very recently started getting out-of-memory errors on my Unraid server. And this morning I woke up to my HomeAssistant VM showing as 'Started' but inaccessible and throwing errors in VNC console (screenshot attached). Recent changes: Upgraded from 16GB RAM to 48GB Added Frigate as Docker Added a Coral Mini PCIe card. Added 2 new 8TB HDDs My assumption, is that Frigate is trying to use up all the RAM. I do have a Dell Optiplex 7010 with a 4th gen? i5 and 24GB of RAM that is currently unused. Would it be better to offload frigate to that? My diagnostics are attached. Thanks in advance! dxsunraid-diagnostics-20230531-0904.zip

I'm getting the same error. Just updated from 6.9.3 to 6.11.5 Everything else seems to be working ok.

I agree with the 3 of the above opinions: Search should be on the right hand side, Close should also be on the right and side of pop-ups Pop-ups should not cover the banner.