On 12/20/2025 at 8:11 PM, DingusKahn said:

I keep getting this code reappearing in the syslog. It makes my nvidia card disappear and reappear every so often in my Unraid. Not sure what the cause is. This has persisted across different drivers and even different gpus (a 5050 with the open source driver). Not sure what the issue is or what the fix is

Most of the times hardware incompatibility, outdated BIOS or wrong set BIOS setting.

Please try:

1. Updating the BIOS to the latest available version

2. Enable Above 4G Decoding in the BIOS

3. Enable Resizable BAR Support

4. Put the line nvidia-persistenced in your go file (put it at the very end of /boot/config/go )

9 hours ago, ElementG8 said:

couldn't find many reports of how stable this GPU is under Unraid

Please do keep in mind that this has not strictly speaking something to do with Unraid, I was suffering from the same issues on my Linux Desktop PC with an RTX3080Ti and the ultimate issue was a wrongly set BIOS setting, at least in my case.

The GSP error could also be a hardware defect.

From what I see the card is listed as supported in the Supported Products tab here:

NVIDIA

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

5 hours ago, abhi.ko said:

Can anyone help resolve this please?

Please read this post:
https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/211/#comment-1593815

5 hours ago, abhi.ko said:

but I do get a notification saying there was an error and asking me to install the driver manually.

Is it possible that you have those two lines on your plugins settings page like in this post:
https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/178/#findComment-1487703

If yes please read the next post to fix your issue.

If you don't have those two lines in your plugins settings page then please make sure that nothing is blocking access to GitHub and also make sure to disable AdBlocking if you have it in place, your server needs exclusive access to the Internet without any AdBlocking.

If you have Unifi Network gear please also check the logs if it's blocking access to GitHub for your server.

11 hours ago, abhi.ko said:

Hello - after a recent update to 7.2.3 (from 7.2.2) i started getting this error. Diagnostics attached.

Can anyone help resolve this please?

Nvidia Info:

Nvidia Driver Version: 590.48.01

Open Source Kernel Module: No

Installed GPU(s):
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

GPU does show up still in the system devices, but I do get a notification saying there was an error and asking me to install the driver manually.

Nvidia Driver

Dec 21, 09:01 AM

Notification

Found new Nvidia Driver v590.48.01 but a download error occurred! Please try to download the driver manually!

OMMU group 1:				[10de:1c31] b3:00.0 VGA compatible controller: NVIDIA Corporation GP106GL [Quadro P2200] (rev a1)
				[10de:10f1] b3:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)

tower-diagnostics-20251221-1902.zip

I'm also having this issue after upgrading from 7.2.3.

44 minutes ago, nosaj070 said:

I'm also having this issue after upgrading from 7.2.3.

Did you read the answer that I gave? Anyways, Diagnostics are missing.

Please also note that the user has two issue, downloads not working and the driver not working.

Hi all,

So took my server down to install some fans.

After botting up again I noticed my frigate and plex containers weren't starting and further digging it was due to no gpu's being detected by the system.

What I have done is removed the nvidia plugin > rebooted > reinstalled plugin but still nothing. I have also installed the open source version btu still nothing.ut still get the same message in the plugin:

Installed GPU(s):
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

GPU's show up in my devices (Quadro P1000 and GTX 1060).

Attached is my diagnostics file

homelab-diagnostics-20251222-1819.zip

Edit: Solved. The two gpu's apparently need 580.x legacy drivers

Edited December 22, 2025Dec 22 by Toady001

Just to reiterate, for anyone who missed the edit above...

The v590.x NVidia drivers drop support for the pascal architecture, that's Quadro P Series (i.e. P2000, P1000) and the GTX 10XX (i.e. 1060, 1080). If you have one of these cards, make sure to stay on the v580.x drivers.

Edited December 22, 2025Dec 22 by treos33

I have an old P400 card in my server, nvidia drivers stopped working after update. Headed over here and found the answer, downgraded to 580.x and all back up and running. Thanks all!

Hey guys,

