1 hour ago, ich777 said:

Do you have Diagnostics?

How long did you wait until you got the error? It seems that you installed the plugin already once, please remove the plugin (go to the Plugins page and make sure it's not listed there anymore) reboot and try to reinstall it and wait for the dialogue to display the DONE button.

I have attached some logs below:

May 19 12:15:40 DavesUnraid plugin-manager: creating: /boot/config/plugins/nvidia-driver/nvidia-driver-2025.03.25.txz - downloading from URL https://github.com/unraid/unraid-nvidia-driver/raw/master/packages/nvidia-driver-2025.03.25.txz May 19 12:15:40 DavesUnraid plugin-manager: checking: /boot/config/plugins/nvidia-driver/nvidia-driver-2025.03.25.txz - MD5 May 19 12:15:40 DavesUnraid plugin-manager: running: upgradepkg --install-new /boot/config/plugins/nvidia-driver/nvidia-driver-2025.03.25.txz May 19 12:15:40 DavesUnraid plugin-manager: creating: /usr/local/emhttp/plugins/nvidia-driver/README.md - from INLINE content May 19 12:15:40 DavesUnraid plugin-manager: running: 'anonymous' May 19 12:15:56 DavesUnraid kernel: block nvme0n1: the capability attribute has been deprecated. May 19 12:15:56 DavesUnraid kernel: r8169 0000:24:00.0: invalid VPD tag 0xff (size 0) at offset 0; assume missing optional EEPROM May 19 12:15:58 DavesUnraid nginx: 2025/05/19 12:15:58 [error] 4382#4382: *514646 open() "/usr/local/emhttp/davesunraid-diagnostics-20250519-1515.zip" failed (2: No such file or directory) while sending to client, client: 192.168.68.89, server: , request: "GET /davesunraid-diagnostics-20250519-1515.zip HTTP/1.1", host: "192.168.68.117", referrer: "http://192.168.68.117/Tools/Diagnostics" May 19 12:16:15 DavesUnraid monitor_nchan: Stop running nchan processes

 

Diagnostics have returned a 404 error when trying to save to .zip??

 

When I navigate to /boot/config/plugins/nvidia-driver/ it doesn't exist.

When I navigate to /usr/local/emhttp/plugins/nvidia-driver/ it doesn't exist.

 

This is a pretty fresh install of unraid. I only set it up about 2 days ago..

 

 

35 minutes ago, Dsopinka said:

I have attached some logs below:

Please post your Diagnostics as pointed out above.

 

36 minutes ago, Dsopinka said:

Diagnostics have returned a 404 error when trying to save to .zip??

This indicates a general issue with the server...

How much RAM do you have installed? What USB Boot device are you using? Are you sure you have enough free space on it?

2 minutes ago, ich777 said:

Please post your Diagnostics as pointed out above.

 

This indicates a general issue with the server...

How much RAM do you have installed? What USB Boot device are you using? Are you sure you have enough free space on it?

I have 78GB of ram usable.

 

I am using a SAMSUNG BAR Plus 64GB. 

 

I have 63.3GB free space on this USB

47 minutes ago, Dsopinka said:

Diagnostics have returned a 404 error when trying to save to .zip??

Can you try to open up a terminal from Unraid and issue:

diagnostics

after that you will find the Diagnostics in /boot/logs

1 minute ago, ich777 said:

Can you try to open up a terminal from Unraid and issue:

diagnostics

after that you will find the Diagnostics in /boot/logs

root@DavesUnraid:/# diagnostics
bash: diagnostics: command not found

Just now, Dsopinka said:

root@DavesUnraid:/# diagnostics
bash: diagnostics: command not found

Please create a post in the General sub forums, I think your USB flash drive dropped offline and that's why you can't issue the command:

 

At least something seems wrong to me, please try to reboot your server and issue the command right after the reboot.

15 hours ago, alturismo said:

if its a docker, sort your issue

 

from your logs it looks like rbar, above 4g ... not activated ?

seat is correct

Power supply is sufficient

...

 

May 19 16:10:30 server kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 239
May 19 16:10:30 server kernel: 
May 19 16:10:30 server kernel: nvidia 0000:04:00.0: enabling device (0000 -> 0003)
May 19 16:10:30 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
May 19 16:10:30 server kernel: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:04:00.0)
May 19 16:10:30 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
May 19 16:10:30 server kernel: NVRM: BAR2 is 0M @ 0x0 (PCI:0000:04:00.0)
May 19 16:10:30 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
May 19 16:10:30 server kernel: NVRM: BAR3 is 0M @ 0x0 (PCI:0000:04:00.0)
May 19 16:10:30 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
May 19 16:10:30 server kernel: NVRM: BAR4 is 0M @ 0x0 (PCI:0000:04:00.0)
May 19 16:10:30 server kernel: nvidia 0000:04:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
May 19 16:10:30 server kernel: nvidia 0000:0b:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
May 19 16:10:30 server kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  570.144  Thu Apr 10 20:33:29 UTC 2025
May 19 16:10:30 server kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  570.144  Thu Apr 10 20:03:03 UTC 2025
May 19 16:10:30 server kernel: [drm] [nvidia-drm] [GPU ID 0x00000400] Loading driver
May 19 16:10:30 server kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:04:00.0 on minor 0
May 19 16:10:30 server kernel: [drm] [nvidia-drm] [GPU ID 0x00000b00] Loading driver
May 19 16:10:30 server kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:0b:00.0 on minor 1

 

