5 hours ago, ich777 said:

Is this the first time you are trying to utilise your Nvidia GPU in a Docker container or was it working previously?

 

Please never runs such a container as Privileged, this is not a switch that will solve all your issues, exactly to other side is happening in your case because you are running the container in Host networking mode you basically give the container full access to your Hosts network interfaces and Privileged is always a thing that should be avoided at all cost.

 

Seems like it can't utilise your Nvidia GPU, please upgrade to the latest Nvidia Driver in the plugin, reboot and try to official Plex container and see if it's working with that one.

Maybe you have to install a docker mod into the Linux Server container but I'm not sure about that because I'm not familiar with their container.

 

Also make sure to enable Above 4G Decoding or in some cases it's named Support for Huge Address Spaces in the BIOS at the PCI submenu.

 

Please also double check if you don't have any additional spaces at the end of the UUID in the Docker template.

Everything seems fine from what I see in your Diagnostics.

 

ATTENTION: Please try forcing a transcode with a native Plex app like for iOS or Android since it a known issue that the Plex Web Player or Windows App just shows a black screen and transcoding is not working there in combination with Nvidia.

 

@ich777 got an update to this. It's still throwing the same errors. I did the following:

1. Removed plex (linuxserver) and deleted the .../appdata/plex/ folder
2. Updated video driver to v570 (current version branch)
3. Restarted PC and checked to make sure the driver installed correctly
4. Installed the official plex container (followed the guide in post 2 of this thread)

Still got the same errors. I looked through the BIOS settings, not much for PCIe settings, just Enable or Disable power control. It was disabled, I tried enabling it.

 

However, I had noticed that when using lspci, there is an integrated GPU (AMD ES1000) on the motherboard. Is it possible that somehow Plex is trying to use this GPU? If so, I'm not sure how to check or how to stop it. I have attached updated Diagnostics file.

 

nas-1-diagnostics-20250323-1305.zip

I recently upgraded the GPU from a 1660Ti that was working great for transcoding in plex, to a 1080Ti.

 

I shutdown the server, swapped GPU, and now my plex docker has disappeared and the GPU is not showing in the Nvidia Driver plugin, and the GPU Dashboard isn't showing it either.  It IS showing in the System Devices, and I can select it for the GPU stats dashboard but the dashboard shows this error:

I am also getting these errors trying to shutdown the server to pull diagnostics.

 

Diagnostics attached.  Hopefully they can help shed some light.  I put back in my old 1660Ti and everything is working as it should.

 

 

 

 

milkyway-diagnostics-20250323-1900.zip

Edited March 24, 20251 yr by Rhuarc

6 hours ago, Rhuarc said:

I recently upgraded the GPU from a 1660Ti that was working great for transcoding in plex, to a 1080Ti.

 

your diags showing a 1060

 

0c:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
	Subsystem: eVga.com. Corp. Device [3842:6368]
	Kernel driver in use: nvidia
	Kernel modules: nvidia_drm, nvidia
0c:00.1 Audio device [0403]: NVIDIA Corporation GP106 High Definition Audio Controller [10de:10f1] (rev a1)
	Subsystem: eVga.com. Corp. Device [3842:6368]

 

and when you swap your GPU, you also changed the UID of the card in the docker template ? also chacked Plex then once it started so ots still setted to a Nvidia card.

 

seeking logs, everything is looking ok in the logs with your card

11 hours ago, strider2112 said:

However, I had noticed that when using lspci, there is an integrated GPU (AMD ES1000) on the motherboard. Is it possible that somehow Plex is trying to use this GPU?

I don't think that this is the issue here since you've explicitly set the GPU to your Nvidia GPU.

 

I'm also not sure what it could be, maybe it is related to your old hardware but I'm not sure about that.

From what I can see from your Diagnostics everything should work just fine.

 

Can you please try to set up Jellyfin and see if it is working there, just to double check...

8 hours ago, Rhuarc said:

GPU stats dashboard but the dashboard shows this error

Please note that this is related to the GPU Statistics Plugin and is possibly caused because you didn't changed the UUID in the plugin settings.

