1 hour ago, mark2741 said:

Yesterday I opened top and did a kill cmd on the nv_open_q. Checked back a minute or two later and the CPU was no longer spiking. So definitely that process is the cause.

Are you sure that you are not on the Dashboard when you do this because GPU Statistics will call nvidia-smi every N seconds that you've specified it in the settings from GPU Statistics, please note that any open Dashboard page on any device will cause this.

 

Please note that if you set the interval really tight (2 seconds) then it will definitely cause spikes because GPU Statistics will call every 2 seconds nvidia-smi

 

My guess is since if you installed new Hardware you where often times on the Dashboard page to see if everything is working and you now noticed that.

 

1 hour ago, mark2741 said:

nv_open_q

Please see this post:

https://github.com/NVIDIA/open-gpu-kernel-modules/discussions/615#discussioncomment-9789092

 

However I can't do anything about that since this seems to be a driver issue and not much people seem to be affected from that behaviour, I also don't think that changing the RAM will cause such a behaviour.

 

You can try to switch to a different driver verions, somethin

1 hour ago, mark2741 said:

After confirming that and running memtest (passed for 5+ hours) I booted and noticed that it said something about installing the nvidia open source driver? I just pressed enter and moved on and didn't think about it. 

Where did it say that and where did you need to press enter?

If this was the case something weird is going on on your system, you have to never press Enter or anything like that with the driver plugin, I also see from your syslog that the proprietary driver was installed and loaded:

Nov 17 09:22:13 UNRAID kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  565.57.01  Thu Oct 10 12:29:05 UTC 2024
Nov 17 09:22:13 UNRAID kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  565.57.01  Thu Oct 10 12:02:00 UTC 2024
Nov 17 09:22:13 UNRAID kernel: [drm] [nvidia-drm] [GPU ID 0x00002600] Loading driver
Nov 17 09:22:13 UNRAID kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:26:00.0 on minor 0

 

 

The drivers that you are installing and the ones are installed by default are still based on the proprietary Kernel module, only if you select the Open Source driver, which you can select no the plugin page it will use the Open Source one.

 

1 hour ago, mark2741 said:

I had already had an nvidia card installed and plugin installed with the "latest branch" nvidia driver running fine with no issues so was surprised to see the reference to the open source driver install popping up. 

I'm also surprised because I don't see any indication that it actually installed the Open Source one.

 

 

Thank you so much. You were right - this is only happening when I am viewing the Dashboard. To confirm, I opened the terminal window and then switched off of the Dashboard and immediately the nv_open_q process stopped using any resources. I will ignore when viewing that Dashboard page. I did drop the polling interval of gpu-stats to 5000ms, which reduced CPU spiking by about half but still odd to me that it would do it. Thank you for your help!

Edited November 17, 20241 yr by mark2741
added gpu-stat interval

On 11/15/2024 at 4:33 PM, ich777 said:

Please post your Diagnostics.

 

Do you maybe also have Diagnostics when this happens?

I didn't take diagnostics at the time. I have current diags.  When it happens next time what is the process for getting the correct diags?  It will most likely need a dirty restart. If I get the diags after restart will that work?

1 hour ago, Davo67 said:

When it happens next time what is the process for getting the correct diags?

Connect trough SSH if the webui isn‘t responding and enter: diagnostics

This will create diagnoctigs in /boot/logs

 

If the webui is still responding the creat them the usual way.

Having issues today trying to update my plugin version

root@tower:~# /usr/local/emhttp/plugins/nvidia-driver/include/exec.sh update_version latest

+==============================================================================
| WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
|
| Don't close this window with the red 'X' in the top right corner until the 'DONE' button is displayed!
|
| WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
+==============================================================================

----------------Downloading Nvidia Driver Package v470.239.06-----------------
---------This could take some time, please don't close this window!------------
/boot/config/plugins/nvidia-driver/packages/6.1.106/nvidia-470.239.06-6.1.106-Unraid-1.txz
nvidia-550.107.02-6.1.106-Unraid-1.txz
nvidia-550.120-6.1.106-Unraid-1.txz
nvidia-550.127.05-6.1.106-Unraid-1.txz
nvidia-560.35.03-6.1.106-Unraid-1.txz
nvidia-565.57.01-6.1.106-Unraid-1.txz: Invalid argument

---------------Can't download Nvidia Driver Package v470.239.06----------------
root@tower:~# /usr/local/emhttp/plugins/nvidia-driver/include/exec.sh update_version latest_prb

+==============================================================================
| WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
|
| Don't close this window with the red 'X' in the top right corner until the 'DONE' button is displayed!
|
| WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
+==============================================================================

