Jump to content
linuxserver.io

[Plugin] Linuxserver.io - Unraid Nvidia

2361 posts in this topic Last Reply

Recommended Posts

16 hours ago, bradtn said:

 

Im getting this over and over and over in my syslog since patching and implementing a 1070ti into my setup with plex. Is this an error? is it normal? does it even matter? I have the card in a 16x slot if this matters or not.

cap.PNG

 

It doesn't look normal. But I have no idea what it means. Probably best to ask Google and see if it comes up with something.

Share this post


Link to post
 
It doesn't look normal. But I have no idea what it means. Probably best to ask Google and see if it comes up with something.
Yeah I got no ideas either.

Sent from my Mi A1 using Tapatalk

Share this post


Link to post
9 hours ago, saarg said:

 

It doesn't look normal. But I have no idea what it means. Probably best to ask Google and see if it comes up with something.

Are you using an AMD processor?

 

I get the same error's.

 

Nvidia trips AMD's processor security.

 

I have no more issues with my 1660 hardlocking my system because I disabled encrypted memory on boot.

 

mem_encrypt=off

 

No idea if Nvidia or AMD will fix it..

 

I don't have accounts to report it to AMD linux people nor nvidia.

Share this post


Link to post
2 hours ago, Dazog said:

Are you using an AMD processor?

 

I get the same error's.

 

Nvidia trips AMD's processor security.

 

I have no more issues with my 1660 hardlocking my system because I disabled encrypted memory on boot.

 

mem_encrypt=off

 

No idea if Nvidia or AMD will fix it..

 

I don't have accounts to report it to AMD linux people nor nvidia.

I am! Ryzen 1950x I'll have to try this, thx! Are you saying this is on my motherboard settings or? 

Edited by bradtn

Share this post


Link to post
19 minutes ago, bradtn said:

I am! Ryzen 1950x I'll have to try this, thx! Are you saying this is on my motherboard settings or? 

mem_encrypt=off needs to be added at boot for unraid.

Share this post


Link to post
40 minutes ago, Dazog said:

mem_encrypt=off needs to be added at boot for unraid.

Does this apply to the 2920X as well? I was having hard crashes every 4 days, but it seemed like it was plex crashing, from the few logs that were actually being saved (plex fatal error script not found or something like that). If this applies to me too, then I wonder if one caused the other (I had 2 NVIDIA GPUs, and added a third for transcoding.) Anyways, this is the first time I’m hearing of this flag being used. 

 

Is it placed in the go file, or MAIN > Flash Drive, flags?

Share this post


Link to post
9 hours ago, urhellishntemre said:

Does this apply to the 2920X as well? I was having hard crashes every 4 days, but it seemed like it was plex crashing, from the few logs that were actually being saved (plex fatal error script not found or something like that). If this applies to me too, then I wonder if one caused the other (I had 2 NVIDIA GPUs, and added a third for transcoding.) Anyways, this is the first time I’m hearing of this flag being used. 

 

Is it placed in the go file, or MAIN > Flash Drive, flags?

Applies to Threadripper and possibly ryzen.

 

I can only confirm Threadripper. Since it's what I use.

Share this post


Link to post
7 hours ago, Dazog said:

Applies to Threadripper and possibly ryzen.

 

I can only confirm Threadripper. Since it's what I use.

Can you explain exactly where to put that flah and how to initially apply it? Thanks 

Share this post


Link to post
3 hours ago, bradtn said:

Can you explain exactly where to put that flah and how to initially apply it? Thanks 

Under Syslinux configuration

 

add to unRAID OS section.

Share this post


Link to post
11 hours ago, Dazog said:

Under Syslinux configuration

 

add to unRAID OS section.

I added that line in the place you indicated. Rebooted. I noticed and I don't know if this was also the reason before or not but the image I pasted above with my log I still see it in my log when I have the watch Nvidia-smi running in terminal. 