This problem has been going for MONTHS and it's driving me insane because just when I think I've fixed it, it happens again.
So I mainly use this card for Plex transcoding, and when the Nvidia driver is detecting the card normally, it works flawlessly. When trandcoding, the GPU statistics plugin correctly displays the Plex icon and nvidia-smi returns the appropriate data. Needless to say, I have correctly set up the Plex docker for the nvidia transcoding. I DON'T have it passed through to a VM.
However every few weeks, the nvidia driver/plugin decides it no longer wants to detect the card, and will not detect it again until I reboot the entire server.

I've attached diags and screenshots. See below.

The card is visible in system devices under IOMMU group 13: [10de:21c4] 01:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] (rev a1).

However I can find no trace of it anywhere else. Even running 'nvidia-smi' returns 'No devices were found'.
I've double and triple checked that the card is seated correctly. I've deleted the Nvidia plugin/driver, stopped docker, then reinstalled several times. I've rolled back the driver as far back as the plugin will allow (v575.64.05), but still no success. This also used to happen with my older 1050Ti on a different motherboard before I upgraded the system.

I'm sick to death of logging into the web UI and discovering that the GPU Statistics plugin has not detected the card (god knows for how long), and I need this fixed PERMANENTLY.

Any ideas???

nas-diagnostics-20251224-0010.zip

Edited December 26, 2025Dec 26 by Corvus

5 hours ago, Corvus said:

This problem has been going for MONTHS and it's driving me insane because just when I think I've fixed it, it happens again.

First of all, why:

Dec 17 14:55:33 NAS emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/Nvidia Patch/script" >/dev/null 2>&1

Please read the first post and especially the red text, you are modifying the driver and I can't give support for that and in reality how much concurrent streams do you have which need to be transcoded?

This is the real issue:

Dec 24 00:06:15 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Dec 24 00:06:15 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 24 00:06:17 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Dec 24 00:06:17 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 24 00:06:19 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Dec 24 00:06:19 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 24 00:06:21 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Dec 24 00:06:21 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

I can't tell you why that is caused (maybe because of your patch script) however I would recommend that you do the following:

1. Check if your BIOS is up to date

2. Check if you have Above 4G Decoding enabled

3. Check if you have Resizable BAR support enabled

4. Use that as your startup script instead of patching the driver:
   nvidia-persistenced

However I really don't see why you are using a Nvidia for transcoding, you have a Intel iGPU in your system which is probably well enough for you to transcode (Intel has no hard limit of simultaneous transcodes BTW).

20 hours ago, ich777 said:

First of all, why:

Dec 17 14:55:33 NAS emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/Nvidia Patch/script" >/dev/null 2>&1

Please read the first post and especially the red text, you are modifying the driver and I can't give support for that and in reality how much concurrent streams do you have which need to be transcoded?

This is the real issue:

Dec 24 00:06:15 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Dec 24 00:06:15 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 24 00:06:17 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Dec 24 00:06:17 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 24 00:06:19 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Dec 24 00:06:19 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 24 00:06:21 NAS kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:2584)

Dec 24 00:06:21 NAS kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

I can't tell you why that is caused (maybe because of your patch script) however I would recommend that you do the following:

1. Check if your BIOS is up to date

2. Check if you have Above 4G Decoding enabled

3. Check if you have Resizable BAR support enabled

4. Use that as your startup script instead of patching the driver:
   nvidia-persistenced

However I really don't see why you are using a Nvidia for transcoding, you have a Intel iGPU in your system which is probably well enough for you to transcode (Intel has no hard limit of simultaneous transcodes BTW).

1. Why what? Sorry I'm a newbie at this. I'm assuming you mean that I modified the nvidia plugin somehow? That's impossible as I wouldn't even know how to do that. Unless I did so unwittingly by following someone else's advice. How would I undo this?
   
   2. I have a large number of users. Sometimes up to 8-10 streams needing transcoding at once.

