I've noticed that since my upgrade to a 5070 that when a Playback fails for whatever reason, which also happens more often than when I had a 3060, the card then disappears and can't be used unless the server is restarted completely.

Is there any reason why this would be, or what I could do to help?

4 hours ago, lukeb873 said:

Is there any reason why this would be, or what I could do to help?

Please post your Diagnostics, I can't say anything without them.

I had a question @ich777
If i'm getting this correctly , if you pick anything else than open source driver within the latest versions options you'll get a proprietary driver.
If you pick from the available versions you'll also get proprietary driver right ?
Is it possible to change this behavior with a toggle (open source / proprietary) that would allow you to install whatever driver version you want (in the case there is a bug on a release) for open source as well as proprietary as the demand is growing with new rtx 5000 being used ?

38 minutes ago, micka said:

If you pick from the available versions you'll also get proprietary driver right ?

Yes.

38 minutes ago, micka said:

Is it possible to change this behavior with a toggle (open source / proprietary) that would allow you to install whatever driver version you want (in the case there is a bug on a release) for open source as well as proprietary as the demand is growing with new rtx 5000 being used ?

No, since shortly everything is changing and only the Open Source driver will be available and the Proprietary driver becomes the new Legacy Driver which is currently driver version 470.x which should be after the transition driver version 580.x

And no, that wouldn't let you install any driver version you want since every driver package that you see in the plugin is pre-compiled for each individual Kernel version for Unraid.

On 8/26/2025 at 6:30 AM, ich777 said:

Please post your Diagnostics, I can't say anything without them.

I'm not Luke, but I had a similar issue where my GPU "disappears" every few days. I've attached my diagnostics. I was searching through the thread when I saw his recent post and went "It might be related, let me just post before I go diving back through 200 pages."

Additional Information:

• Two weeks ago, I had two 3060 GPU's. Both GPU's would disappear at seemingly random intervals (2-4 days). I was using the Production Driver at that point.

• Last week, I changed to a 5070ti and switched to the Open-Source Driver. The issue persists, with the GPU regularly disappearing after a few days.

• Similarly, I need to fully reboot the machine to make it reappear.

tower-diagnostics-20250827-1342.zip

1 hour ago, mrguymiah said:

Luke

Can you please try to upgrade to the latest Unraid beta version and see if the issue persits?

3 hours ago, ich777 said:

Can you please try to upgrade to the latest Unraid beta version and see if the issue persits?

With respect, I'm cautious of risking my data on a beta version. Is this a targeted resolution step or just covering the usual bases of ensuring everything is updated?

6 hours ago, mrguymiah said:

With respect, I'm cautious of risking my data on a beta version. Is this a targeted resolution step or just covering the usual bases of ensuring everything is updated?

No worries, then you'll have to wait for the next release from Unriad but I already have two confirmations that on the new beta everything is working as expected.

12 hours ago, ich777 said:

No worries, then you'll have to wait for the next release from Unriad but I already have two confirmations that on the new beta everything is working as expected.

So it's a targeted step. I'll take a look through information about the beta tonight. If I confirm the low risk to my data, I'll let you know if that resolves the problem.

Hi, thanks for the contributions on the community first of all.

I got a trouble with driver for Nvidia Tesla A2.

I recently bought and installed Nvidia Tesla A2 from second-hand market because the guy with the black leather jacket abandoned the supportation of my les petits GTX960 working on Frigate NVR.

I checked the latest driver for Nvidia Tesla A2 on official driver download webpage, and the version was 580.65.06, which is also available on the plugin.

But after selecting and installing the version of it, it showed "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver."

after that, I tried all the driver available -production, new feature, open source- but all those didn't work.

I can see there is a device on lspci command,

01:00.0 3D controller [0302]: NVIDIA Corporation GA107GL [A2 / A16] [10de:25b6] (rev a1)

Subsystem: NVIDIA Corporation Device [10de:157e]

Kernel modules: nouveau, nvidia_drm, nvidia

So I tried running .run script from the official driver website, but gcc was not available and the NerdTools was abandoned and didn't work either.

After trying all the things above, I got no clue how to overcome with this, so I post my situation on here.

I attached my diagnostics on here.

Great regards.

tower-diagnostics-20250830-1457.zip

9 hours ago, g0nd0l4 said:

I got a trouble with driver for Nvidia Tesla A2.

Your issue is right there:

Aug 30 14:54:21 JunkyardGarage kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 238

Aug 30 14:54:21 JunkyardGarage kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Aug 30 14:54:21 JunkyardGarage kernel: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:01:00.0)

