28 minutes ago, tombstone said:

OK thanks for looking into this for me

If possible, please also pull diagnostics when the error occurs.

From the Diagnostics I don't see anything wrong. You can try to add nvidia-persistenced to your go file, make sure that you are on the latest BIOS version, make sure that Above 4G Decoding and Resizable BAR Support is enabled.

4 minutes ago, ich777 said:

If possible, please also pull diagnostics when the error occurs.

From the Diagnostics I don't see anything wrong. You can try to add nvidia-persistenced to your go file, make sure that you are on the latest BIOS version, make sure that Above 4G Decoding and Resizable BAR Support is enabled.

Sorry — I’m not sure how to update the server to the latest BIOS version, or how to check whether Above 4G Decoding and Resizable BAR support are enabled.

I also don’t know what nvidia-persistenced is, or where the go file is located but I think you may mean its in my BIOS setting so going to have a look now..

When I searched on Google, this video showed up, and I’m watching it now.

I managed to make the error appear again. Also, when I play videos, they’re using my CPU instead of my GPU…

https://youtu.be/xLaE5z8HkjY?si=Ay37VneTcLlaZ2_A

happy2me-diagnostics-20251212-1802.zip

4 minutes ago, tombstone said:

Sorry — I’m not sure how to update the server to the latest BIOS version, or how to check whether Above 4G Decoding and Resizable BAR support are enabled.

You have to go into the BIOS for that and check the settings.

For the BIOS update you have to check your Motherboards/Systems manufacturers website.

Just put the line:

nvidia-persistenced

at the end of the file /boot/config/go and reboot afterwards.

The video is a good source of information.

6 minutes ago, tombstone said:

I managed to make the error appear again. Also, when I play videos, they’re using my CPU instead of my GPU…

Seems to be a PCI related issue, I would strongly recommend that you do the above steps.

3 minutes ago, ich777 said:

You have to go into the BIOS for that and check the settings.

For the BIOS update you have to check your Motherboards/Systems manufacturers website.

Just put the line:

nvidia-persistenced

at the end of the file /boot/config/go and reboot afterwards.

The video is a good source of information.

Seems to be a PCI related issue, I would strongly recommend that you do the above steps.

ok here is my setting for PCI-E in the bios.

what I can see my bios is BIOS_Acer_P08

e

and from this page its the only one.

https://www.acer.com/au-en/support/product-support/Altos_T310_F3

29 minutes ago, ich777 said:

Just put the line:

nvidia-persistenced

at the end of the file /boot/config/go and reboot afterwards.

I am thinking this is what you mean?

17 minutes ago, tombstone said:

what I can see my bios is BIOS_Acer_P08

Okay, seems pretty old but you might be out of luck with the BIOS updates, seems this machine is deprecated from the manufacturer.

19 minutes ago, tombstone said:

and from this page its the only one.

Seems your machine doesn't support either of these options.

4 minutes ago, tombstone said:

I am thinking this is what you mean?

Not exactly but it is enough if you issue it once after a reboot.

May I ask if this is a new issue or a new installation or even a new GPU or a new installation from Unraid?
Most of the times it's a hardware incompatibility issue or a wrong set setting in the BIOS, but I don't think it's the latter in your case.

5 minutes ago, tombstone said:

I am thinking this is what you mean?

sorry now looking at it is this were you mean for me to do

I use ther nano go right

Just now, tombstone said:

sorry now looking at it is this were you mean for me to do

Unraid should have a file explorer where you can edit files directly in the WebUI.

1 minute ago, ich777 said:

May I ask if this is a new issue or a new installation or even a new GPU or a new installation from Unraid?
Most of the times it's a hardware incompatibility issue or a wrong set setting in the BIOS, but I don't think it's the latter in your case.

I used Unraid back in the day, then I started going down the TrueNAS path. But I saw the light and came back. I’ve been building my new Unraid stack over the last four or five days.

Just now, tombstone said:

I’ve been building my new Unraid stack over the last four or five days.

Pairing old hardware (you System) with relatively new Hardware GTX16 series or RTX series is most of the times a bad idea and will lead to potential issues like you are experiencing.

4 minutes ago, ich777 said:

Unraid should have a file explorer where you can edit files directly in the WebUI.

file mangager but no way to get into the USB (boot drive) that I can see.

3 minutes ago, ich777 said:

Pairing old hardware (you System) with relatively new Hardware GTX16 series or RTX series is most of the times a bad idea and will lead to potential issues like you are experiencing.

I also got the google coral edgetpu to get working also, think it was working on the truenas.