----------------Downloading Nvidia Driver Package v470.239.06-----------------
---------This could take some time, please don't close this window!------------
/boot/config/plugins/nvidia-driver/packages/6.1.106/nvidia-470.239.06-6.1.106-Unraid-1.txz
nvidia-550.107.02-6.1.106-Unraid-1.txz
nvidia-550.120-6.1.106-Unraid-1.txz
nvidia-550.127.05-6.1.106-Unraid-1.txz
nvidia-560.35.03-6.1.106-Unraid-1.txz
nvidia-565.57.01-6.1.106-Unraid-1.txz: Invalid argument

---------------Can't download Nvidia Driver Package v470.239.06----------------
root@tower:~# ll /boot/config/plugins/nvidia-driver/packages/6.1.106
total 243M
-rw------- 1 root   33 Aug 22 00:26 nvidia-560.35.03-6.1.106-Unraid-1.txz.md5
-rw------- 1 root 243M Aug 22 00:26 nvidia-560.35.03-6.1.106-Unraid-1.txz
drwx------ 2 root  16K Sep  6 07:40 ./
drwx------ 3 root  16K Sep  6 07:40 ../
root@tower:~# ll /boot/config/plugins/nvidia-driver/packages/
total 48K
drwx------ 2 root 16K Sep  6 07:40 6.1.106/
drwx------ 3 root 16K Sep  6 07:40 ./
drwx------ 3 root 16K Nov 18 19:35 ../

 

3 hours ago, sethwv said:

Having issues today trying to update my plugin version

The plugin is broken, you‘ll see that on the two php warnings on the page.

 

Please do the following:

1. Uninstall the Nvidia driver plugin,
2. Reboot
3. Pull a fresh copy from the CA App
4. Go to the Nvidida Plugins website and slelct the driver that you want to use
5. Reboot again

@ich777 Thank you! The provided steps & guidance worked.

Hello All,

 

HW transcode not working.

• PMS Version 1.41.2.9200
• Followed ICH777 instructions above
• "Installation of Nvidia driver v565.57.01 successful"
• GPUID in Plex docker config matches Nvidia plugin info
• nvidia-smi sees the GPU
• NVIDIA_VISIBLE_DEVICES added
• I don't see any place to add:  '--runtime=nvidia' to the 'Extra Parameters

But HW transcode is not working:

Nov 22, 2024 17:35:47.787 [22699250924344] ERROR - [Req#2bd/Transcode] [FFMPEG] - Cannot load libnvidia-encode.so.1
Nov 22, 2024 17:35:47.787 [22699250924344] ERROR - [Req#2bd/Transcode] [FFMPEG] - The minimum required Nvidia driver for nvenc is 455.28 or newer

 

Edited November 23, 20241 yr by Bladedude

1 hour ago, Bladedude said:

But HW transcode is not working:

this looks more like an issue with your docker, which one are you using ?

 

and which driver version is installed on the host ?

58 minutes ago, alturismo said:

this looks more like an issue with your docker, which one are you using ?

 

and which driver version is installed on the host ?

PlexInc. Repository plexinc/pms-docker:latest

From Nvidia driver plugin: Nvidia Driver Version: 565.57.01

3 minutes ago, Bladedude said:

PlexInc. Repository plexinc/pms-docker:latest

 

looking good, may post your docker run <<click<< here and also may look at the plex forums if there are any issues with the latest update ... they are currently working on the transcoder engine.

Works now. I was missing "NVIDIA_DRIVER_CAPABILITIES" parameter.

However, when I set this up 2 months ago, I didn't have that parameter. I was following a YT from AlienTech, but this guide is much better.

And I still can't find where to add '--runtime=nvidia' to the 'Extra Parameters'" to complete all the documented steps from the guide.

 

docker run
  -d
  --name='Plex-Media-Server'
  --net='host'
  --pids-limit 2048
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="supermicro"
  -e HOST_CONTAINERNAME="Plex-Media-Server"
  -e 'PLEX_CLAIM'='Insert Token from https://plex.tv/claim'
  -e 'PLEX_UID'='99'
  -e 'PLEX_GID'='100'
  -e 'VERSION'='latest'
  -e 'NVIDIA_VISIBLE_DEVICES'='GPU-XXX'
  -e 'NVIDIA_DRIVER_CAPABILITIES'='all'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/plexinc/pms-docker/master/img/plex-server.png'
  -v '/mnt/user/data/media':'/data/media':'rw'
  -v '/dev/shm':'/transcode':'rw'
  -v '/mnt/user/appdata/Plex-Media-Server':'/config':'rw'
  --runtime=nvidia 'plexinc/pms-docker'

The command finished successfully!

 

Edited November 23, 20241 yr by Bladedude

1 minute ago, Bladedude said:

And I still can't find where to add '--runtime=nvidia' to the 'Extra Parameters'" to complete all the documented steps from the guide.

Did you follow this tutorial:

You have to enable Advanced View in the Docker template at the top right.

 

If this parameter is not present it shouldn‘t work.

17 minutes ago, ich777 said:

Did you follow this tutorial:

You have to enable Advanced View in the Docker template at the top right.

 

If this parameter is not present it shouldn‘t work.

Yes. I followed the tutorial.

Ah OK. Once Advanced View was enabled, I saw that I had already added "--runtime=nvidia" during initial setup.

 

Today I noticed HW transcode wasn't working, but had been working 1-2 months ago, so I:

1. Uninstalled, reinstalled the Nvidia plugin, and installed the latest Nvidia driver. No change, same Plex error in log

2. Followed the tutorial, and added NVIDIA_DRIVER_CAPABILITIES parameter. HW transcode works.

Not sure how HW transcode was working on initial setup w/o NVIDIA_DRIVER_CAPABILITIES set..

Edited November 23, 20241 yr by Bladedude

28 minutes ago, Bladedude said:

Today I noticed HW transcode wasn't working

So it still isn‘t working?

Please post your Diagnostics.

14 minutes ago, ich777 said:

So it still isn‘t working?

Please post your Diagnostics.

It's working now, since I added NVIDIA_DRIVER_CAPABILITIES.

I recently noticed an issue when i upgraded to version 6.12.14 with my GTX 1070.

 

i get an error nvidia smi not found.  

 

I tried a few to reinstall the nvidia plugin. 

I tried to reseat the GPU.  The GPU lights up and  fans spins.

GPU is not listed in terminal when listing all the devices connected to the server (lspci) 

I tried downgrading to 6.12.13, but that did not help.

i tried to remove the contents of this folder /boot/config/plugins/nvidia-driver/packages/6.1.118/

 

i tried to set is as an open source driver.  after reboot i could see the gpu for a few min and then i got an different error.-  i dont have an screenshots of the other error.

 

 

 

does anyone have an suggestions?  i also added the diagnostics too 

 

Than you for your help

 

gormuck-diagnostics-20241128-0829.zip

4 hours ago, frothy said:

does anyone have an suggestions?  i also added the diagnostics too 

 

driver installation looking ok, but the card is "not there"

 

so i assume you already checked the seating, power supply, .. may take a look if something went loose,

also BIOS, above 4g decode and rbar activated if possible.

 

only concern i would see, many errors here ...

 

Nov 27 23:59:00 Gormuck kernel: I/O error, dev sr0, sector 49144 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Nov 27 23:59:00 Gormuck kernel: sr 0:0:0:1: [sr0] tag#0 unaligned transfer

 

but actually i cant tell if they could be related somehow ...

9 minutes ago, alturismo said:

driver installation looking ok, but the card is "not there"

 

so i assume you already checked the seating, power supply, .. may take a look if something went loose,

also BIOS, above 4g decode and rbar activated if possible.

 

only concern i would see, many errors here ...

 

Nov 27 23:59:00 Gormuck kernel: I/O error, dev sr0, sector 49144 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Nov 27 23:59:00 Gormuck kernel: sr 0:0:0:1: [sr0] tag#0 unaligned transfer

 

but actually i cant tell if they could be related somehow ...

The 1070 worked fine up until a few days ago.  I can try to test with a different NVIDIA graphics card.

 

is there anything i can do about the errors?

54 minutes ago, frothy said:

The 1070 worked fine up until a few days ago.  I can try to test with a different NVIDIA graphics card.

Have you yet tried to fully shutdown the server, pull the power cord from the wall, press the power and reset button a few times (to empty the caps), wait for at least a minute, plug the server back into the wall and try to boot?

 

Maybe something just hangs, if that also doesn't help the card might be defective...

The power pins were not seated properly in the GPU.  EVERYTHING WORKS.  Thank you for your help.  Much appreciated.

After upgrading to rc-1 I noticed kasm stopped working. Upon further investigation it seems the latest 565 driver does not create the requisite /sys/class/drm entries. Downgrading to 560 "new feature branch" fixes it. 

Unsure if this is an issue with the plugin, the nvidia driver, or rc-1, but posting here first since if nothing else I'll be redirected accordingly.

Edited December 4, 20241 yr by Spitko

2 hours ago, Spitko said:

Unsure if this is an issue with the plugin, the nvidia driver, or rc-1, but posting here first since if nothing else I'll be redirected accordingly.

Thank you for the report, I will look into this ASAP and report back!

3 hours ago, Spitko said:

After upgrading to rc-1 I noticed kasm stopped working.

Sorry but I can't reproduce this over here and everything seem to work totally fine:
 

 

 

Even transcoding works fine:

 

 

It would be super helpful if you could pull the Diagnostics next time when this happens so that I can take a deeper look why it was not working for you.

Hi @ich777,

 

I am having an issue with Jellyfin transcoding ffmpegs. I read through a few of the previous posts on this issue and the solutions there don't seem to be what I am looking for. 

 

Based on the versioning issue shown in the log I updated the driver, but for some reason this still seems to be an issue. Any direction you can point me in would be helpful. Thank!

 

Nvidia-smi screenshot as well:

error_log.txt