Share this post


Link to post
On 2/25/2019 at 7:47 AM, depreciated_ said:

I've been doing a lot of testing with the 1050ti and rtx 2080's in the past few days.  In regards to decoding on linux, the video quality on 4k content is very poor with pascal.  The new turing architecture uses much better decoder on the chip and for another 80 bucks, its worth it for me to upgrade to an 1660.  Also more vram :)

 

https://www.nvidia.com/content/dam/en-zz/Solutions/design-visualization/technologies/turing-architecture/NVIDIA-Turing-Architecture-Whitepaper.pdf

 

Did you end up getting the 1660? I ask because i have the 1050ti, presently.. but considering upgrading to the 1660 if it means significant (as in immediately noticeable) transcoded video quality performance

 

Does anyone have an image comparison between pascal and turing?

Edited by pimogo

Share this post


Link to post
4 minutes ago, pimogo said:

 

Did you end up getting the 1660? I ask because i have the 1050ti, presently.. but considering upgrading to the 1660 if it means significant (as it immediately noticeable) transcoded video quality.

 

Does anyone have an image comparison between pascal and turing?

Now y'all have me thinking... This may be the solution to the artifact issue I posted about a while back. The P4000 is Pascal based. I need more than 2 transcodes at a time, so it's gotta be a Quadro. It looks like I could flip my current card and cover about 75% of the new one. If it fixes the issue, that's worth it. Is there anyone out there using an RTX 4000?

Share this post


Link to post

v6.7.1rc1 just uploading.

Share this post


Link to post

I've been kicking around with this all day and hoping someone can help. I've successfully added the --runtime=nvidia parameter and the NVIDIA_DRIVER_CAPABILITIES variable and plex updates and starts. However, adding NVIDIA_VISIBLE_DEVICES variable with the UUID value (or 0 or all) throws up the following:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-0e64b88f-fa47-56a5-d740-5f989b63fc65' -v '/mnt/user/appdata/plex':'/config':'rw' --runtime=nvidia 'linuxserver/plex' 
458cbf493f1f14c2f87df492eb789360284d4ed61b3f24bcf8e23fd61fbb405e
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused "process_linux.go:407: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/local/bin/nvidia-container-cli --load-kmods --debug=/var/log/nvidia-container-runtime-hook.log --ldcache=/etc/ld.so.cache configure --ldconfig=@/sbin/ldconfig --device=GPU-0e64b88f-fa47-56a5-d740-5f989b63fc65 --compute --compat32 --graphics --utility --video --display --pid=11393 /var/lib/docker/btrfs/subvolumes/bbb1ee999ab52a47f5db1e25ffe306072910df3fafff7d19c1c72d092e7e8f8d]\\nnvidia-container-cli: initialization error: cuda error: initialization error\\n\""": unknown.

The command failed.

 

The log:

 

May 19 15:57:08 Tower login[10845]: ROOT LOGIN on '/dev/pts/0'
May 19 15:57:15 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000d7fff window]
May 19 15:57:15 Tower kernel: caller _nv000934rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
May 19 15:59:33 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000d7fff window]
May 19 15:59:33 Tower kernel: caller _nv000934rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
May 19 15:59:33 Tower kernel: nvidia 0000:01:00.0: swiotlb buffer is full (sz: 4194304 bytes)
May 19 15:59:33 Tower kernel: nvidia 0000:01:00.0: swiotlb buffer is full

 

 

Share this post


Link to post
25 minutes ago, u13rr1 said:

I've been kicking around with this all day and hoping someone can help. I've successfully added the --runtime=nvidia parameter and the NVIDIA_DRIVER_CAPABILITIES variable and plex updates and starts. However, adding NVIDIA_VISIBLE_DEVICES variable with the UUID value (or 0 or all) throws up the following:

 


