9 minutes ago, kpwillis said:

Could someone please assist me.

Please read the first recommended post on top of this thread.

On 2/15/2025 at 3:10 AM, ich777 said:

I created an issue back then for this error on GitHub but it hasn't been an issue in a long time.

https://github.com/NVIDIA/nvidia-container-toolkit/issues/102

 

However I don't think that Nerd Tools is the culprit here and this is just a coincidence. Did you yet try to install another plugin and see if that fixes the issue too? Maybe its related so something completely different?

 

Do you use the your GPU in only one container or do you use it in multiple containers? If you are using it in multiple containers which containers?

 

Please also remove that script from your go file if you want to further troubleshoot since you are moving files for Docker around and maybe that's causing issues:

# -------------------------------------------------
# RAM-Disk for Docker json/log files
# -------------------------------------------------
# create RAM-Disk on starting the docker service
sed -i '/^  echo "starting \$BASE ..."$/i \
  # move json/logs to ram disk\
***line removed***
  mount -t tmpfs tmpfs /var/lib/docker/containers\
***line removed***
  logger -t docker RAM-Disk created' /etc/rc.d/rc.docker
# remove RAM-Disk on stopping the docker service
sed -i '/^  # tear down the bridge$/i \
  # backup json/logs and remove RAM-Disk\
***line removed***
  umount /var/lib/docker/containers\
***line removed***
  logger -t docker RAM-Disk removed' /etc/rc.d/rc.docker
# automatically backup RAM-Disk if Docker tab has been loaded (https://unix.stackexchange.com/a/198543/101920)
sed -i '/^<?PHP$/a \
if (file_exists("/var/lib/docker/containers")) {\
  exec("mkdir /var/lib/docker_bind");\
  exec("mount --bind /var/lib/docker /var/lib/docker_bind");\
  exec("rsync -aH --delete /var/lib/docker/containers/ /var/lib/docker_bind/containers");\
  exec("umount /var/lib/docker_bind");\
  exec("rmdir /var/lib/docker_bind");\
  exec("logger -t docker Created RAM-Disk backup");\
}' /usr/local/emhttp/plugins/dynamix.docker.manager/DockerContainers.page

 

 

Did you yet try another driver version? I just tested this exact driver version and the official Jellyfin container for example starts fine with the Nvidia Driver.

Thanks for taking a look at my post. I looked at the github issue but it seems like for that user, the problem went away by itself? I wish I was that lucky!

 

I removed that script in my go file and downgraded to nvidia driver 565.77 but the same issue occurs.

 

Quote

Do you use the your GPU in only one container or do you use it in multiple containers? If you are using it in multiple containers which containers?

I currently use my rtx 3060 ti in the following docker containers: whisper-asr-service, immich, plex.

 

Surprisingly, installing a different plugin (I randomly chose "AppData Cleanup") also fixes this issue - my containers (plex, immich, and whisper-asr-service) can start again as normal. I booted up Unraid, the containers failed to start with the same nvidia-container-cli error message, and then I installed the AppData Cleanup plugin (note I did not uninstall Nerd Tools this time, it is still currently installed). I then tried to start the containers again and they started up no problem. What the heck?

Edited February 19, 20251 yr by msalad
clarification

I'm on unRaid 6.11.5, updating to 6.12.10, and I got the following toast notifications:

I have not received the toast notification that it's safe to reboot yet.

I'm already on a higher driver version than 470.239.06, and I don't seem to have a corrupt plugin like some others in this thread have had. Here's a screenshot from my plugin settings page:


Any help would be appreciated.

2 hours ago, Eyeheartpie said:

Any help would be appreciated.

Uninstall the plugin, deactivate autostart from the array, install the plugin, enable autostrt from the array in the disk settings again and reboot again.

 

I would strongly recommend that you upgrade directly to 7.0.0

 

Please post your Diagnostics if you experiencing further issues.