Aug 30 14:54:21 JunkyardGarage kernel: nvidia 0000:01:00.0: probe with driver nvidia failed with error -1

Aug 30 14:54:21 JunkyardGarage kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).

Aug 30 14:54:21 JunkyardGarage kernel: NVRM: None of the NVIDIA devices were initialized.

Aug 30 14:54:21 JunkyardGarage kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 238

This usually means that you don't have Resizable BAR Support and/or Above 4G Decoding enabled in your BIOS.

I would however firstly recommend to update your BIOS.

9 hours ago, g0nd0l4 said:

open source

You should definitely be using the OpenSource Driver for your card.

9 hours ago, g0nd0l4 said:

Kernel modules: nouveau, nvidia_drm, nvidia

You see that Unraid loads the nouveau driver correct?

Please disable the nouveau driver by doing that from a terminal and reboot:

mkdir -p /boot/config/modprobe.d

echo "blacklist nouveau" > /boot/config/modprobe.d/nouveau.conf

9 hours ago, g0nd0l4 said:

So I tried running .run script from the official driver website, but gcc was not available and the NerdTools was abandoned and didn't work either.

That wouldn't do much because you would need to run the installer every time you boot Unraid or create a package that you install somehow on boot, I wouldn't recommend going down that route since this is really complicated and the plugin is there for.

What is that script in your go file:

# Custom: NVIDIA Datacenter Driver Install

sh /boot/config/custom/scripts/install_nvidia.sh

Anyone how to solve this? I'm on 7.1.4 and using Open Source Driver: v575.57.08 with nvidia 5070ti. When I stopped using VM with GPU passthrough, sometimes nvidia driver cannot detect the 5070ti anymore? I need to restart the server again for it to appear?

Here's the log

Aug 31 07:49:48 Wajinserver kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Aug 31 07:49:48 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

Aug 31 07:49:48 Wajinserver kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Aug 31 07:49:48 Wajinserver kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Aug 31 07:49:48 Wajinserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Aug 31 07:49:48 Wajinserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 31 07:49:49 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Aug 31 07:49:49 Wajinserver kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Aug 31 07:49:49 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

Aug 31 07:49:49 Wajinserver kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Aug 31 07:49:49 Wajinserver kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Aug 31 07:49:49 Wajinserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Aug 31 07:49:49 Wajinserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 31 07:49:50 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Aug 31 07:49:50 Wajinserver kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Aug 31 07:49:50 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

Aug 31 07:49:50 Wajinserver kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Aug 31 07:49:50 Wajinserver kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Aug 31 07:49:50 Wajinserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Aug 31 07:49:50 Wajinserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 31 07:49:55 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Aug 31 07:49:55 Wajinserver kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Aug 31 07:49:55 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

Aug 31 07:49:55 Wajinserver kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Aug 31 07:49:55 Wajinserver kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Aug 31 07:49:55 Wajinserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Aug 31 07:49:55 Wajinserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 31 07:49:57 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Aug 31 07:49:57 Wajinserver kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Aug 31 07:49:57 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

Aug 31 07:49:57 Wajinserver kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Aug 31 07:49:57 Wajinserver kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Aug 31 07:49:57 Wajinserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Aug 31 07:49:57 Wajinserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 31 07:49:58 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Aug 31 07:49:58 Wajinserver kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Aug 31 07:49:58 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

Aug 31 07:49:58 Wajinserver kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Aug 31 07:49:58 Wajinserver kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Aug 31 07:49:58 Wajinserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Aug 31 07:49:58 Wajinserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 31 07:50:01 Wajinserver kernel: docker0: port 1(vethf2b0a1f) entered blocking state

Aug 31 07:50:01 Wajinserver kernel: docker0: port 1(vethf2b0a1f) entered disabled state

Aug 31 07:50:01 Wajinserver kernel: vethf2b0a1f: entered allmulticast mode

Aug 31 07:50:01 Wajinserver kernel: vethf2b0a1f: entered promiscuous mode

Aug 31 07:50:01 Wajinserver kernel: eth0: renamed from veth2cc0116

Aug 31 07:50:01 Wajinserver kernel: docker0: port 1(vethf2b0a1f) entered blocking state

Aug 31 07:50:01 Wajinserver kernel: docker0: port 1(vethf2b0a1f) entered forwarding state

Aug 31 07:50:03 Wajinserver dnsmasq[24934]: reading /etc/resolv.conf

Aug 31 07:50:03 Wajinserver dnsmasq[24934]: using nameserver 100.100.100.100#53