root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-0e64b88f-fa47-56a5-d740-5f989b63fc65' -v '/mnt/user/appdata/plex':'/config':'rw' --runtime=nvidia 'linuxserver/plex' 
458cbf493f1f14c2f87df492eb789360284d4ed61b3f24bcf8e23fd61fbb405e
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused "process_linux.go:407: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/local/bin/nvidia-container-cli --load-kmods --debug=/var/log/nvidia-container-runtime-hook.log --ldcache=/etc/ld.so.cache configure --ldconfig=@/sbin/ldconfig --device=GPU-0e64b88f-fa47-56a5-d740-5f989b63fc65 --compute --compat32 --graphics --utility --video --display --pid=11393 /var/lib/docker/btrfs/subvolumes/bbb1ee999ab52a47f5db1e25ffe306072910df3fafff7d19c1c72d092e7e8f8d]\\nnvidia-container-cli: initialization error: cuda error: initialization error\\n\""": unknown.

The command failed.

 

The log:

 


May 19 15:57:08 Tower login[10845]: ROOT LOGIN on '/dev/pts/0'
May 19 15:57:15 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000d7fff window]
May 19 15:57:15 Tower kernel: caller _nv000934rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
May 19 15:59:33 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000d7fff window]
May 19 15:59:33 Tower kernel: caller _nv000934rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
May 19 15:59:33 Tower kernel: nvidia 0000:01:00.0: swiotlb buffer is full (sz: 4194304 bytes)
May 19 15:59:33 Tower kernel: nvidia 0000:01:00.0: swiotlb buffer is full

 

 

 

 

I'm also having no luck, my log file is showing this too: 

May 19 16:30:10 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000d7fff window]
May 19 16:30:10 Tower kernel: caller _nv000939rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs

Clean Unraid install, latest version. Emby doesn't show the GPU

 

Specs:

 

CPU: i7-3770S

MB: ASRock Z77 Extreme11

RAM 24GB

GPU: 1050Ti

 

Share this post


Link to post
7 hours ago, u13rr1 said:

I've been kicking around with this all day and hoping someone can help. I've successfully added the --runtime=nvidia parameter and the NVIDIA_DRIVER_CAPABILITIES variable and plex updates and starts. However, adding NVIDIA_VISIBLE_DEVICES variable with the UUID value (or 0 or all) throws up the following:

 


root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-0e64b88f-fa47-56a5-d740-5f989b63fc65' -v '/mnt/user/appdata/plex':'/config':'rw' --runtime=nvidia 'linuxserver/plex' 
458cbf493f1f14c2f87df492eb789360284d4ed61b3f24bcf8e23fd61fbb405e
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused "process_linux.go:407: running prestart hook 0 caused \"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/local/bin/nvidia-container-cli --load-kmods --debug=/var/log/nvidia-container-runtime-hook.log --ldcache=/etc/ld.so.cache configure --ldconfig=@/sbin/ldconfig --device=GPU-0e64b88f-fa47-56a5-d740-5f989b63fc65 --compute --compat32 --graphics --utility --video --display --pid=11393 /var/lib/docker/btrfs/subvolumes/bbb1ee999ab52a47f5db1e25ffe306072910df3fafff7d19c1c72d092e7e8f8d]\\nnvidia-container-cli: initialization error: cuda error: initialization error\\n\""": unknown.

The command failed.

 

The log:

 


May 19 15:57:08 Tower login[10845]: ROOT LOGIN on '/dev/pts/0'
May 19 15:57:15 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000d7fff window]
May 19 15:57:15 Tower kernel: caller _nv000934rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
May 19 15:59:33 Tower kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d4000-0x000d7fff window]
May 19 15:59:33 Tower kernel: caller _nv000934rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
May 19 15:59:33 Tower kernel: nvidia 0000:01:00.0: swiotlb buffer is full (sz: 4194304 bytes)
May 19 15:59:33 Tower kernel: nvidia 0000:01:00.0: swiotlb buffer is full

 

 

 

