58 minutes ago, dabl said:

EDIT: I am probably confused. After updating the Nvidia Driver plugin to 2026.05.01 running terminal, nvidia-smi reports driver version 575.51.02 so maybe that is ok.

Please downgrade to Driver 580.x and reboot.

1 hour ago, ich777 said:

Please downgrade to Driver 580.x and reboot.

Thanks for your help. A couple of questions:

Can you please list the basic steps to downgrade a driver version?

So Driver 580.x is earlier than 575.x?

EDIT: I see simply clicking on the icon for the plugin gets me into the settings to change things.

The settings are reporting the Quadro P2000 which seems good/correct and the revision I'm running. Do I really want Driver 580.x? Did you mean something earlier than 575.x?

Supported candidates: 470.256.02, 550.144.03, 565.57.01, 565.77, 570.144, 575.51.02
Recommended Driver: 575.51.02 (best-available)

Edited May 5May 5 by dabl

7 hours ago, dabl said:

Thanks for your help.

Please post your Diagnostics for further help since it seems you are not on the latest Unraid version.

7 hours ago, ich777 said:

Please post your Diagnostics for further help since it seems you are not on the latest Unraid version.

Thanks yes, I meant to mention that I was not on the latest Unraid version, my apologies.

Poking around some more it seems my jellyfin transcoding is not in fact broken and that what I was seeing was due to client side issues and everything seems to be working fine with the Recommended Driver 575.51.02

Reading between the lines I'm guessing previous unraid versions may not have an issue with the latest Nvidia Driver plugin but would be curious if it should be offering a higher revision 580.x driver

raid-01-diagnostics-20260506-0939.zip

I'm having trouble recently and believe it's due to the Nvidia driver. When I reboot my server it hangs on the boot up process (photo). When I hard restart it again, it boots us fine, but screen shows a lot of warnings related to Nvidia (photos). It runs fine, but appears my dockers can't access it like they were previously (i.e. Plex can't do HW transcoding, using CPU). Server has 3060ti installed. Running Unraid 7.2.5 with Nvidia Driver 2026.05.01/595.71.05. Any advice would be helpful.

5 hours ago, tusculumgolfer said:

I'm having trouble recently an believe it's due to the Nvidia driver. When I reboot my server it hangs on the boot up process (photo). When I hard restart it again, it boots us fine, but screen shows a lot of warnings related to Nvidia (photos). It runs fine, but appears my dockers can't access it like they were previously (i.e. Plex can't do HW transcoding, using CPU). Server has 3060ti installed. Running Unraid 7.2.5 with Nvidia Driver 2026.05.01/595.71.05. Any advice would be helpful.

I am getting those same errors. Mine are with the 580.159.03 driver. SMI not reporting any transcoding processes when i force transcode from Plex.

Rolled back to 7.2.4 and get same errors on boot.

asura-diagnostics-20260506-1509.zip

Edited May 6May 6 by Viperkc
added additional picture

On 5/5/2026 at 11:36 AM, trey81 said:

I am also still having the same issue with same troubleshooting steps as the fixed build post and your troubleshooting steps too.

Do I need to change how the GPU is passed through in the template?

I fixed my issue with containers not starting/not using GPU after updating Unraid to 7.2.5 and hopefully this can help others as well. It was sated in other posts, but I didn't understand at the time.

The container management switched to CDI (Container Device Interface). Which, what I've read, is a standardized way to expose hardware (GPUs... etc.) to containers and such. Looks like this update switched to this. Here's what I did to fix it:

1. Go to Plugins tab in the UI.

2. Click 'Check for Updates' and update Nvidia Driver if there's an update.

3. Reboot server

4. Once up and running, open a terminal and type the following the following into the terminal (Generates nvidia.yaml file):

nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml

5. Reconfigure the Docker runtime

nvidia-ctk runtime configure --runtime=docker --cdi.enabled

6. Go to Settings > Docker

7. Set 'Enable Docker' to No and click apply

8. Set 'Enable Docker' to Yes and click apply

9. Go to your container template that won't start/won't use your GPU

10. Click the Basic View toggle to switch it to Advanced View in the top right

11. Find the 'Extra Parameters' field

12. Enter in the NEW CDI format for your GPU into the 'Extra Parameters' field:

    --device=nvidia.com/gpu=all

After this, my containers worked and used my GPU again. I'm no expert and I cannot help beyond what I've typed here. The internet helped me understand this more. Hopefully you can get yours working, too.

Also, thank you to the developer, ich777. I use a lot of your tools and containers. Your work does not go underappreciated.

Edited May 7May 7 by trey81

15 hours ago, tusculumgolfer said:

I'm having trouble recently and believe it's due to the Nvidia driver. When I reboot my server it hangs on the boot up process (photo). When I hard restart it again, it boots us fine, but screen shows a lot of warnings related to Nvidia (photos). It runs fine, but appears my dockers can't access it like they were previously (i.e. Plex can't do HW transcoding, using CPU). Server has 3060ti installed. Running Unraid 7.2.5 with Nvidia Driver 2026.05.01/595.71.05. Any advice would be helpful.

9 hours ago, Viperkc said:

Sorry about that, you won't see those message anymore with the plugin update 2026.05.07, this was displayed by accident.

Where did you test that? In the browser or on a native app?

Does the card show up in your Plex transcoding settings?

Please post your docker run command.

It is a common issue that transcoding won't work if you force a transcode in the WebUI from Plex when using Nvidia Cards.

16 hours ago, dabl said:

Thanks yes, I meant to mention that I was not on the latest Unraid version, my apologies.

I don't support that old Unraid versions, please upgrade to version 7.2.5

However, I don't see any indication that the driver isn't working.

1 hour ago, trey81 said:

I fixed my issue with containers not starting/not using GPU after updating Unraid to 7.2.5 and hopefully this can help others as well. It was sated in other posts, but I didn't understand at the time.

Did you do a reboot also in between?

1 hour ago, trey81 said:

The container management switched to CDI (Container Device Interface). Which, what I've read, is a standardized way to expose hardware (GPUs... etc.) to containers and such. Looks like this update switched to this. Here's what I did to fix it:

Please try it without that "fix" since this is already in the plugin.

1 hour ago, trey81 said:

Enter in the NEW CDI format for your GPU into the 'Extra Parameters' field:

It should be actually okay to use the old way described in post 2 of this thread, or also --gpus all

1 hour ago, trey81 said:

--device=nvidia.com/gpu=all

1 hour ago, trey81 said:

After this, my containers worked and used my GPU again. I'm no expert and I cannot help beyond what I've typed here. The internet helped me understand this more. Hopefully you can get yours working, too.

If possible please try again after a reboot, since this seems a bit overcomplicated and it should now work right OOB.

4 hours ago, ich777 said:

Sorry about that, you won't see those message anymore with the plugin update 2026.05.07, this was displayed by accident.

Errors on bootup are gone - thank you

4 hours ago, ich777 said:

Where did you test that? In the browser or on a native app?

Tested with iOS app and also Nvidia Shield

4 hours ago, ich777 said:

Does the card show up in your Plex transcoding settings?

Yes I do see it in my plex settings under transcoding

I still don't see any processes found when i run smi on the plex docker.

Will test more later today and report back

Edited May 7May 7 by Viperkc

6 minutes ago, Viperkc said:

Errors on bootup are gone - thank you

These where no errors, just warnings, nothing to worry about.

7 minutes ago, Viperkc said:

I still don't see any processes found when i run smi on the plex docker.

Your docker run command?

7 minutes ago, Viperkc said:

I still don't see any processes found when i run smi on the plex docker.

Do you see the card in your Plex transcoding settings?

8 hours ago, ich777 said:

Your docker run command?

I have --runtime=nvidia under extra parameters

NVIDIA_DRIVER_CAPABILITIES = All

NVIDIA_VISIBLE_DEVICES - my device ID

Have been running this for 4+ yrs no issues

8 hours ago, ich777 said:

Do you see the card in your Plex transcoding settings?

Yes I do see the card in Plex settings

I just noticed that in the GPU plugin it does show processes and some transcoding - so maybe the only thing that is broken is the SMI just not showing the processes

I just had noticed high CPU usage once upgrading to 7.2.5 and just panicked thinking transcoding was not being done by my GPU and the CPU was doing it.

I know there are processes ATM.

Thanks for all your help on this. Now to figure out why my CPU usage is so high with 7.2.5 - pretty sure its not related to the Nvidia driver.

2 hours ago, Viperkc said:

I just had noticed high CPU usage once upgrading to 7.2.5 and just panicked thinking transcoding was not being done by my GPU and the CPU was doing it.

Probably backed in subtitles, these are a nightmare for your CPU.

2 hours ago, Viperkc said:

I just noticed that in the GPU plugin it does show processes and some transcoding - so maybe the only thing that is broken is the SMI just not showing the processes

Transcoding is actually Throttled by Plex, meaning it transcodes a batch, then ends the process, transcodes a batch and so on... in between you won't see any processes.

New plugin update is out. Does anyone know the proper steps to get it working again? Is it update then restart Unraid?

14 minutes ago, Nanuk_ said:

New plugin update is out. Does anyone know the proper steps to get it working again? Is it update then restart Unraid?

I don't understand.

