Zoidoid

Ever find a solution to this problem? I'm experiencing the same thing.

Yep having the same problem myself: tmpfs /run full - General Support - Unraid

I was trying to install a new Docker image and it was failing. Also suddenly seeing warnings around Unraid about a lack of free disk space: Warning: file_put_contents(): Only -1 of 100 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php on line 715 root@Tower:/var/log# df -h -t tmpfs Filesystem Size Used Avail Use% Mounted on tmpfs 32M 32M 0 100% /run tmpfs 7.8G 0 7.8G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 256M 45M 212M 18% /var/log Could someone kindly explain what /run is and why it might be full? I couldn't easily find anyone else who was experiencing this issue. Any help would be greatly appreciated. Thank you! EDIT: Seems like this is the culprit: /run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/f3e7a3a030a1d536b1147f7922564df9866fecca5a120a60d4330c4c263ae1fd# ^C root@Tower:/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/f3e7a3a030a1d536b1147f7922564df9866fecca5a120a60d4330c4c263ae1fd/log.json The log file isn't terribly interesting: {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:12-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:17-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:22-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:27-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:32-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:37-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:42-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:47-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:52-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:13:57-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:02-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:07-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:12-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:17-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:22-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:28-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:33-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:38-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:43-05:00"} {"level":"error","msg":"exec failed: write /var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/f3e7a3a030a1d536b1147f7922564df9866fecca5a120a60d4330c4c263ae1fd/.269433a179ee056127a893dee64e8f5c23120e57541a3105e974663c37885a31.pid: no space left on device","time":"2023-01-06T21:14:43-05:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-01-06T21:14:48-05:00"}

Thanks for this advice! Everything seems to be working as expected now. I didn't read the settings carefully enough originally. I didn't realize that selecting an option from the top few versions forced it to download rather than use the pre-downloaded version. Why the download failed is a little bit of a mystery to me -- I think it might be an order of operations thing where my network interface isn't ready by the time Unraid wanted to try to download the driver? Regardless, I'm happy for it just to use the perfectly-functional driver that's now on the usb stick. Appreciate the help!

Hello! I'm very new to Unraid so forgive me if there's something basic I'm missing here. I recently got everything set up and installed a Quadro P620 to use for transcoding with Plex. Everything was working fine! After I rebooted, however, I saw that the Plex Docker wouldn't launch any longer because of an invalid parameter call to load with nvidia support. Looking in the plugins tab, I saw that the Nvidia-Driver plugin was no longer listed as installed and under the Plugin File Install Errors, there was an entry with "/boot/config/plugins-error/nvidia-driver.plg." If I re-install the plugin, everything works fine until I reboot again. Any idea what might be going on? Attached diagnostics after my most recent reboot. Any help would be VERY much appreciated. EDIT: Was just looking through the logs. It looks like it realizes that it already has the desired version downloaded and installs it. Then after the NIC initializes, it attempts to download the driver again and fails. Would this lead to the situation I'm in? Any idea why this might be happening? tower-diagnostics-20220308-1349.zip

Oh, apologies! That explains why there is no button for creating a new topic. Didn't realize that's how the plugins support forum was meant to work. Stupid of me. I'll move the post there. Thanks!

Hello! I'm very new to Unraid so forgive me if there's something basic I'm missing here. I recently got everything set up and installed a Quadro P620 to use for transcoding with Plex. Everything was working fine! After I rebooted, however, I saw that the Plex Docker wouldn't launch any longer because of an invalid parameter call to load with nvidia support. Looking in the plugins tab, I saw that the Nvidia-Driver plugin was no longer listed as installed and under the Plugin File Install Errors, there was an entry with "/boot/config/plugins-error/nvidia-driver.plg." If I re-install the plugin, everything works fine until I reboot again. Any idea what might be going on? Attached diagnostics after my most recent reboot. Any help would be VERY much appreciated. EDIT: Just realized this line was in the logs. Any idea why? Also -- why is it trying to install the driver at startup? Shouldn't it already be installed? Mar 8 13:40:38 Tower root: Mar 8 13:40:38 Tower root: -------Main download URL not reachable, using Fallback URL------- Mar 8 13:40:56 Tower root: Mar 8 13:40:56 Tower root: -----ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR------ Mar 8 13:40:56 Tower root: ----Can't get Production Branch version and found no installed local driver----- Mar 8 13:40:56 Tower root: -----Please wait for an hour and try it again, if it then also fails please----- Mar 8 13:40:56 Tower root: ------go to the Support Thread on the unRAID forums and make a post there!------ tower-diagnostics-20220308-1349.zip