Please also make sure to increase the polling rate from the plugin to something reasonable like 5000ms (=5s) or I would even recommend setting it to something higher than 20000ms (=20s).

 

8 hours ago, Rhuarc said:

I am also getting these errors trying to shutdown the server to pull diagnostics.

Are you sure that the card is working and don't has any issues?

Please double check that Above 4G Decoding alongside with Resizable BAR Support in your BIOS is enabled.

Hi @ich777,

 

Back in Feb2025 we discussed me running into a strange "nvidia-container-cli permission denied" error, seemingly out of nowhere, after I upgraded from Unraid 6.12.14--> 7.0. For reference, our discussion is here

 

Unfortunately, this issue hasn't gone away but I'm desperate for a solution. I downgraded from Unraid 7.0.1 --> 6.12.15 but still encounter the issue. I have removed the Nvidia driver plugin, turned docker on/off, rebooted, and reinstalled the Nvidia driver plugin again but still encounter the issue.

 

My question is, how can I "start fresh"? I need some help getting back to my previous state where this permissions issue doesn't happen anymore

 

Currently, my 2 main headaches that this permissions issue causes are:

 

1) I do a weekly, overnight appdata backup w/ the associated plugin. This plugin stops each docker, backs up it's appdata folder, and then restarts the container. So my Plex container (w/ Nvidia GPU) is stopped, backed up, but then can't restart again because of this nvidia-container-cli permissions error. Recall that my only workaround for this error is to install and then uninstall any plugin (I like using the CA GUI Links plugin for this but any seem to work), and then my Plex (or other docker w/ Nvidia GPU passed through) will start back up. So I end up with many hours of downtime until I'm able to manually install/uninstall a plugin the following morning and restart my Plex docker.

 

Idea - do you know if there is a way to install a plugin that's in the app store using the command line or using a script? If I could automate installing and then uninstalling a plugin using say a userscript, I could just configure that to run after my backup process. That would effectively work around this issue for me

 

2) 2nd major headache - I have my array set to auto start on boot, but my dockers w/nvidia gpu passed through always fail to start on first system boot until I install and then uninstall any plugin. This is a significant issue since I now have to manually monitor each boot. As above, if I could automate installing and uninstalling a plugin at first array start (like with a userscript), that would be a good workaround for this issue.

 

Final question - Alternatively, I'm willing to do the extreme - can I format my Unraid USB drive, install a fresh copy of Unraid 7.0.1 to it, and essentially remake my server from scratch? I've never done that before so I'm just not sure how it would work regarding not losing my 400 TB of data. If I reassign my hard drives to the array (I don't use parity) + assign my nvme cache drives to their respective, correctly named pools, would I be able to start my array without formatting my disks and access my data?

 

I appreciate any final advice you can give on this issue

Edited March 29, 20251 yr by msalad

50 minutes ago, msalad said:

I appreciate any final advice you can give on this issue

I would recommend that you grab a new flash drive, install Unraid and register trail on it.

After doing so, if possible connect a spare HDD to the server (a extrnal usb disk would also work and in the worst case a flash drive) boot into this installation, assign only the one spare HDD and start the Array, after starting the Array set the auto start to yes in the Desk Settings, install the Nvidia Driver and possibly Jellyfin or Plex with your Nvidia card assigned to the container and autostart for the container enabled.

Restart Unraid and see if you get the same error.

 

I really don‘t know what‘s going on on your system since you seem to be the only one with that issue, it wouldn‘t be the first time that someting in a User Script or somewhere else causes this issue, I guess it could be also related to the Hardware or some setting in your BIOS.

On 3/20/2025 at 4:53 AM, ich777 said:

Sorry currently I only compile the latest driver version from the open source driver which is available at the release from the Unraid version you are running.

This might change in the future but for now it is what it is, however if you are willing to upgrade to 7.1.0-beta.1 (which is stable since I run that on my production Server where I also compile and create the plugin packages for the 3rd party driver plugin) then you would be able to download this driver.

 

Background to that is that the plugin is in it's current state not fully able to detect the correct version if there are multiple version from the OpenSource driver in the repository available.

 

I hope that somehow helps, sorry for not having better news currently.