Aug 31 07:50:07 Wajinserver kernel: Did not receive response to NOPIN on CID: 1, failing connection for I_T Nexus iqn.1991-05.com.microsoft:gaming-pc-win11,i,0x400001370001,iqn.2003-01.org.linux-iscsi.wajinserver.x8664:sn.764426ad0a24,t,0x01

Aug 31 07:50:17 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Aug 31 07:50:17 Wajinserver kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Aug 31 07:50:17 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

Aug 31 07:50:17 Wajinserver kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Aug 31 07:50:17 Wajinserver kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Aug 31 07:50:17 Wajinserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Aug 31 07:50:17 Wajinserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 31 07:50:18 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1353

Aug 31 07:50:18 Wajinserver kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615

Aug 31 07:50:18 Wajinserver kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502

Aug 31 07:50:18 Wajinserver kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image

Aug 31 07:50:18 Wajinserver kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Aug 31 07:50:18 Wajinserver kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)

Aug 31 07:50:18 Wajinserver kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 31 07:55:24 Wajinserver kernel: NVRM: nvAssertFailedNoLog: Assertion failed: !rmapiLockIsOwner() @ rmapi.c:563

Aug 31 07:55:24 Wajinserver kernel: NVRM: nvAssertFailedNoLog: Assertion failed: !rmapiLockIsOwner() @ rmapi.c:563

Aug 31 07:55:24 Wajinserver kernel: NVRM: nvAssertFailedNoLog: Assertion failed: !rmapiLockIsOwner() @ rmapi.c:563

Aug 31 07:55:24 Wajinserver kernel: NVRM: nvAssertFailedNoLog: Assertion failed: !rmapiLockIsOwner() @ rmapi.c:563

Edited August 31, 2025Aug 31 by sausuke

6 hours ago, sausuke said:

Here's the log

as mentioned many times, rather provide full diagnostics instead, better chances to get help.

overall, its not really recommended and sys related if the hardware has issues with usage like this.

recommended is always, either use this plugin and keep VM passthrough out of the game, OR vfio bind the card and use it exclusive in a VM.

i personally use it also as "wanted", either VM or Host (Docker) usage and never experienced any issues, but it can happen ... as mentioned, depending on some points if that will work or now and you have to be carefully to setup all nice so you never run into conflicts with dual access (host and vm)

Sorry for the late response. Since the hardware is separated from my home, it took some time to follow your instruction and solve the problem.

18 hours ago, ich777 said:

This usually means that you don't have Resizable BAR Support and/or Above 4G Decoding enabled in your BIOS.

This was the problem. I updated and checked the BIOS, and the Above 4G Decoding and Resizable BAR functions were disabled. As soon as I enabled it, the problem was gone. Tesla A2 was detected well and showed the GPU ID.

Setting the driver version as open source is done, but blacklisting nouveau will be done after I install the fan adapter.

18 hours ago, ich777 said:

What is that script in your go file:

And this was my ignorant trial of trying to make a script about installing the driver every time I boot the system. I immediately removed it as soon as I saw your comment.

Now it's time to make a fan adapter.

And most of all, thanks for your dedication to the communities.

Huge respect.

On 8/28/2025 at 2:02 AM, ich777 said:

No worries, then you'll have to wait for the next release from Unriad but I already have two confirmations that on the new beta everything is working as expected.

Unfortunately, updating to the beta did not result the issue. I used it last night at approximately 24 hours ago. Sometime between then and now (when I was planning to use it again), it cut out and the GPU is missing again.

tower-diagnostics-20250901-0144.zip

20 minutes ago, mrguymiah said:

it cut out and the GPU is missing again.

Did you yet try to to lower the PCIe Gen to something like Gen3.

Since you have a second gen Ryzen CPU please also disable C-States for your CPU entirely and see if that helps.

However from looking through your syslog I see probably a few errors:

NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy

This is an error that I never saw before to be completely honest.

And then you get this error which I've seen a lot recently but in your case it's a bit different and it seems it's related to the CPU but I really can't tell, however what you can do is that you report that on the Nvidia Developer Linux Forums subforums:

Aug 31 05:19:39 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363

Aug 31 05:19:40 Tower kernel: NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy

Aug 31 05:19:40 Tower kernel: eth0: renamed from veth6aa9d85

Aug 31 05:19:40 Tower kernel: br-6deb7f169b14: port 20(veth7d89dc4) entered blocking state

Aug 31 05:19:40 Tower kernel: br-6deb7f169b14: port 20(veth7d89dc4) entered forwarding state

Aug 31 05:19:41 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363

Aug 31 05:19:42 Tower kernel: NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy

Aug 31 05:19:42 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363

Aug 31 05:19:42 Tower kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242

Aug 31 05:19:42 Tower kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed

Aug 31 05:19:42 Tower kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed

Aug 31 05:19:42 Tower kernel: NVRM: osInitNvMapping: *** Cannot attach gpu

Aug 31 05:19:42 Tower kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter

Aug 31 05:19:42 Tower kernel: NVRM: GPU 0000:09:00.0: RmInitAdapter failed! (0x22:0x51:763)

Aug 31 05:19:42 Tower kernel: NVRM: GPU 0000:09:00.0: rm_init_adapter failed, device minor number 0

Aug 31 05:19:48 Tower kernel: NVRM: nvAssertFailedNoLog: Assertion failed: rmapiLockIsOwner() && rmGpuLockIsOwner() @ conf_compute_api.c:78

This is unrelated to the Nvidia Driver but you have lots of XFC Checksum errors:

Aug 29 06:12:57 Tower kernel: XFS (md1p1): Metadata CRC error detected at xfs_dir3_data_read_verify+0x7e/0x100, xfs_dir3_data block 0xbdd8fbe8

Aug 29 06:12:57 Tower kernel: XFS (md1p1): Unmount and run xfs_repair

Aug 29 06:12:57 Tower kernel: XFS (md1p1): First 128 bytes of corrupted metadata buffer:

Aug 29 06:12:57 Tower kernel: 00000000: 58 44 44 33 fa 13 dc ae 00 00 00 00 bd d8 fb e8 XDD3............

Aug 29 06:12:57 Tower kernel: 00000010: 00 00 00 01 00 04 b3 99 d7 b2 3a 12 2b 94 46 cb ..........:.+.F.

Aug 29 06:12:57 Tower kernel: 00000020: a0 27 c6 a5 40 66 31 b1 00 00 00 00 cf 30 95 6e .'[email protected]

Aug 29 06:12:57 Tower kernel: 00000030: 07 80 08 80 00 00 00 00 00 00 00 00 ff 7f 00 00 ................

Aug 29 06:12:57 Tower kernel: 00000040: 00 00 00 00 cf 30 96 15 16 53 6c 75 6d 20 4c 6f .....0...Slum Lo

Aug 29 06:12:57 Tower kernel: 00000050: 72 64 20 28 48 75 6d 61 6e 29 2e 63 68 75 6d 01 rd (Human).chum.

Aug 29 06:12:57 Tower kernel: 00000060: 00 00 00 00 00 00 00 40 00 00 00 00 cf 30 96 16 [email protected]..

Aug 29 06:12:57 Tower kernel: 00000070: 14 53 6c 75 6d 20 4c 6f 72 64 20 28 4f 72 6b 29 .Slum Lord (Ork)

I would recommend that you report that alongside with your Diagnostics in the General Support subforums here on the Forum.

39 minutes ago, ich777 said:

Did you yet try to to lower the PCIe Gen to something like Gen3.

Since you have a second gen Ryzen CPU please also disable C-States for your CPU entirely and see if that helps.

However from looking through your syslog I see probably a few errors:

NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy

This is an error that I never saw before to be completely honest.

And then you get this error which I've seen a lot recently but in your case it's a bit different and it seems it's related to the CPU but I really can't tell, however what you can do is that you report that on the Nvidia Developer Linux Forums subforums:

Aug 31 05:19:39 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363

Aug 31 05:19:40 Tower kernel: NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy

Aug 31 05:19:40 Tower kernel: eth0: renamed from veth6aa9d85

Aug 31 05:19:40 Tower kernel: br-6deb7f169b14: port 20(veth7d89dc4) entered blocking state

Aug 31 05:19:40 Tower kernel: br-6deb7f169b14: port 20(veth7d89dc4) entered forwarding state

Aug 31 05:19:41 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363

Aug 31 05:19:42 Tower kernel: NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy

Aug 31 05:19:42 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363

Aug 31 05:19:42 Tower kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242

Aug 31 05:19:42 Tower kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed

Aug 31 05:19:42 Tower kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed

Aug 31 05:19:42 Tower kernel: NVRM: osInitNvMapping: *** Cannot attach gpu

Aug 31 05:19:42 Tower kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter

Aug 31 05:19:42 Tower kernel: NVRM: GPU 0000:09:00.0: RmInitAdapter failed! (0x22:0x51:763)

Aug 31 05:19:42 Tower kernel: NVRM: GPU 0000:09:00.0: rm_init_adapter failed, device minor number 0