Did you copy/paste the variables and runtime from the forum?

if you did, delete it and type it in manually. There is a bug on the forum that adds an invisible character.

Share this post


Link to post

Might be nice if you told us what version of Unraid you're using too.

All the releases other than v6.7.1rc1 are tested.

Not sure I've seen any reports of that yet.

Sent from my Mi A1 using Tapatalk

Share this post


Link to post

The fields were all typed, not copied and pasted. I've tried multiple times. 

 

Version is 6.7.0

 

Im using a GTX1050, which I can see from nvidia-smi so not a hardware issue. 

Share this post


Link to post
The fields were all typed, not copied and pasted. I've tried multiple times. 
 
Version is 6.7.0
 
Im using a GTX1050, which I can see from nvidia-smi so not a hardware issue. 
And the card isn't being used by a VM?

Sent from my Mi A1 using Tapatalk

Share this post


Link to post
32 minutes ago, CHBMB said:

And the card isn't being used by a VM?

Sent from my Mi A1 using Tapatalk
 

No VMs have ever run on this hardware.

Share this post


Link to post
No VMs have ever run on this hardware.
Screenshot of the plugin page please. This is strange, we know v6.7.0 is working, so it must be something specific to you.

Sent from my Mi A1 using Tapatalk

Share this post


Link to post

tonight my plex app crashed caused my unraid server to need a reboot upon doing so i had a problem loading plex and emby up, I looked in the logs to see 

 kernel: nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 245
 kernel: NVRM: RmInitAdapter failed! (0x31:0xffff:834)
 kernel: NVRM: rm_init_adapter failed for device bearing minor number 0
 iceberg kernel: NVRM: RmInitAdapter failed! (0x31:0xffff:834)
 kernel: NVRM: rm_init_adapter failed for device bearing minor number 0
 rc.docker: PlexMediaServer: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:407: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/local/bin/nvidia-container-cli --load-kmods --debug=/var/log/nvidia-container-runtime-hook.log --ldcache=/etc/ld.so.cache configure --ldconfig=@/sbin/ldconfig --device=GPU-cc63faa0-8033-52ac-dad4-79279b371033 --compute --compat32 --graphics --utility --video --display --pid=31670 /var/lib/docker/btrfs/subvolumes/4787b541f516ce4d01faa8f10f4dfed05c53589f0b299ae78d883bc14cdc346d]\\\\nnvidia-container-cli: device error: unknown device id: GPU-cc63faa0-8033-52ac-dad4-79279b371033\\\\n\\\"\"": unknown
 rc.docker: Error: failed to start containers: PlexMediaServer
 kernel: NVRM: RmInitAdapter failed! (0x31:0xffff:834)
 kernel: NVRM: rm_init_adapter failed for device bearing minor number 0
 kernel: NVRM: RmInitAdapter failed! (0x31:0xffff:834)
 kernel: NVRM: rm_init_adapter failed for device bearing minor number 0
 rc.docker: EmbyServer: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:407: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/local/bin/nvidia-container-cli --load-kmods --debug=/var/log/nvidia-container-runtime-hook.log --ldcache=/etc/ld.so.cache configure --ldconfig=@/sbin/ldconfig --device=GPU-cc63faa0-8033-52ac-dad4-79279b371033 --compute --compat32 --graphics --utility --video --display --pid=32044 /var/lib/docker/btrfs/subvolumes/6ea3c2c0c5428be0afad1d23b1f459f821776f1dcf923641c55aae2b4acdd312]\\\\nnvidia-container-cli: device error: unknown device id: GPU-cc63faa0-8033-52ac-dad4-79279b371033\\\\n\\\"\"": unknown
 rc.docker: Error: failed to start containers: EmbyServer

and when i went in to my nvidia plugin my p2000 does not show up but it is listed in iommu group 28 under system devices, I'm on ver 6.7

Share this post


Link to post

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.