This is currently what is listed under "latest" correct? I have Unraid 7.0.1 installed and tried to get this NVIDIA driver for my 5090 to work but the Open Source Kernel Module says "NO" and the device is not found when doing nvidia-smi. It is however shown in lspci and also shows the constant error log of text repeating:

Mar 29 22:21:50 Tower kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:2b85)
Mar 29 22:21:50 Tower kernel: NVRM: installed in this system requires use of the NVIDIA open kernel modules.
Mar 29 22:21:50 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x56:884)
Mar 29 22:21:50 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Do I need to upgrade to the beta to get the open source module instead for the GPU?

3 hours ago, unmannedmedia said:

Do I need to upgrade to the beta to get the open source module instead for the GPU?

Please post your Diagnostics.

11 minutes ago, ich777 said:

Please post your Diagnostics.

Here it is: 

tower-diagnostics-20250330-0157.zip.crdownload

24 minutes ago, unmannedmedia said:

Here it is: 

You have to actually select the Open Source driver in the plugin at the radio buttons, then Click Update & Download, wait for the download to finish and then reboot.

 

By default the plugin installs the closed source driver.

11 minutes ago, ich777 said:

You have to actually select the Open Source driver in the plugin at the radio buttons, then Click Update & Download, wait for the download to finish and then reboot.

 

By default the plugin installs the closed source driver.

By radio buttons, do you mean the versions below the main three types? Near available versions?

 

Edited March 30, 20251 yr by unmannedmedia

18 minutes ago, unmannedmedia said:

By radio buttons, do you mean the versions below the main three types? Near available versions?

Please look again, the blue text at Latest Versions says Open Source Driver, this is the one you need for 5000 series.

8 minutes ago, ich777 said:

Please look again, the blue text at Latest Versions says Open Source Driver, this is the one you need for 5000 series.

Due to my ignorance, I assumed this version was not up to date and did not support 5000 series GPUs yet. Thank you for the support, as always!

4 hours ago, unmannedmedia said:

Due to my ignorance, I assumed this version was not up to date and did not support 5000 series GPUs yet. Thank you for the support, as always!

If you are mostly using the card for transcoding it doesn‘t matter much if you are one version behind, I might change my toolchain so that the latest version is also built for the open source driver.

I have to think about that a bit more…

3 hours ago, ich777 said:

If you are mostly using the card for transcoding it doesn‘t matter much if you are one version behind, I might change my toolchain so that the latest version is also built for the open source driver.

I have to think about that a bit more…

So I finally updated to "Open Source Driver: v570.86.16" but it shows "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 restarted the system before installing and after. Also ensured to enable and disable Docker too. Any reason why the supported version for 50 series doesn't work?

 

tower-diagnostics-20250330-1045.zip

Edited March 30, 20251 yr by unmannedmedia

19 minutes ago, unmannedmedia said:

So I finally updated to "Open Source Driver: v570.86.16" but it shows "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running."

Sorry but now I don't see a Nvidia Graphics card in your PCI devices list.

Are you sure that the card is seated properly and all power cables are attached.

 

What is this:

/tmp/user.scripts/tmpScripts/nvidia fans array start/script

 

If everything is connected properly please turn off your server entirely, pull the power cord from the wall, press the reset and power button a few times (to empty the caps on the motherboard), plug the power cord back into the wall and start your server.

This procedure seems a bit overkill but sometimes this helps with PCI devices not recognised.

5 minutes ago, ich777 said:

Sorry but now I don't see a Nvidia Graphics card in your PCI devices list.

Are you sure that the card is seated properly and all power cables are attached.

 

What is this:

/tmp/user.scripts/tmpScripts/nvidia fans array start/script

 

If everything is connected properly please turn off your server entirely, pull the power cord from the wall, press the reset and power button a few times (to empty the caps on the motherboard), plug the power cord back into the wall and start your server.

This procedure seems a bit overkill but sometimes this helps with PCI devices not recognised.

That script is from a while ago when I had an NVIDIA card installed before this. I will remove it. As for the PCIE detection, I do have a Windows boot drive installed to test if it was detected. It is showing up in Windows at least. I did followed the instructions and booted the Unraid machine, I am seeing what you mean by it not being detected. Before it had been with lspci.