3. BIOS is up to date. 'Above 4G decoding' is enabled in BIOS (unless I need to enable it elsewhere?). What is 'resizable BAR support'? Use what as my startup script? What does typing 'nvidia-persistenced' in terminal do? Sorry, again I'm very unfamiliar with Linux so I'll need much more detailed instructions please.
   
   4. I run a couple of VMs 24/7 (No GPUs passed through) and I don't want to eat into the performance of my CPU, so I'm using the GPU for transcoding as I had it lying around. Additionally, I also use it for running my own 24/7 IPTV channels in another docker container.

What should I be doing to fix this?

Edited December 27, 2025Dec 27 by Corvus

6 hours ago, Corvus said:

Why what? Sorry I'm a newbie at this. I'm assuming you mean that I modified the nvidia plugin somehow? That's impossible as I wouldn't even know how to do that. Unless I did so unwittingly by following someone else's advice. How would I undo this?

I don't know, you have a patch script in place which I don't support and which could be the culprit from your issue. Maybe a user script?

6 hours ago, Corvus said:

2. I have a large number of users. Sometimes up to 8-10 streams needing transcoding at once.

The iGPU from your CPU should be more than be capable of such a task.

6 hours ago, Corvus said:

BIOS is up to date. 'Above 4G decoding' is enabled in BIOS (unless I need to enable it elsewhere?). What is 'resizable BAR support'? Use what as my startup script? What does typing 'nvidia-persistenced' in terminal do? Sorry, again I'm very unfamiliar with Linux so I'll need much more detailed instructions please.

Above 4G decoding needs to be enabled in your BIOS including Resizable BAR Support <- this is also a setting in your BIOS.

You can define a User Script which runs on boot with the contents:
nvidia-persistenced

This will ensure that your card is constantly in a low power state (at least when it's not in use) and hopefully not fail to initialize.

6 hours ago, Corvus said:

4. I run a couple of VMs 24/7 (No GPUs passed through) and I don't want to eat into the performance of my CPU, so I'm using the GPU for transcoding as I had it lying around. Additionally, I also use it for running my own 24/7 IPTV channels in another docker container.

Your iGPU on the CPU is dedicated from the CPU and the CPU will be not impacted or better speaking will not be affected by the load from transcoding if you use the iGPU.

Oh, please also check your Power Supply, they degrade over time and if a power spike happens because a HDD spins up and transcoding starts it is possible that they fail to deliver "enough" power and such issues can happen.

Hi,

Santa brought me a little 5060ti to help me craate useless IA images but I'm facing issues.

I installed opensource nvidia drivers to replace my old official nvidia drivers used for my previous 1650. But I can't do anything because the card is flip-flapping with theses messages :

Dec 27 13:31:31 Tower kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter

Dec 27 13:31:31 Tower kernel: NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x51:763)

Dec 27 13:31:31 Tower kernel: NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0

Dec 27 13:31:41 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1359

Dec 27 13:32:07 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1359

Dec 27 13:32:07 Tower kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242

Dec 27 13:32:07 Tower kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed

Dec 27 13:32:07 Tower kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed

I read this forum for a solution but nothing seems to work. If some kind guy could help me or give me some hints, I would be very grateful.

tower-diagnostics-20251227-1321.zip

4 minutes ago, Astrayel said:

I read this forum for a solution but nothing seems to work. If some kind guy could help me or give me some hints, I would be very grateful.

A bit more in detail please, what did you try yet?
Did you also try to add:

nvidia-persistenced to your go file or as a startup script?

Also what is this in your go file:
sysctl vm.overcommit_memory=1

I mean it won't change much but it certainly won't help your issue here.

Please make sure to enable Above 4G Decoding and also to enable Resizable BAR Support.

Make also sure that you are on the latest BIOS version.

40 minutes ago, ich777 said:

A bit more in detail please, what did you try yet?
Did you also try to add:

nvidia-persistenced to your go file or as a startup script?

Also what is this in your go file:
sysctl vm.overcommit_memory=1

I mean it won't change much but it certainly won't help your issue here.

Please make sure to enable Above 4G Decoding and also to enable Resizable BAR Support.