also, with a 50 series card you have to use the open source driver, like mentioned many times

and looks to me you are using the regular one.

 

May 19 16:11:00 server rc.local: plugin: installing: nvidia-driver.plg
May 19 16:11:00 server rc.local: Executing hook script: pre_plugin_checks
May 19 16:11:00 server rc.local: +==============================================================================
May 19 16:11:00 server rc.local: | Installing new package /boot/config/plugins/nvidia-driver/nvidia-driver-2025.03.25.txz
May 19 16:11:00 server rc.local: +==============================================================================
May 19 16:11:00 server rc.local: Verifying package nvidia-driver-2025.03.25.txz.
May 19 16:11:00 server rc.local: Installing package nvidia-driver-2025.03.25.txz:
May 19 16:11:00 server rc.local: PACKAGE DESCRIPTION:
May 19 16:11:00 server rc.local: Package nvidia-driver-2025.03.25.txz installed.
May 19 16:11:00 server rc.local: --------------------Nvidia driver v570.144 found locally---------------------
May 19 16:11:00 server rc.local: --------------Installation of Nvidia driver v570.144 successful--------------
May 19 16:11:00 server rc.local: plugin: nvidia-driver.plg installed
May 19 16:11:00 server rc.local: Executing hook script: post_plugin_checks

 

may also check pcie slots, assignments, free pcie lanes on your board, etc etc ...

as you are running an AMD System which is may not the best option cfor virtualising (personal oppinion, likely having issues), may alot trial & error, cant help too much here as its not the best combo overall.

I did turn on 4g and rebar in the bios.

When i'm using production branch my P4000 is detected but the 5070Ti is not.
When i'm using open source brance non of the GPUs is detected. I've attached screenshots and diagnostics.

server-diagnostics-20250520-0946.zip

58 minutes ago, mrkwkns said:

When i'm using open source brance non of the GPUs is detected. I've attached screenshots and diagnostics.

 

yep, the p4000 is not supported by the open source driver ...

 

May 20 09:41:58 server kernel: NVRM: The NVIDIA GPU 0000:0b:00.0 (PCI ID: 10de:1bb1)
May 20 09:41:58 server kernel: NVRM: installed in this system is not supported by open
May 20 09:41:58 server kernel: NVRM: nvidia.ko because it does not include the required GPU
May 20 09:41:58 server kernel: NVRM: System Processor (GSP).
May 20 09:41:58 server kernel: NVRM: Please see the 'Open Linux Kernel Modules' and 'GSP
May 20 09:41:58 server kernel: NVRM: Firmware' sections in the driver README, available on
May 20 09:41:58 server kernel: NVRM: the Linux graphics driver download page at
May 20 09:41:58 server kernel: NVRM: www.nvidia.com.

 