Let me know if I should do anything further.

Thank you for your support as always!

tower-diagnostics-20250330-1121.zip

1 hour ago, unmannedmedia said:

Let me know if I should do anything further.

Sorry but I can‘t help if it‘s not detected in your System, that‘s a thing that you have to figure out.

 

In the first Diagnostics that you‘ve sent it was detected just fine (please note that this has nothing to do with the driver sonce the driver wont do anything if no GPU is detected). 

 

Please check your BIOS settings that Resizable BAR and above 4G Decoding is enabled. Maybe also try to setting the PCIe slot to Gen 4 since it seems some 5000 series cards have issues with Gen5 on some Motherboards.

 

Did you already try the procedure that I recommended above?

1 hour ago, ich777 said:

Sorry but I can‘t help if it‘s not detected in your System, that‘s a thing that you have to figure out.

 

In the first Diagnostics that you‘ve sent it was detected just fine (please note that this has nothing to do with the driver sonce the driver wont do anything if no GPU is detected). 

 

Please check your BIOS settings that Resizable BAR and above 4G Decoding is enabled. Maybe also try to setting the PCIe slot to Gen 4 since it seems some 5000 series cards have issues with Gen5 on some Motherboards.

 

Did you already try the procedure that I recommended above?

Just tried each of those options. Still no luck. Also disabled IGPU too since I have intel CPU, but that didn't change anything.

On 3/29/2025 at 5:37 AM, ich777 said:

I would recommend that you grab a new flash drive, install Unraid and register trail on it.

After doing so, if possible connect a spare HDD to the server (a extrnal usb disk would also work and in the worst case a flash drive) boot into this installation, assign only the one spare HDD and start the Array, after starting the Array set the auto start to yes in the Desk Settings, install the Nvidia Driver and possibly Jellyfin or Plex with your Nvidia card assigned to the container and autostart for the container enabled.

Restart Unraid and see if you get the same error.

 

I really don‘t know what‘s going on on your system since you seem to be the only one with that issue, it wouldn‘t be the first time that someting in a User Script or somewhere else causes this issue, I guess it could be also related to the Hardware or some setting in your BIOS.

Hey @ich777,

 

I did the steps you indicated. Plex booted with my nvidia gpu passed through without issue. I installed the gpu statistics plugin and it worked as expected.

 

I also have an intel A310 gpu in my server and was able to install intel_gpu_top, which worked as expected as well. Interestingly, in my original server, the gpu statistics plugin only works with my nvidia gpu, not my intel gpu. Not sure if this is relevant but just wanted to give you as much info as I can. This reminded me that I also installed intel_gpu_top while still on unraid 6.12.14, immediately before upgrading to unraid 7.0.0. Maybe that caused a conflict?

 

It seems like something is broken with my original server and is not related to my hardware. I think it's time to format my original usb, install fresh unraid 7.0.1, and rebuild my server piece by piece. Would you agree?

Edited March 30, 20251 yr by msalad

5 minutes ago, msalad said:

also have an intel A310 gpu in my server and was able to install intel_gpu_top, which worked as expected as well. Interestingly, in my original server, the gpu statistics plugin only works with my nvidia gpu, not my intel gpu. Not sure if this is relevant but just wanted to give you as much info as I can

A310 needs change to intel top timers, Latest version of GPU stat and top fix this so check you are on the latest.

17 minutes ago, unmannedmedia said:

Just tried each of those options. Still no luck. Also disabled IGPU too since I have intel CPU, but that didn't change anything.

Sorry but I can't help with that since it's not even recognised by the system.

If it would be recognised by the system it should however work.

18 minutes ago, SimonF said:

A310 needs change to intel top timers, Latest version of GPU stat and top fix this so check you are on the latest.

After looking at your plugin's changelogs, this was likely the issue. I was using v2025.03.18 at the latest at the time

Edited March 30, 20251 yr by msalad

@unmannedmedia just to let you know, here is a thread from a user also with a 5000 series card who solved his issue by setting the PCIe slot to Gen4:

Please note that this is not related to the Nvidia Driver Plugin since he had issues passing it to a VM (at least that is what I've read when I flew over the thread, sorry time is cheap ).