Make also sure that you are on the latest BIOS version.

I checked BIOS and Above 4G decoding does not exist anymore on my Z890. But Resizable BAR was already enabled.

I removed the sysctl. It's been here for a long time but I can't remember why I put it.

I added the nvidia-persistenced and I'm waiting but it looks like it did the trick.

Thanks for all. I'll come back if errors come back.

33 minutes ago, Astrayel said:

I checked BIOS and Above 4G decoding does not exist anymore on my Z890

This could also be something like: Huge address table, Support for lage address or something like that.

2 hours ago, ich777 said:

I don't know, you have a patch script in place which I don't support and which could be the culprit from your issue. Maybe a user script?

I have no idea. How do I remove it?

2 hours ago, ich777 said:

The iGPU from your CPU should be more than be capable of such a task.

Since I use the iGPU for my VMs, I still don't think this is a good idea. I also have a few AI object recognition dockers which utilize nvidia CUDA cores. Unless there's an alternative I'm missing?

2 hours ago, ich777 said:

You can define a User Script which runs on boot with the contents:
nvidia-persistenced

This will ensure that your card is constantly in a low power state (at least when it's not in use) and hopefully not fail to initialize.

So I just type that command into terminal, and that's it?

Does this remove the patch script you're seeing above?

2 hours ago, ich777 said:

Your iGPU on the CPU is dedicated from the CPU and the CPU will be not impacted or better speaking will not be affected by the load from transcoding if you use the iGPU.

Since I need the dedicated GPU for other dockers (not used simultaneously), I would still like to solve this problem.

2 hours ago, ich777 said:

Oh, please also check your Power Supply

How would I go about checking for an intermittent fault such as this?

I think I should rule out the easy fixes first, starting with this custom script you mentioned. Could you please tell me how to remove it?

1 hour ago, Corvus said:

I have no idea. How do I remove it?

Sorry, can't help with that, I don't know how you've set that up, but most definitely in User Scripts I assume.

1 hour ago, Corvus said:

Since I use the iGPU for my VMs, I still don't think this is a good idea. I also have a few AI object recognition dockers which utilize nvidia CUDA cores. Unless there's an alternative I'm missing?

Always depends, if there is a OpenVINO variant from the container available probably.

1 hour ago, Corvus said:

So I just type that command into terminal, and that's it?

Does this remove the patch script you're seeing above?

Nope, you have to actively remove your old script, I really can't tell you how or where but most certainly in User Scripts.

You also have to set up a new user script that runs once at startup with the contents:

#!/bin/bash
nvidia-persistenced

1 hour ago, Corvus said:

How would I go about checking for an intermittent fault such as this?

How old is your power supply, what power supply do you have, is the power supply sufficient in it's base configuration for the hardware that you are using?

1 hour ago, Corvus said:

I think I should rule out the easy fixes first, starting with this custom script you mentioned. Could you please tell me how to remove it?

Please ask in the User Script support thread or just look on the server for this plugin.

However most questions are not related to the Nvidia Driver Plugin and I can only give support for the driver plugin itself if something isn't working, especially if you are using the patch script, again, please read the first post in this thread on top the red text.

10 hours ago, ich777 said:

Sorry, can't help with that, I don't know how you've set that up, but most definitely in User Scripts I assume.

Ok I just found what it is. Apparently it was recommended by SpaceInvader to remove the nvidia-imposed limit on the number of simultaneous transcoding streams. Is this something that is no longer required for me to get unlimited simultaneous transcodes? Happy to remove this if so.

10 hours ago, ich777 said:

if there is a OpenVINO variant from the container available probably.

There isn't, which is why I rely on using the GPU for dockers.

10 hours ago, ich777 said:

How old is your power supply, what power supply do you have

It's a Corsair CXM 750 W 80+. More than enough for my config + drives, according to pcpartpicker.

Hi, I’m joining the club! :)
I’m seeing the same NVRM errors with an NVIDIA RTX 5060 Ti 16GB on an ASRock Z790 Pro RS/D4.