at this time I have to wait till next year to buy and new upgrades (new motherboard)

Just now, tombstone said:

I also got the google coral edgetpu to get working also, think it was working on the truenas.

Yeah, that should work.

Just now, tombstone said:

at this time I have to wait till next year to buy and new upgrades (new motherboard)

Sorry, but most of the times it has to do with hardware incompatibility, the GTX16 series was always a bit of hit and miss, maybe look out for something like a Nvidia T400 4GB (even the 2GB version should work fine) and try if this card works.

7 minutes ago, ich777 said:

Yeah, that should work.

Sorry, but most of the times it has to do with hardware incompatibility, the GTX16 series was always a bit of hit and miss, maybe look out for something like a Nvidia T400 4GB (even the 2GB version should work fine) and try if this card works.

ok thanks I will look into doing something in the new year if everything with money works out for me.

23 minutes ago, ich777 said:

Not exactly but it is enough if you issue it once after a reboot.

the nvidia-persistenced seems like th cpu is alot more carma now but seems lik the GPU is still not doing anything.

have done another diagnostic when playing an movie on jellyfin, what do you think? is it fix or its the best its going to get?
happy2me-diagnostics-20251212-1921.ziph

49 minutes ago, ich777 said:

Also is this what I do to make it work after reboot.

2 hours ago, tombstone said:

Also is this what I do to make it work after reboot.

I don't know if that will definitely help but a few users reported that this helped, however that looks okay.

2 hours ago, tombstone said:

the nvidia-persistenced seems like th cpu is alot more carma now but seems lik the GPU is still not doing anything.

Sorry, you have to ask that on the container side of things however it looks like you don't do transcoding if you are currently playing a file.

Please also note, if audio transcoding is needed, this is done on the CPU not on the GPU.

Hello, i've searched many forums but didn't quite manage to find the problem i have. I built my first HomeLab recently and have the following main specs:
- AsRock B650D4U-2L2T/BCM
- AMD EPYC 4345P
- Nvidia RTX 5060

- Unraid 7.2.2

Ever since setting up my Server around a week ago i couldn't detect my GPU fully.

The device doesn't show up in Plex when i try to choose a device for transcoding.

lspci shows my GPU:
01:00.0 VGA compatible controller: NVIDIA Corporation GB206 [GeForce RTX 5060]

01:00.1 Audio device: NVIDIA Corporation GB206 High Definition Audio Controller

But nvidia-smi doesn't find the device:
root@Tower:~# nvidia-smi

No devices were found

root@Tower:~#

GPU Statistics shows the GPU:

But in the Dashboard, it only says "PCI Bus Utilization":


Nvidia Driver does have the Open Source version that is required for 50XX cards, but the device is not found:

I've also not bound anything in system devices, no checkmarks for:

IOMMU group 13:				[10de:2d05] 01:00.0 VGA compatible controller: NVIDIA Corporation GB206 [GeForce RTX 5060] (rev a1)
				[10de:22eb] 01:00.1 Audio device: NVIDIA Corporation GB206 High Definition Audio Controller (rev a1)

Another output from the terminal that clearly detects my gpu:
root@Tower:~# lspci -ks 0000:01:00.0

01:00.0 VGA compatible controller: NVIDIA Corporation GB206 [GeForce RTX 5060] (rev a1)

Subsystem: CardExpert Technology Device f331

Kernel driver in use: nvidia

Kernel modules: nouveau, nvidia_drm, nvidia

root@Tower:~#

The only logical reason for me is that the driver doesn't support my gpu, but in the post it clearly says i need the open source, meaning the v580.95.05 version which i have installed. I've run the latest version before, but it gave out the same results as now with the open source version..

Are there any other reasons my gpu gets detected in some ways but doesn't really work for Unraid?

6 hours ago, ElementG8 said:

i've searched many forums but didn't quite manage to find the problem i have.

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

Hi everyone,

Could someone briefly confirm whether I can run full CUDA acceleration with Ollama using an RTX 5060 Ti on Unraid 7.2.2 with the latest open source NVIDIA driver?

Thanks in advance!

2 hours ago, waterfallbay said:

I can run full CUDA acceleration

What is the opposite from full CUDA acceleration?

4 hours ago, ich777 said:

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

Here are my Diagnostics, hope that's correct:
Diagnotics Unraid

46 minutes ago, ElementG8 said:

hope that's correct

You can drag them just into the textbox within the forums.

First of all, your plugin is broken, you can see that on these lines:

Please remove the plugin, reboot, install the plugin again, select the open source driver, click Download & Update and reboot again.

From what I see from your syslog:

Dec 14 02:27:30 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1359

Dec 14 02:27:30 Tower kernel: NVRM: _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP

Dec 14 02:27:30 Tower kernel: NVRM: _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)

Dec 14 02:27:30 Tower kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Dec 14 02:27:30 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2015)

Dec 14 02:27:30 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 14 02:27:32 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1359

You are suffering from the same issues as others do, this is most of the times caused by hardware incompatbility or a wrong set setting in the BIOS.

I would recommend that you do the following:

1. Make sure your BIOS is up to date

2. Load default BIOS settings

3. Add nvidia-persistence at the end of your go file (/boot/config/go)

4. Make sure to enable Above 4G Decoding in the BIOS

5. Make sure to enable Resizabel BAR Support in the BIOS

6. If you have the setting in your BIOS, enable BME DMA Mitigation (see this post)

I did all that, including the nvidia-persistance in the go file, my Bios is up to date and i don't have a BME DMA Mitigation option
The red marked error on the plugin page is gone now, but the gpu still is not detected.

Can't drag it in here, don't know why, sorry:
https://www.swisstransfer.com/d/9ef0ffb6-34a9-4561-92e8-a5538eb2493e

Then i guess my GPU won't work with that MB, ffs... How do i find out or check what GPU works with my MB, there wasn't anything on the page...

From the Terminal - GSP Firmware Errors