1. Go to the Plugin page

2. Click Check for Updates

3. At the Nvidia Plugin click Update

4. Done

Nothing more needed.

However this update was a really small change which only changed a console output on boot.

If you have issues, please post your Diagnostics and what's not working exactly.

I'm trying to figure out if this is the right solution for me. I'm hitting a sw_power_cap even under ~50% load on my RTX 4000 running Ollama.

What would be right solution to fix this?

Running on unRAID 6.12.15 with the latest Nvidia driver 575.51.02

(I'm super new to managing my hardware down to this level so bare with me please)

On 4/22/2026 at 9:33 AM, fka said:

bin/bash

if [ "$2" == "prepare" ]
then
killall nvidia-persistenced
elif [ "$2" == "release" ]
then
nvidia-persistenced

echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control

fi

exit 0 

Edited May 8May 8 by d_buster

1 hour ago, d_buster said:

What would be right solution to fix this?

This is not an issue per se, this is just a power limitation from your card to not get damaged. However since it seems you are using Ollama this question would be best suited in the support thread from the container.

However as said, that's just normal and nothing to worry about.

The script that you've linked is for VMs and not needed when running applications in containers.

That makes sense, I appreciate the feedback.

The original reason why I ask is because the sw_power_cap triggers around 98-100 watt, the RTX4000 has a 160 watt TDP rating, I guess I expected throttling to kick on closer to 150 watt.

Updated without issue. Thanks guys!

I'm on a GTX 1050ti and no matter what I do, I can't get the plugin to download and install the v580.159.03 driver. I keep getting "Can't download Nvidia Driver Package v580.159.03". I don't know how to manually force it to install. I have tried to wget the file directly into the directory it looks in and it will verify the checksum and pass but still says it can't download (it even deletes the file for some reason). Running unRAID 7.2.6 with plugin version 2026.05.07

30 minutes ago, GoldenCyn said:

I'm on a GTX 1050ti and no matter what I do, I can't get the plugin to download and install the v580.159.03 driver. I keep getting "Can't download Nvidia Driver Package v580.159.03". I don't know how to manually force it to install. I have tried to wget the file directly into the directory it looks in and it will verify the checksum and pass but still says it can't download (it even deletes the file for some reason). Running unRAID 7.2.6 with plugin version 2026.05.07

How does the plugin page look like, do you have some php errors on there.

If you have php errros on the page please follow this procedure:

1. Remove the plugin

2. Reboot

3. Install the plugin again

4. Go to the plugin settings and select the 580.x driver and click Update & Download

5. Reboot

Diagnostics would also always help.

I've just update to 7.2.6 and got isseu with my plex container and nvidia p620. The container don't start anymore i had to remove the nvidia to let it start. I've tryesd to reinstall the driver ando also the aother trick indicate here but with not siccess anyone can help me?

Here is my error:

docker run
  -d
  --name='plex'
  --net='host'
  --pids-limit 2048
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Joshua"
  -e HOST_CONTAINERNAME="plex"
  -e 'VERSION'='public'
  -e 'PLEX_CLAIM'=''
  -e 'NVIDIA_VISIBLE_DEVICES'='GPU-1ec4894a-9a88-7038-922c-04c92d1742f6'
  -e 'NVIDIA_DRIVER_CAPABILITIES'='all'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:32400]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-logo.png'
  -v '/mnt/user/Show/':'/tv':'ro,slave'
  -v '/mnt/user/Movies/':'/movies':'ro,slave'
  -v '/tmp/':'/transcode':'rw'
  -v '/mnt/user/Video/':'/video':'ro,shared'
  -v '/mnt/user/appdata/plex':'/config':'rw'
  --runtime=nvidia 'lscr.io/linuxserver/plex'
42bca44bc77ea11a4fa5305ad54e5ba4bb88d753cd520f232f482b6511fce6e6
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 jailing process inside rootfs: open /proc/self/mountinfo: no such file or directory

Run 'docker run --help' for more information

The command failed.

Edited May 10May 10 by Alex_75

7 hours ago, Alex_75 said:

Here is my error:

Please post your Diagnostics.

i notice my zfs mirror get data corruption on both drive same file do mem test pass decide to downgrade from 7.2.6 to 7.2.5 the same thing happened lucky i have snapshot and backup problem solve when i downgrade from nvidia driver v595.71.05 to v580.159.03

bug product

• unraid 7.2.5-6

• zfs mirror with dataset

• nvidia driver v595.71.05

• RTX 4060

• copy new file or do zfs scub will report new data corruption

it's a silence data corruption no log no drive error only when i check zpool status -v cache

is this PCIe/ZFS I/O corruption bug?

Edited May 11May 11 by Gvon