your 5070 has still the same pcie issue for the driver ... same error as above, and as its an AMD sys im out anyhow ...

 

so in the end you only have 1 option left, keep p4000 as "host" usage (docker and co ...)

while using the regular branch driver

 

try to passthrough the 5070 to a VM and hope it works well ...

update unraid 7.1.2  Not available Tesla P4

3 minutes ago, Jeffmiao said:

update unraid 7.1.2  Not available Tesla P4

Please always include your Diagnostics.

4 hours ago, ich777 said:

Please always include your Diagnostics.

jeffmiaounraid-diagnostics-20250520-2155.zip

39 minutes ago, Jeffmiao said:

jeffmiaounraid-diagnostics-20250520-2155.zip

You've enabled the nouveau driver by creating the file /boot/config/modprobe.d/nouveau.conf:

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: GPU 0000:b3:00.0 is already bound to nouveau.

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: This can occur when another driver was loaded and

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: obtained ownership of the NVIDIA device(s).

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: Try unloading the conflicting kernel module (and/or

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: reconfigure your kernel without the conflicting

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: again.

May 20 17:34:58 JeffmiaoUnraid kernel: NVRM: No NVIDIA devices probed.

If you want to revert that and use the Nvidia Driver plugin you have to issue this command from an Unraid Terminal:
rm -f /boot/config/modprobe.d/nouveau.conf

and reboot afterwards.

I've successfully got the 5070Ti working within a Windows 11 VM, without encountering error 43, and I'm able to stream games via Steam. While I'm using the production branch of the Nvidia driver, it doesn't recognize my Quadro P4000, which I intend to use in my Plex Docker. How can I get the Quadro to work? I'm not entirely sure what else to attempt.

server-diagnostics-20250521-1020.zip

13 minutes ago, mrkwkns said:

it doesn't recognize my Quadro P4000

You have multiple issues:

May 21 10:03:26 server kernel: nvidia 0000:0b:00.0: enabling device (0000 -> 0003)
May 21 10:03:26 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

May 21 10:03:26 server kernel: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:0b:00.0)

May 21 10:03:26 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

May 21 10:03:26 server kernel: NVRM: BAR2 is 0M @ 0x0 (PCI:0000:0b:00.0)

May 21 10:03:26 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

May 21 10:03:26 server kernel: NVRM: BAR3 is 0M @ 0x0 (PCI:0000:0b:00.0)

May 21 10:03:26 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

May 21 10:03:26 server kernel: NVRM: BAR4 is 0M @ 0x0 (PCI:0000:0b:00.0)

and:

May 21 10:04:20 server kernel: NVRM: GPU 0000:0b:00.0: RmInitAdapter failed! (0x24:0x72:1512)
May 21 10:04:20 server kernel: NVRM: GPU 0000:0b:00.0: rm_init_adapter failed, device minor number 0
May 21 10:04:20 server kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
May 21 10:04:20 server kernel: pci 0000:06:00.0: VPD access failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update
May 21 10:04:21 server kernel: resource: resource sanity check: requesting [mem 0x00000000de700000-0x00000000df6fffff], which spans more than 0000:0b:00.0 [mem 0xde000000-0xdeffffff]
May 21 10:04:21 server kernel: caller _nv046997rm+0x3a/0xb0 [nvidia] mapping multiple BARs
May 21 10:04:21 server kernel: NVRM: GPU 0000:0b:00.0: RmInitAdapter failed! (0x24:0x72:1512)
May 21 10:04:21 server kernel: NVRM: GPU 0000:0b:00.0: rm_init_adapter failed, device minor number 0
May 21 10:04:21 server emhttpd: error: get_key_info, 683: Invalid argument (22): stat: /boot/config/Plus.key
May 21 10:04:21 server kernel: resource: resource sanity check: requesting [mem 0x00000000de700000-0x00000000df6fffff], which spans more than 0000:0b:00.0 [mem 0xde000000-0xdeffffff]
May 21 10:04:21 server kernel: caller _nv046997rm+0x3a/0xb0 [nvidia] mapping multiple BARs
May 21 10:04:21 server kernel: NVRM: GPU 0000:0b:00.0: RmInitAdapter failed! (0x24:0x72:1512)
May 21 10:04:21 server kernel: NVRM: GPU 0000:0b:00.0: rm_init_adapter failed, device minor number 0

