Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Plugin] Nvidia-Driver

Featured Replies

I’m getting error notifications from the nvidia plugin

 

Quote

unRAID Server: Notification
 

Link: https://Brunnhilde.dahoney.me/Settings/nvidia-driver

Event: Nvidia Driver
Subject: Notification
Description: Found new Nvidia Driver v570.133.07 but a download error occurred! Please try to download the driver manually!
Importance: alert
 


But when I go to the plugins tab and try to manually download I get a popup showing that the updated plugin has already been downloaded.

 

IMG_0300.thumb.png.091bf9fc6a8b445e2b5d003d13d27939.png

  • Replies 5.9k
  • Views 1.1m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • To utilize your Nvidia graphics card in your Docker container(s) the basic steps are:   Add '--runtime=nvidia' in your Docker template in 'Extra Parameters' (you have to enable 'Advanced

  • Recompiled the drivers and they are now just working fine (to get it working scroll down):   Please do the following (this is only necessary if you upgraded before I recompiled the dri

  • I'm currently spinning up my build VM and compiling the drivers again, currently drivers for 6.11.0 stable are not available...

Posted Images

  • Author
1 hour ago, wgstarks said:

I’m getting error notifications from the nvidia plugin

Please try to remove the plugin entirely (you containers will still work as expected) and then install the Nvidia Driver plugin from the CA App again and see if you get the same error?

fyi on my problem. `modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.6.78-Unraid`

I ended up installing a fresh unraid while keeping all my disks, shares, docker containers, etc. The problem magically disappeared. I updated my bios to most recent before doing this, but it had no effect. Everything works as expected now.

@ich777, @alturismo, thanks for the diagnoses aid. Its always nice to have a forum to bounce around ideas in.

EDIT: Oh yeah, there was no overclocking set on the motherboard. It was all on "auto". So, as compatible/stable as I can see it being. That said, it is an 

ASRock motherboard. Not the most stable brand AFAIK

Edited by pa77y

  • Author
49 minutes ago, pa77y said:

I ended up installing a fresh unraid while keeping all my disks, shares, docker containers, etc. The problem magically disappeared. I updated my bios to most recent before doing this, but it had no effect. Everything works as expected now.

This is really strange since I had another user with a similar issue not long ago and I couldn't explain why that was happening but it's good to know that this solved your issue.

Something must be interfering with the installation or whatever, I really don't know what could cause this.

 

However it's great that you've let me know and that your issues is solved!

Thanks for the reply.

So, I had the issue where my GPU would come alive for a moment then go back to sleep. (Again)

The RTX 4060 would start to transcode for a moment then go back to sleep then everything would fall back to the CPU.

 

I never got around to testing the P2000 but that cards dedicated to Tdarr for converting older formats to h265.

 

I found that if i commented out "nvidia-persistenced" from my Go file then everything started working perfectly....... on the latest driver too.

The 4060 is idling like it's suppoesd to but the P2000 keeps waking up and going back to sleep.

It states it's only idling at 20 watts but I think it can do better? Is there a way to send "nvidia-persistenced" to just the P2000?

 

EDIT, I commented out "nvidia-persistenced" because it's the only thing i could think of that was still poking at the driver.

Edited by AnnabellaRenee87

4 hours ago, AnnabellaRenee87 said:

Is there a way to send "nvidia-persistenced" to just the P2000?

yes, but be aware, nvidia is considering to drop this feature (at least thats calles the last years ;))

 

as sample, im using it to en / disable on VM Startup / Shutdown.

 

depending now on card from nvidia-smi output as sample for 2 cards

 

nvidia-smi -i 0 -pm 1

nvidia-smi -i 1 -pm 0

 

card 0 (1st card) pers mode enable

card 1 (2nd card) pers mode disable

 

so, -i (0,1,2,3,...) to specify which card, -pm to en/disable pers mode (1 enable, 0 disable)

  • Author
7 hours ago, AnnabellaRenee87 said:

So, I had the issue where my GPU would come alive for a moment then go back to sleep. (Again)

May I ask first which container are you testing transcoding with?

 

The only time that I hear from such issues is in combination with Plex and trying transcoding in the WebPlayer.

It's a known issue that the Plex WebPlayer shows just a quick transcoding process on the GPU and then either showing a black screen or falling back to the CPU transcoder when switching the quality and trying to force a transcode.

 

For proper testing you should use a Native Plex Client like the Android or iOS App and forcing a transcode there or try it with Jellyfin.

 

The transcoder log should/could also give more information about that <- but it's not always that obvious what the problem is.

 

2 hours ago, alturismo said:

yes, but be aware, nvidia is considering to drop this feature (at least thats calles the last years ;))