Hardware / SW:

- Unraid: 7.2.3

- NVIDIA driver: 580.95.05 (open kernel modules)

- Motherboard: ASRock Z790 Pro RS/D4

- CPU: i5-14600K

- RAM: 96GB DDR4

- GPU: RTX 5060 Ti 16GB

Symptoms:

- GPU sometimes works (nvidia-smi OK, can run compute like llama.cpp),

but then syslog starts spamming NVRM errors and the driver fails to attach/init the GPU.

Example log:

Dec 28 14:46:06 kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242

Dec 28 14:46:06 kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed

Dec 28 14:46:06 kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed

Dec 28 14:46:06 kernel: NVRM: osInitNvMapping: *** Cannot attach gpu

Dec 28 14:46:06 kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter

Dec 28 14:46:06 kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:763)

BIOS / platform notes:

- Above 4G Decoding: Enabled

- Resizable BAR (C.A.M.): Enabled

- VT-d: Enabled

- PCIe ASPM: Disabled

- Slot is stable.

I’ve tried the common suggested toggles/settings for days and nothing has reliably fixed it. At this point I’m not too bothered, but if anyone has a new angle or a known workaround, I’m all ears. :)

6 minutes ago, Flashman007 said:

At this point I’m not too bothered, but if anyone has a new angle or a known workaround, I’m all ears. :)

Did you also add nvidia-persistenced to a startup script and are you sure that you are booting in UEFI instead of Legacy?

Thanks for the reply. Yes to both. Also, I’m on the latest BIOS.

1 hour ago, Flashman007 said:

Thanks for the reply. Yes to both. Also, I’m on the latest BIOS.

Sorry, then I can't help, you can create a post on the Nvidia Developer forums about the issue since there are many users on there which having the same issue, but as said, I already suffered from the same issue on my Debian Desktop machine (Intel 12th gen) and once I reset the BIOS to defaults everything was starting to work again, not sure which setting causes this.

20 hours ago, Corvus said:

Ok I just found what it is. Apparently it was recommended by SpaceInvader to remove the nvidia-imposed limit on the number of simultaneous transcoding streams. Is this something that is no longer required for me to get unlimited simultaneous transcodes? Happy to remove this if so.

There isn't, which is why I rely on using the GPU for dockers.

It's a Corsair CXM 750 W 80+. More than enough for my config + drives, according to pcpartpicker.

Just a follow-up on this to see what I need to do with this user script -- or if it's even necessary anymore to get unlimited transcodes.

1 hour ago, Corvus said:

Just a follow-up on this to see what I need to do with this user script -- or if it's even necessary anymore to get unlimited transcodes.

I believe that the GTX1660 can now do 8 concurrent transcodes. Back when SpaceInvader One posted that video, NVidia drivers had it throttled to only 2 transcodes at a time.

You put ich777 in a bad spot. If you read the opening posts in this thread, he clearly states that he cannot assist anyone using this patch. It violates the Terms of Agreement from Nvidia, whom take their ToA very seriously. Which could actually put both him and Limetech at legal and financial risk.

Regarding power supplies - Your supply may be more than enough for your system if it is functioning correctly. They do fail over time, and not only catastrophically. Most of the time, they start being flaky (or to be more exact, the system they power has intermittent issues). I have seen several systems do this - many hours of troubleshooting, only to be resolved by replacing the power supply. Failing capacitors, noisy voltages cause strange things to happen, especially as computer semiconductors get physically smaller and power efficient.

Other possible issues could be the power you plug your PC into. Noise on the A/C power, improper grounding, floating neutral wire. Or it could be an issue with the NVidia driver code itself. ich777 cannot do anything about that. He generously compiles a package (and the mechanism and GUI to utilize it in Unraid) and offers his knowledge and support for this and literally hundreds of other plugins and Docker containers. Not for money or fame, but because he is genuinely a nice guy (as far as I have observed over the past few years).

Edited December 29, 2025Dec 29 by ConnerVT