I see that you also booting with Legacy, can you please enable UEFI boot mode and also set UEFI boot in your BIOS and see if that solves the issue?

Are you really sure that you've enabled Resizable BAR support, usually you have to boot into UEFI mode to fully support that.

23 hours ago, ich777 said:

You have multiple issues:

May 21 10:03:26 server kernel: nvidia 0000:0b:00.0: enabling device (0000 -> 0003)
May 21 10:03:26 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

May 21 10:03:26 server kernel: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:0b:00.0)

May 21 10:03:26 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

May 21 10:03:26 server kernel: NVRM: BAR2 is 0M @ 0x0 (PCI:0000:0b:00.0)

May 21 10:03:26 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

May 21 10:03:26 server kernel: NVRM: BAR3 is 0M @ 0x0 (PCI:0000:0b:00.0)

May 21 10:03:26 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

May 21 10:03:26 server kernel: NVRM: BAR4 is 0M @ 0x0 (PCI:0000:0b:00.0)

and:

May 21 10:04:20 server kernel: NVRM: GPU 0000:0b:00.0: RmInitAdapter failed! (0x24:0x72:1512)
May 21 10:04:20 server kernel: NVRM: GPU 0000:0b:00.0: rm_init_adapter failed, device minor number 0
May 21 10:04:20 server kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
May 21 10:04:20 server kernel: pci 0000:06:00.0: VPD access failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update
May 21 10:04:21 server kernel: resource: resource sanity check: requesting [mem 0x00000000de700000-0x00000000df6fffff], which spans more than 0000:0b:00.0 [mem 0xde000000-0xdeffffff]
May 21 10:04:21 server kernel: caller _nv046997rm+0x3a/0xb0 [nvidia] mapping multiple BARs
May 21 10:04:21 server kernel: NVRM: GPU 0000:0b:00.0: RmInitAdapter failed! (0x24:0x72:1512)
May 21 10:04:21 server kernel: NVRM: GPU 0000:0b:00.0: rm_init_adapter failed, device minor number 0
May 21 10:04:21 server emhttpd: error: get_key_info, 683: Invalid argument (22): stat: /boot/config/Plus.key
May 21 10:04:21 server kernel: resource: resource sanity check: requesting [mem 0x00000000de700000-0x00000000df6fffff], which spans more than 0000:0b:00.0 [mem 0xde000000-0xdeffffff]
May 21 10:04:21 server kernel: caller _nv046997rm+0x3a/0xb0 [nvidia] mapping multiple BARs
May 21 10:04:21 server kernel: NVRM: GPU 0000:0b:00.0: RmInitAdapter failed! (0x24:0x72:1512)
May 21 10:04:21 server kernel: NVRM: GPU 0000:0b:00.0: rm_init_adapter failed, device minor number 0

I see that you also booting with Legacy, can you please enable UEFI boot mode and also set UEFI boot in your BIOS and see if that solves the issue?

Are you really sure that you've enabled Resizable BAR support, usually you have to boot into UEFI mode to fully support that.

Thank you for your response.

I believe I have everything working correctly now. The P4000 is installed in PCI slot one, and the 5070Ti is in slot two.

The P4000 is being recognized by the production branch of the Nvidia driver and is functional within Docker. The 5070Ti is operational within a Windows 11 VM.

server-diagnostics-20250522-1007.zip

IMG_0330 - kopie.HEIC

