kwheel596

I continued looking into this today and came across https://github.com/NVIDIA/nvidia-container-toolkit/issues/102 I saw that Krusader was an issue previously. I use krusader about once a year and the initial reason I downloaded it (unrar abilities) I no longer need thanks to un-get. I removed the krusader container and no longer have any issues passing my GPU through to any other containers.

Recently, I needed to change some network settings. I disabled Docker, made my changes, and re-enabled Docker. Now any Docker containers that utilize my GPU (Nvidia RTX 2000 Ada 16gb) refuse to start. I get an error Execution error: Bad parameter pop up. I've done a few Google searches and even asked (cautiously) chatGPT for assistance. ChatGPT suggested to temporarily try starting Plex with the "--privileged" next to the already populated "--runtime=nvidia" but this also doesn't work (and has been removed). When attempting to change that variable I received the following error at the end of the docker run: docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: initialization error: open failed: /proc/sys/kernel/overflowuid: permission denied: unknown. The command failed. Again, various Google searches and more chatGPT lead me to do the following, all to no avail: 1: a-remove nvidia driver b-reboot server c-reinstall nvidia driver 2: (figured the order could matter here but no) a-remove nvidia driver b-reinstall nvidia driver c-reboot server 3: I have also followed spaceinvaderone's corrupt docker video that lead me to delete and recreate my docker image. Initially this provided errors stating that the 20gb vdisk size was full. There are probably some changes I could make to correct this but I assume they're unrelated to my issue at the moment. I increased the vdisk size limit to 55gb for now and those space errors went away but after re-installing all my containers, all the gpu-needy ones failed to start still 4: Rebooting the server, some of the gpu-needy containers are running (due to having auto-start selected) but not all of them. Plex, Jellyfin, Tdarr for example are all running. Ollama is not and trying to start it results in the same Execution error: Bad parameter pop up. The same error comes up if it try to restart or even stop/start any of the others I mentioned. Similarly after rebooting, the docker run still gives the same error about the nvidia-container-cli and a permission denied on /proc/sys/kernel/overflowuid. 5: Running nvidia-smi via ssh: 6: Viewing the permissions of the file thats mentioned to be denying permissions: Diagnostics attached. bananas-diagnostics-20250805-1459.zip

Thats my bad. I didnt look at it before updating and just went by date/time. Unfortunately, I never ran the command to generate more diagnostics and there were none generated automatically.

I believe this is the diagnostics file from the first boot.tower-diagnostics-20250211-1840.zip I updated to this just a bit ago.

I partially gave up on this venture due to pressure from others that use the features hosted by my server. I removed the USB from the server and put it in my computer and took a backup of the drive in its exact current state. From there, I found the 'previous' folder. I copied the entire contents to the base directory of the USB and put it back into the server and booted it up. It booted fine with no issues as if none of this ever happened, and back into 6.12.10. I'd still like to be able to go to 7.0 at some point.

While having Firefox open to the IP of the server on another monitor this is what I get. I have refreshed the page multiple times but still nothing in the phplog, not even a phplog generated it seems.

Tried this twice just now: I deleted the SERVER_unraid_bundle.pem from the flash drive and then manually stopped nginx and then started nginx via CLI, this generated another SERVER_unraid_bundle.pe but still the same 500 Internal Server Error. I deleted the SERVER_unraid_bundle.pem from the flash drive and then rebooted back into safemode. After booting into safemode, going to the IP in the browser gave a page cannot be displayed error. Logging back into CLI and received the following: root@banaNAS:~# /etc/rc.d/rc.nginx status Nginx server daemon is not running. I then tried to manually start nginx but again got the 500 Internal Server Error.

Not getting anything when I run that, maybe thats the issue?

It does get an IP, I am able to SSH into the server remotely. (I also have IPMI access to help troubleshoot as theres no monitor)

I am not able to access the webui via the IP in a browser, but if i launch Safe mode with GUI I do get a linux desktop. That opened a Firefox page automatically to https://localhost/ and it gets an "Unable to Connect" page.

Here are the safe mode diagnostics tower-diagnostics-20250211-1023.zip

Hi, I upgraded to Unraid 7 earlier today and all was well. I then tried to go through a cache drive swap process that I have gone through before and upon reboot I am no longer able to access the GUI. I typically get HTTP 500 or 503 errors via nginx. I was able to ssh in so I was able to restart PHP and temporarily receive a login prompt, but the HTTP errors persist after. I've attached the diagnostics .zip Any advice would be greatly appreciated. tower-diagnostics-20250210-2128.zip