It has been finally deprecated with the newer drivers, I think starting with version 570+

I was testing with Plex on my phone while on 5G/LTE.

I was also testing with Emby and JellyFin (Yes i have all 3 runing because I'm a nerd)

Don't suppose you can keep the v565.77 drivers as legacy for the immedeate future? I ask because where Pascal is apparently going to be dropped at some point. I also need to find another single slot card (that I can afford) that can handle doing transcodes of a show from a totally legal place that may be in MP4 or AVI lol to H265.

  • Author
5 hours ago, AnnabellaRenee87 said:

Don't suppose you can keep the v565.77 drivers as legacy for the immedeate future?

Sorry but no, since these are really not legacy drivers, at least not now. 😅

 

6 hours ago, AnnabellaRenee87 said:

I ask because where Pascal is apparently going to be dropped at some point.

That‘s true but first they will be legacy drivers, I can‘t imagine that they drop these card immedeately but I also have to say these cards are now really old.

 

6 hours ago, AnnabellaRenee87 said:

I also need to find another single slot card (that I can afford) that can handle doing transcodes of a show from a totally legal place that may be in MP4 or AVI lol to H265.

Look at something like the Nvidia A400 or A1000

 

However the issue that you are experiencing is really weird since no one else reported such an issue and many more people have enabled nvidia-persistenced, do you already habe new hardware? Maybe it‘s related to the old hardware that you are running.

3 hours ago, ich777 said:
9 hours ago, AnnabellaRenee87 said:

I ask because where Pascal is apparently going to be dropped at some point.

That‘s true but first they will be legacy drivers, I can‘t imagine that they drop these card immedeately but I also have to say these cards are now really old.

 

HEY!  I'm really old, but I still get the job done.  😜

Hi, I recently got the Gigabyte 5060ti Windforce OC. I am able to boot into my unraid system and am able to get video output from the card. However, my nvidia drivers is showing me: "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." I'm running a Ryzen 7 3700x with a B450 Tomahawk Max Mobo. I'm not sure if the half PCIE slot from the 5060ti has anything to do with it or maybe I'm setting something in my bios wrong. I've attached how the GPU looks like for reference:

 

image.png.98f8a633bb4ca2665bf3a8d93a72b9e8.png

 

 

I searched around and it says to put it to PCIE gen 4, but my mobo doesn't have that option only up to gen 3. I also saw a reddit post to put it in gen 2 but that didn't work either.

Edited by jayryuki

  • Author
42 minutes ago, jayryuki said:

I searched around and it says to put it to PCIE gen 4, but my mobo doesn't have that option only up to gen 3. I also saw a reddit post to put it in gen 2 but that didn't work either.

Diagnostics would help a lot for such specific questions and to diagnose the issue properly.

 

However 5000 Series cards only work with the Open Source drivers, please select the Open Source driver, wait for the Download to finish and reboot your server.

1 hour ago, ich777 said:

Diagnostics would help a lot for such specific questions and to diagnose the issue properly.

 

However 5000 Series cards only work with the Open Source drivers, please select the Open Source driver, wait for the Download to finish and reboot your server.

Thank you so much, I must have missed the post about that. Thank you very much, it is working now! 

  • Author
16 minutes ago, jayryuki said:

Thank you so much, I must have missed the post about that. Thank you very much, it is working now! 

Glad that everything is working now, please include Diagnostics next time you got issues with a Driver plugin.

On 4/15/2025 at 4:10 PM, pa77y said:

fyi on my problem. `modprobe: FATAL: Module nvidia not found in directory /lib/modules/6.6.78-Unraid`

I ended up installing a fresh unraid while keeping all my disks, shares, docker containers, etc. The problem magically disappeared. I updated my bios to most recent before doing this, but it had no effect. Everything works as expected now.

@ich777, @alturismo,thanks for the diagnosdiagnosests always nice to have a forum to bounce around ideas in.

EDIT: Oh yeah, there was re was clocking set on the motherboard. It was all on "auto". So, as compatible/stable as I cas I c it bee it bein saTha it is an 

ASRock motherboard. Not the most stable brand AFAIK

I'm currently having the exact same issue as you (also on an asrock mobo) , all overclocking is disabled as I was fiddling with bios settings to try to hit deep idle cstates. Unfortunately for me this coincided with an update to rc1 so I'm not sure if it was the bios or the software update that caused it. Id really like to avoid doing a fresh unraid install.

servbot-diagnostics-20250423-2318.zip

Edited by sage2050

  • Author
4 hours ago, sage2050 said:

Id really like to avoid doing a fresh unraid install.

What is all of that in your go file:

cp /boot/custom/docker-shell /usr/local/bin

#copy mount scripts for each virtofs share
#Games
cp /boot/virtiofsd/games.sh /usr/libexec/games.sh
chmod +x /usr/libexec/games.sh

sed -i 's/$options\[\] = "--fd=".$argoptions\['"'"'fd'"'"'\];/if (isset($argoptions\['"'"'fd'"'"'\])) {\n    $options[] = "--fd=".$argoptions\['"'"'fd'"'"'\];\n}/' /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/virtiofsd.php 

 

Are you also really sure you need all of that:

BOOT_IMAGE=/bzimage pcie_acs_override=downstream,multifunction modprobe.blacklist=i2c_i801,i2c_smbus vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot

 

Please note that Unraid is not designed to be general purpose server, it's an app server so I'm also questioning these packages:

-rw------- 1 root root  448876 Jan  6 11:37 btop-1.2.13-x86_64-1_SBo_UES.txz
-rw------- 1 root root   60236 Dec 12 16:23 iotop-0.6-x86_64-14cf.txz
-rw------- 1 root root   14776 Jan  6 11:37 mktorrent-1.1_de7d011-x86_64-1_SBo_UES.txz
-rw------- 1 root root 1797248 Jul 17  2024 openssl11-1.1.1za-x86_64-1.txz
-rw------- 1 root root  207368 May  3  2024 powertop-2.15-x86_64-2.txz
-rw------- 1 root root  267728 Jan  6 11:37 unrar-7.1.2-x86_64-1cf.txz

 

Did you run at some point a custom Kernel?

 

 

Yes, it's exactly the same issue since the Nvidia driver package is found on boot by the plugin:

Apr 23 22:52:45 Servbot rc.local: --------------------Nvidia driver v575.51.02 found locally---------------------
Apr 23 22:52:45 Servbot rc.local: -----------------Installing Nvidia Driver Package v575.51.02-------------------
Apr 23 22:52:45 Servbot rc.local: --------------Installation of Nvidia driver v575.51.02 successful--------------

however this is basically not correct because the package should be installed way earlier in the boot process which is not done on your system which is exactly the same issue as for the previous user who reported that issue.

 

I really don't know by what this is caused, I can only assume something is messing with rc.modules (which is responsible for installing the 3rd party drivers early in the boot process).

i honestly dont remember what the docker-shell line is for, i will look into that,

edit: its from an ancient spaceinvader one video about bashing into a running docker container. it's probably no longer necessary.

 

the second script is a vm virtiofs trick thats now deprecated, the bootimage looks like old iommu separation that's now native to unraid, that can definitely be cleaned up.

 

those pkgs are tools from the now deprecated nerd pack that i use frequently (except openssl, i dont even remember what i needed that for) so I installed them myself, not sure why they would cause any issues.

 

ive never run a custom kernel, just betas and release candidates.'

 

the successful driver install you're seeing is possibly me removing the plugin and reinstalling it, as that's the only way to get it working after a reboot, like in pa77ys case.

Edited by sage2050

  • Author
1 hour ago, sage2050 said:

the successful driver install you're seeing is possibly me removing the plugin and reinstalling it

No, this is on plugin installation at boot and yes, I also saw that you reinstalled it later again.

 

1 hour ago, sage2050 said:

as that's the only way to get it working after a reboot, like in pa77ys case.

Sorry I really can't help, it seem like you are using a highly customized Unraid installation, not in terms of Containers or VMs since you have a lot of stuff which is now deprecated or simply not working anymore as you've pointed out above?

 

Are you also sure you don't run any User Scripts or something like that and also that your USB Flash device is working properly? Issue is that you have a lot of stuff on there which I really don't know why it's there:

/boot
total 1228160
-rw-------  1 root root   6220854 Apr  3 13:49 250403174920.BMP
-rw-------  1 root root   1440054 Apr 23 08:06 250423120618.BMP
-rw-------  1 root root   1440054 Apr 23 08:06 250423120627.BMP
-rw-------  1 root root   1440054 Apr 23 08:06 250423120628.BMP
-rw-------  1 root root   1440054 Apr 23 08:06 250423120629.BMP
-rw-------  1 root root   6220854 Apr 23 08:07 250423120730.BMP

you even have BMP files on your flash drive and other stuff which I really wouldn't put on there.

 

I really can't tell what the issue is, maybe try the following:

  1. Grab a USB Key (if you have one laying around)
  2. Install Unraid on there
  3. Boot Unraid from this newly created USB Falsh device on your Server
  4. Don't start the Array!!!
  5. Install CA App by clicking on Apps
  6. Download the Nvidia Driver plugin (yes this is working too if you don't start the Array)
  7. Wait for the Download to finish
  8. Reboot
  9. Log in again
  10. See if the driver was installed properly

After that you can shutdown the server and boot from your existing USB device as usual, the above is just for testing if a new installation would work and install the driver just fine.

well i updated my motherboard bios this morning and the problem went away 🤷‍♂️

  • Author
1 hour ago, sage2050 said:

well i updated my motherboard bios this morning and the problem went away 🤷‍♂️

Well… that‘s strange…

 

Glad to hear that it‘s resolved.

--------Nothing to do, Nvidia Driver v575.51.02 already downloaded!---------

------------------------------Verifying CHECKSUM!------------------------------

----------------------------------CHECKSUM OK!---------------------------------

root@unraid:~# nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

root@unraid:~# sudo modprobe nvidia
modprobe: ERROR: could not insert 'nvidia': No such devic

running with a RTX3070. This started happening after upgrade to 7.0.0, any ideas? 

  • Author
9 minutes ago, BoKKeR said:

running with a RTX3070. This started happening after upgrade to 7.0.0, any ideas? 

If you are willing to, please try to upgrade to Unraid 7.1.0-rc.1, this should hopefully solve the issue.

 

Diagnostics would also help.

Thanks thats good to know, will just wait it out

  • Author
2 minutes ago, BoKKeR said:

Thanks thats good to know, will just wait it out

Do you have Diagnostics since these would help me to understand what's going on?

I have now multiple reports about that issue and I'm not sure what the cause of the issue is.

 

BTW it would help a lot if you could upgrade and see if the issue is solved on 7.1.0-rc.1, you can also downgrade afterwards if you don't want to stay on 7.1.0-rc.1 <- this build is stable as always.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.