root@Tower:~# cat /proc/cmdline BOOT_IMAGE=/bzimage initrd=/bzroot root@Tower:~# nvidia-smi No devices were found root@Tower:~# dmesg -T | egrep -i "gsp|NVRM|Xid" | tail -n 100 [Sun Dec 14 15:33:30 2025] NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 580.95.05 Release Build (dvs-builder@U22-I3-B17-02-5) Tue Sep 23 09:55:41 UTC 2025 [Sun Dec 14 15:34:55 2025] NVRM: kgspLogXid119: ********************************* GSP Timeout ********************************** [Sun Dec 14 15:34:55 2025] NVRM: kgspLogXid119: Note: Please also check logs above. [Sun Dec 14 15:34:55 2025] NVRM: nvAssertFailedNoLog: Assertion failed: expectedFunc == pHistoryEntry->function @ kernel_gsp.c:2119 [Sun Dec 14 15:34:55 2025] NVRM: GPU at PCI:0000:01:00: GPU-977a01c6-93b1-cd5f-8a7a-9e1d2bb797c3 [Sun Dec 14 15:34:55 2025] NVRM: Xid (PCI:0000:01:00): 119, Timeout after 6s of waiting for RPC response from GPU0 GSP! Expected function 4097 (GSP_INIT_DONE) sequence 0 (0x0 0x0). [Sun Dec 14 15:34:55 2025] NVRM: GPU0 GSP RPC buffer contains function 4124 (GSP_LOCKDOWN_NOTICE) sequence 0 and data 0x0000000000000000 0x0000000000000000. [Sun Dec 14 15:34:55 2025] NVRM: GPU0 RPC history (CPU -> GSP): [Sun Dec 14 15:34:55 2025] NVRM: entry function sequence data0 data1 ts_start ts_end duration actively_polling [Sun Dec 14 15:34:55 2025] NVRM: 0 73 SET_REGISTRY 0 0x0000000000000000 0x0000000000000000 0x000645ea65990143 0x0000000000000000 y [Sun Dec 14 15:34:55 2025] NVRM: -1 72 GSP_SET_SYSTEM_INFO 0 0x0000000000000000 0x0000000000000000 0x000645ea65990140 0x0000000000000000 [Sun Dec 14 15:34:55 2025] NVRM: GPU0 RPC event history (CPU <- GSP): [Sun Dec 14 15:34:55 2025] NVRM: entry function sequence data0 data1 ts_start ts_end duration during_incomplete_rpc [Sun Dec 14 15:34:55 2025] NVRM: 0 4124 GSP_LOCKDOWN_NOTICE 0 0x0000000000000000 0x0000000000000000 0x000645ea65e6a050 0x000645ea65e6a050 y [Sun Dec 14 15:34:55 2025] NVRM: -1 4124 GSP_LOCKDOWN_NOTICE 0 0x0000000000000001 0x0000000000000000 0x000645ea65e69edf 0x000645ea65e69edf y [Sun Dec 14 15:34:55 2025] NVRM: -2 4124 GSP_LOCKDOWN_NOTICE 0 0x0000000000000000 0x0000000000000000 0x000645ea65e568af 0x000645ea65e568af y [Sun Dec 14 15:34:55 2025] NVRM: -3 4124 GSP_LOCKDOWN_NOTICE 0 0x0000000000000001 0x0000000000000000 0x000645ea65e53d53 0x000645ea65e53d54 1us y [Sun Dec 14 15:34:55 2025] NVRM: -4 4108 UCODE_LIBOS_PRINT 0 0x0000000000000000 0x0000000000000000 0x000645ea65a47571 0x000645ea65a47571 y [Sun Dec 14 15:34:55 2025] NVRM: -5 4108 UCODE_LIBOS_PRINT 0 0x0000000000000000 0x0000000000000000 0x000645ea65a47567 0x000645ea65a47568 1us y [Sun Dec 14 15:34:55 2025] NVRM: -6 4124 GSP_LOCKDOWN_NOTICE 0 0x0000000000000000 0x0000000000000000 0x000645ea65a467fe 0x000645ea65a467fe y [Sun Dec 14 15:34:55 2025] NVRM: -7 4124 GSP_LOCKDOWN_NOTICE 0 0x0000000000000001 0x0000000000000000 0x000645ea65a43901 0x000645ea65a43902 1us y [Sun Dec 14 15:34:55 2025] kgspRpcRecvPoll+0x650/0x820 [nvidia] [Sun Dec 14 15:34:55 2025] ? kgspWaitForRmInitDoneIMPL+0x36/0xf8 [nvidia] [Sun Dec 14 15:34:55 2025] ? kgspBootstrap_GH100+0x385/0xaca [nvidia] [Sun Dec 14 15:34:55 2025] ? kgspInitRm_IMPL+0x96a/0x1680 [nvidia] [Sun Dec 14 15:34:55 2025] NVRM: kgspLogXid119: ******************************************************************************** [Sun Dec 14 15:34:55 2025] NVRM: nvCheckOkFailedNoLog: Check failed: Call timed out [NVERR_TIMEOUT] (0x00000065) returned from rpcRecvPoll(pGpu, pRpc, NV_VGPU_MSG_EVENT_GSP_INIT_DONE, 0) @ kernel_gsp.c:4992 [Sun Dec 14 15:34:55 2025] NVRM: nvAssertOkFailedNoLog: Assertion failed: Call timed out [NV_ERR_TIMEOUT] (0x00000065) returned from kgspWaitForRmInitDone(pGpu, pKernelGsp) @ kernel_gsp_gh100.c:980 [Sun Dec 14 15:34:55 2025] NVRM: kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP [Sun Dec 14 15:34:55 2025] NVRM: kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset) [Sun Dec 14 15:34:55 2025] NVRM: RmInitAdapter: Cannot initialize GSP firmware RM [Sun Dec 14 15:34:55 2025] NVRM: iovaspaceDestruct_IMPL: 1 left-over mappings in IOVAS 0x100 [Sun Dec 14 15:34:55 2025] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2015) [Sun Dec 14 15:34:55 2025] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 [Sun Dec 14 15:34:59 2025] NVRM: kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP [Sun Dec 14 15:34:59 2025] NVRM: kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset) [Sun Dec 14 15:34:59 2025] NVRM: RmInitAdapter: Cannot initialize GSP firmware RM [Sun Dec 14 15:34:59 2025] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2015) [Sun Dec 14 15:34:59 2025] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 [Sun Dec 14 15:35:15 2025] NVRM: kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP [Sun Dec 14 15:35:15 2025] NVRM: kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset) [Sun Dec 14 15:35:15 2025] NVRM: RmInitAdapter: Cannot initialize GSP firmware RM [Sun Dec 14 15:35:15 2025] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2015) [Sun Dec 14 15:35:15 2025] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 root@Tower:~#

6 hours ago, ElementG8 said:

Then i guess my GPU won't work with that MB, ffs... How do i find out or check what GPU works with my MB, there wasn't anything on the page...

You'll also see that in the syslog, no dmesg needed, you have a Xid 119 error, please see here.

I'm not sure, that could be also be a driver issue. Have you yet tried to reseat the card, please also check your Power Supply if it's up to the task, don't forget that power supplies also degrade over time.

Maybe also try to set the PCIe Generation to something like Gen 4 or Gen 3 and see if that helps.

I upgraded to Unraid 7.2.2 from 7.2.1 and all my dockers which use the NVIDIA driver (plex, jellyfin and Tdarr) have stopped working.

Checked the nVidia driver config page and it states:

"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'm at the latest version: v590.44.01

Not really sure how to fix this.

tower-diagnostics-20251216-0802.zip

Edited December 15, 2025Dec 15 by bobalot