Edited May 22, 20251 yr by mrkwkns

3 hours ago, mrkwkns said:

I believe I have everything working correctly now. The P4000 is installed in PCI slot one, and the 5070Ti is in slot two.

Yes looking good, from what I see you switched slots from the GPUs and enabled UEFI boot.

Glad to hear that everything is working now.

Hey guys, i hadnt had a chance all week to work on this until now,

i unplugged the gpu (asus 5070 TI) from the pcie 1st (pcie 5) slot and plugged into the 2nd pcie (pcie 4) slot, re seated the power on both ends and raised the gpu vertical stand so the riser cable had less bend, and now in nvidia plugin its showing this

So its that installed or not, it says 0 but now showing stuff, when previously it just said no Device. apologises if its obvious, ive used unraid for a year and a half but this is the first time installing a gpu into it

Edit: in gpu statistic plugin, i can now select this, so i guess its installed? even if the nvidia plugin page says Installed GPU 0 ?

rossiserver-diagnostics-20250524-1406.zip

Edited May 24, 20251 yr by Maximo101
added gpu stats

24 minutes ago, Maximo101 said:

Edit: in gpu statistic plugin, i can now select this, so i guess its installed? even if the nvidia plugin page says Installed GPU 0 ?

yes, the id (0) is the 1st device, id (1) would be the 2nd device, and so on ... so its fine now and as expected, hardware issue with your pcie and riser and / or power supply, now it seems fine.

thank you very much. i wonder if its the pcie 1st slot itself. for now ill leave it but at some point ill want to put it back into the first slot to take advantage of pcie5 and not just pcie4.

is pcie5 supported by unraid os 7.0.0 ?

1 hour ago, Maximo101 said:

thank you very much. i wonder if its the pcie 1st slot itself. for now ill leave it but at some point ill want to put it back into the first slot to take advantage of pcie5 and not just pcie4.

Please keep in mind that 5000 series cards are known to have issues with PCIe 5.0 and it is recommended for users with issues to even switch to PCIe 4.0

1 hour ago, Maximo101 said:

is pcie5 supported by unraid os 7.0.0 ?

This is not related to Unraid, this is hardware related and this is something that your Motherboard Manufacturer with a BIOS update or even Nvidia has to solve.

Thanks Alt and ich, you guys are scholars and gentlemen.

cheers

CodeProject.AI docker (codeproject/ai-server:cuda12_2) with Object Detection (YOLOv5 6.2) is incorrectly reporting in the nvidia gpu plugin (Nvidia Driver Version: 575.51.02 - plugin up to date 2025.03.25) dashboard as beeing in use by "immich (python 3.8)" as i do not have immich installed i had to trial and error restaring all dockers with gpu to find it. I just recently noticed this as before i had never seen the codeproject docker reported in the plugin

1 minute ago, Akagami said:

I just recently noticed this as before i had never seen the codeproject docker reported in the plugin

but this is the wrong place as not related ... ;)

your GPU stats plugin thread would be the right place to post this, there is the "magic" done to put the icon, apps to the running processes, @SimonF can tell you better ... i assume as python is pretty common there are even more apps may reporting "immich"

7 minutes ago, alturismo said:

but this is the wrong place as not related ... ;)

your GPU stats plugin thread would be the right place to post this, there is the "magic" done to put the icon, apps to the running processes, @SimonF can tell you better ... i assume as python is pretty common there are even more apps may reporting "immich"

my bad i thought the dashboard panel was part of the nvidia driver plugin istead it has its own compleatly forgot. ill cross post it sorry

Hi Since upgrading to 7.0 now 7.1.2 i keep getting an error saying its failed to download the updated driver, it then borks the GPU and the whole system needs to be rebooted for the GPU to be recognised

I have uninstalled and reinstalled the plugin, change from production to Nvidia Driver currently installed v575.57.08. I then have to manually select a different branch for it to force a download and reboot.

Any ideas what the issue is?

Edited May 30, 20251 yr by Rkpaxam