Aug 31 05:19:48 Tower kernel: NVRM: nvAssertFailedNoLog: Assertion failed: rmapiLockIsOwner() && rmGpuLockIsOwner() @ conf_compute_api.c:78

This is unrelated to the Nvidia Driver but you have lots of XFC Checksum errors:

Aug 29 06:12:57 Tower kernel: XFS (md1p1): Metadata CRC error detected at xfs_dir3_data_read_verify+0x7e/0x100, xfs_dir3_data block 0xbdd8fbe8

Aug 29 06:12:57 Tower kernel: XFS (md1p1): Unmount and run xfs_repair

Aug 29 06:12:57 Tower kernel: XFS (md1p1): First 128 bytes of corrupted metadata buffer:

Aug 29 06:12:57 Tower kernel: 00000000: 58 44 44 33 fa 13 dc ae 00 00 00 00 bd d8 fb e8 XDD3............

Aug 29 06:12:57 Tower kernel: 00000010: 00 00 00 01 00 04 b3 99 d7 b2 3a 12 2b 94 46 cb ..........:.+.F.

Aug 29 06:12:57 Tower kernel: 00000020: a0 27 c6 a5 40 66 31 b1 00 00 00 00 cf 30 95 6e .'[email protected]

Aug 29 06:12:57 Tower kernel: 00000030: 07 80 08 80 00 00 00 00 00 00 00 00 ff 7f 00 00 ................

Aug 29 06:12:57 Tower kernel: 00000040: 00 00 00 00 cf 30 96 15 16 53 6c 75 6d 20 4c 6f .....0...Slum Lo

Aug 29 06:12:57 Tower kernel: 00000050: 72 64 20 28 48 75 6d 61 6e 29 2e 63 68 75 6d 01 rd (Human).chum.

Aug 29 06:12:57 Tower kernel: 00000060: 00 00 00 00 00 00 00 40 00 00 00 00 cf 30 96 16 [email protected]..

Aug 29 06:12:57 Tower kernel: 00000070: 14 53 6c 75 6d 20 4c 6f 72 64 20 28 4f 72 6b 29 .Slum Lord (Ork)

I would recommend that you report that alongside with your Diagnostics in the General Support subforums here on the Forum.

I'll take it one step at a time then and start by disabling C-States and see how that improves things. I'm not sure what you mean by lower the PCIe Gen to Gen3. I'll double check, but I think that's the max speed of the Mobo's slots. Yeah, the x16 slots appear to be 3.0 slots. Is there a setting in Unraid I'm unfamiliar with?

14 hours ago, mrguymiah said:

I'm not sure what you mean by lower the PCIe Gen to Gen3. I'll double check, but I think that's the max speed of the Mobo's slots. Yeah, the x16 slots appear to be 3.0 slots. Is there a setting in Unraid I'm unfamiliar with?

That's a setting in your BIOS usually but only available when you have a Motherboard that supports newer PCIe Generations than 3.0

I have a gtx 650 that can't be detected by the plugin. How would I go about installing the legacy drivers? I have the correct one downloaded, but have never attempted this before. I'm struggling to find any info on it at the moment.

1 hour ago, mrkrabs said:

I have a gtx 650 that can't be detected by the plugin. How would I go about installing the legacy drivers? I have the correct one downloaded, but have never attempted this before. I'm struggling to find any info on it at the moment.

afaik the gtx650 is outdated and not supported anymore.

also, there is nothing really you can do with this card anyhow ? no nvenc, no ...

2 hours ago, mrkrabs said:

How would I go about installing the legacy drivers?

In addition to @alturismo‘s post:

26 minutes ago, alturismo said:

afaik the gtx650 is outdated and not supported anymore.

also, there is nothing really you can do with this card anyhow ? no nvenc, no ...

tragic, was hoping to get some kind of use out of it after finding it in an old parts bin. Guess it goes on a shelf as a museum piece. Thanks for the response!

3 minutes ago, ich777 said:

In addition to @alturismo‘s post:

All good, thank you!

@ich777 - Thanks for your awesome work on this plugin. Quick question - I am using P2000 for Plex and Immich dockers. What branch should I remain on - it is very confusing and after reading a few comments above I am more confused by legacy and proprietary drivers.

Cheers!

3 hours ago, Unraid-arr said:

@ich777 - Thanks for your awesome work on this plugin. Quick question - I am using P2000 for Plex and Immich dockers. What branch should I remain on - it is very confusing and after reading a few comments above I am more confused by legacy and proprietary drivers.

For now on the latest, we will see what the future or better speaking Nvidia is bringing to the table.