my journey with this same issue.   

  Ive been banging my head on my desk for a month trying to figure this out. Even tried to just use a laptop with plex and unraid on it as a stop gap. I see the same issues on the laptop... (has a 1080) Ive tried to blow away my build and start over (kept array) and still no luck. Ive been using unraid for about 8 years and i have neve had these issues and it has worked properly for years until now.

Edited February 21, 20251 yr by radly82

3 hours ago, ich777 said:

Uninstall the plugin, deactivate autostart from the array, install the plugin, enable autostrt from the array in the disk settings again and reboot again.

Do I reboot in between deactivating autostart and then re-installing the plugin?

 

3 hours ago, ich777 said:

I would strongly recommend that you upgrade directly to 7.0.0

I already started the upgrade process to 6.12.10. Am I able to override this with an upgrade to 7 if I just run it again? Or am I stuck on the upgrade path to 6.12.10?

3 hours ago, ich777 said:

Please post your Diagnostics if you experiencing further issues.

EDIT: Did the above process with a reboot after uninstalling the plugin and deactivating the autostart. Seems to be working as expected now. I'll keep an eye on it when I move up to the 7.0.0 to see if I have similar issues.

Edited February 21, 20251 yr by Eyeheartpie

3 hours ago, Eyeheartpie said:

Do I reboot in between deactivating autostart and then re-installing the plugin?

Just do it in the order that I said above.

 

3 hours ago, Eyeheartpie said:

I already started the upgrade process to 6.12.10. Am I able to override this with an upgrade to 7 if I just run it again? Or am I stuck on the upgrade path to 6.12.10?

I‘m not sure but you can upgrade to 6.12.10 and then to 7.0.0

 

The upgrade process should just work fine from 6.12.10 to 7.0.0 as long as you wait for the notification that it is safe to reboot from the plugin update helper.

 

Hope that helps.

4 hours ago, radly82 said:

my journey with this same issue.

What are you referring to?

 

However I already answered here:

 

Hey @ich777, do you have anymore insight into my nvidia-container-cli issue above? It now does seem unrelated to Nerd Tools plugin since I found that I can install a different plugin to fix the issue too. I'm just not sure where to go from here. Having to install/uninstall a plugin after every reboot and then manually start the affected containers isn't ideal for long term

5 minutes ago, msalad said:

It now does seem unrelated to Nerd Tools plugin since I found that I can install a different plugin to fix the issue too. I'm just not sure where to go from here. Having to install/uninstall a plugin after every reboot and then manually start the affected containers isn't ideal for long term

Do you have any custom user scripts, third party packages, custom scripts or entries in the go file which maybe cause this?

Do you have any plugins installed that are maybe not supported, maybe a plugin is causing this?

Do you modify the /tmp directory in a Docker container or do you overwrite anything in there?

 

Sorry these are just wild guesses since it seems rather strange to me because it‘s not working on your system where it should work right OOB since it works on my test system and probably all orher users that use the Nvidia Driver plugin.

If plex thumb generator script is running while it tries to update, it causes this crash;

 

And I can't stop the thumb gen container (although it contiues to run normally it seems.) I have to disable docker, reboot, then it works fine. but i've noticed it happens during every update.

16 minutes ago, sunwind said:

If plex thumb generator script is running while it tries to update

What is the Plex generator script and what do you mean with update?

 

16 minutes ago, sunwind said:

but i've noticed it happens during every update.

What container are you using, Repository?

 

Diagnostics would also maybe help from after a "crash".

So i have reinstalled the Nvidia plugin after an issue with the driver and the latest NVIDIA Drivers & Rebooted the machine and turned the docker service on and off.

None of my containers that have been previously setup (and working) are using the GPU for transcoding Immich, Unmaninc, Plex and so on.

The device is correctly detected and showing up in the Itop plugin and in the system devices are showing correctly (Now)

Ive been looking for hours and nothing i do seems to be working, has anyone else has this issue since the upgrade or has any ideas on a fix!

tower-diagnostics-20250304-0754.zip

8 minutes ago, Rkpaxam said:

None of my containers that have been previously setup (and working) are using the GPU for transcoding Immich, Unmaninc, Plex and so on.

Are the containers starting?

 

8 minutes ago, Rkpaxam said:

Ive been looking for hours and nothing i do seems to be working, has anyone else has this issue since the upgrade or has any ideas on a fix!

I just tried it on my test server and everything seems to work fine.

 

9 minutes ago, Rkpaxam said:

So i have reinstalled the Nvidia plugin after an issue with the driver and the latest NVIDIA Drivers & Rebooted the machine and turned the docker service on and off.

From your Diagnostics I see nothing obvious, did you change the hardware or anything similar?

How do you check if the transcoding/machine learning is not working?

2 minutes ago, ich777 said:

Are the containers starting?

Everthing as normal 

2 minutes ago, ich777 said:

I just tried it on my test server and everything seems to work fine.

 

From your Diagnostics I see nothing obvious, did you change the hardware or anything similar? Nothings changed other than moving to 7+

How do you check if the transcoding/machine learning is not working?

Shows me on the main page what apps are using the gpu

 

3 minutes ago, Rkpaxam said:

Everthing as normal 

Then the runtime seems at least to be running/working fine.

 

3 minutes ago, Rkpaxam said:

Shows me on the main page what apps are using the gpu

Does Plex/Unmanic transcode anything or do you get a error message?

Please try to open up a terminal from Unraid and after that issue that command:

watch nvidia-smi

Leave the terminal open and start a transcode in Plex/Unmanic.

 

ATTENTION: Please make sure if you are forcing a transcoding you are doing it from a native App like Plex for iOS or Android, the Windows and Web Plex Client are known to just display a black screen after forcing a transcode in combination with Nvidia.

Hi, i was wondering if there were any issues with new 50 series graphics cards and this plugin. I tried to install the plugin and the latest drivers, but my gpu is not showing up. I have a 5070 ti and I do see it in the system devices too. Also, when i try to run nvidia-smi, it also says no devices found.

2 hours ago, c625v12 said:

I tried to install the plugin and the latest drivers,

did you try with the open source drivers ? i think rtx50 only works with opensource drivers

6 hours ago, c625v12 said:

50 series graphics cards

As @alturismo already said, 50 Series GPUs only support the OpenSource version.

Anyone having issues with Emby server and transcoding? This used to work perfectly for me but now it just fails to start any video stream if transcoding is required. The FFMPEG log that Emby generates shows it selecting the Nvidia card etc. but then just fails seemingly with no actual error.

 

I've tried the official Emby dockers and also the linuxserver versions and both fail the same way. I can see from the nvidia-smi output that ffmpeg at least attemps to start transcoding 3-4 times and then fails.

Edited March 5, 20251 yr by allanp81

1 hour ago, allanp81 said:

I've tried the official Emby dockers and also the linuxserver versions and both fail the same way. I can see from the nvidia-smi output that ffmpeg at least attemps to start transcoding 3-4 times and then fails.

Please post your Diagnostics.

40 minutes ago, ich777 said:

Please post your Diagnostics.

 

server-diagnostics-20250305-1145.zip

1 hour ago, allanp81 said:

 

server-diagnostics-20250305-1145.zip 259.88 kB · 0 downloads

Something weird is going on.

 

You changed your GPU as far as I can see correct? Can you please try to use not the OpenSource drivers.

I've been trying all of the driver versions offered to me, none work but I've just done some testing with Jellyfin this afternoon and HW transcoding appears to be working fine so this looks like it's unique to Emby for some reason.

14 minutes ago, allanp81 said:

I've been trying all of the driver versions offered to me, none work but I've just done some testing with Jellyfin this afternoon and HW transcoding appears to be working fine so this looks like it's unique to Emby for some reason.

The last driver that you tried is definitely not working because it‘s the open soucre one.

 

However did you restart in between changing the drivers?

Please try to switch back to the latest driver, reboot and see if it‘s working again.