8 minutes ago, AT123454321 said:

Where are you lacated in the world?

Do you have Diagnostics?

Romania, I just rebooted. Fingers crossed. The driver is for a Tesla P40 used for Jellyfin decoding.

22 minutes ago, AT123454321 said:

Romania, I just rebooted. Fingers crossed. The driver is for a Tesla P40 used for Jellyfin decoding.

Keep in mind that your server will try to download the driver now on boot and if it's like for me over here in Europe the downloads from GitHub are really slow currently about 1MB/s this can take some time since the driver package is about 250MB.

 

If it is not working, just do that:

1. Uninstall the Nvidia Driver plugin (please also check if it's in the Plugin Error tab within the Plugin section in Unraid and remove it)
2. Reboot
3. Install the Nvidia Driver plugin
4. Reboot

 

After that it should work.

Drives are not loading afther upgrade from 6.12.14 to 7.0.0

 

 

Iahve unstalled and installed the drivers. Rebooting between avery stage. 

 

nest2-diagnostics-20250112-0515.zip

11 minutes ago, mikeofoslo said:

Drives are not loading afther upgrade from 6.12.14 to 7.0.0

 

 

Iahve unstalled and installed the drivers. Rebooting between avery stage. 

 

nest2-diagnostics-20250112-0515.zip 155.85 kB · 0 downloads

The Nvidia drivers seem to install fine. 

On the otherhand, it appears, you dont even have a Nvidia GPU in your system. Its not detected at all

Edited January 12, 20251 yr by Mainfrezzer
rephasing and typo

1 hour ago, mikeofoslo said:

Iahve unstalled and installed the drivers. Rebooting between avery stage. 

As @Mainfrezzer said:

Jan 12 05:04:57 NEST2 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 241
Jan 12 05:04:57 NEST2 kernel: NVRM: No NVIDIA GPU found.

 

5 hours ago, Mainfrezzer said:

The Nvidia drivers seem to install fine. 

On the otherhand, it appears, you dont even have a Nvidia GPU in your system. Its not detected at all

The Nvidia GPU is still inside the server. It was working fine under 6.12.14. 

4 hours ago, ich777 said:

As @Mainfrezzer said:

Jan 12 05:04:57 NEST2 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 241
Jan 12 05:04:57 NEST2 kernel: NVRM: No NVIDIA GPU found.

 

The Nvidia GPU is still inside the server. It was working fine under 6.12.14.  This is my backupserver and was the first to go for an upgrade. The main server is practically identical when hardware is concerned. 

 

I think I'll have to ty to roll back for now. 

54 minutes ago, mikeofoslo said:

The Nvidia GPU is still inside the server. It was working fine under 6.12.14. 

51 minutes ago, mikeofoslo said:

I think I'll have to ty to roll back for now. 

Please think again about it...

 

The card is not even recognized by your system, this has nothing to do with the Upgrade or Unraid itself.

The card should at least show up in lspci which it doesn't do...

Maybe try to shutdown your server entirely, pull the cord from the wall, wait for a few minutes and turn it back on after that, maybe the card just hangs or something like that.

5 hours ago, ich777 said:

Please think again about it...

 

The card is not even recognized by your system, this has nothing to do with the Upgrade or Unraid itself.

The card should at least show up in lspci which it doesn't do...

Maybe try to shutdown your server entirely, pull the cord from the wall, wait for a few minutes and turn it back on after that, maybe the card just hangs or something like that.

Managed to get it working, I removed and reseated the GPU. It works now! 
Thnak you all for the help :-) 

Edited January 13, 20251 yr by mikeofoslo

I hear you. But I only have the card in this machine because the CPU (AMD 1700) doesn't have an APU for my IPKVM. I was just trying to give it as a help to the CPU. But from the provided link, doesn't look like it will be doing much. Lol. Thank you for replying all the same!

On 1/11/2025 at 12:02 AM, ich777 said:

This graphics card is not capable of encoding/decoding most of the common formats nowadays because it is pretty old by todays standards.

 

You can take a look here what the card is actually capable of:

https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

 

I would recommend that you look into something new or even used because you can get something like a Nvidia T400 for pretty cheap nowadays.

I

Hi Everyone,

I'm new to Unraid, so please excuse me for my lack of general Docker knownledge! I am trying to get my GPU working for some functionnality in Immich and eventually in Jellyfin. However, after a lot for tickering, I think the drivers does not get install properly because I dont see the option in Setting>Docker (Advanced View) for NVDIA Driver = Enable. Also, NVDA-SMI doesnt work in console mode. BUT, my GPU is showing Tab for NVDIA Driver Package. Can also confirm that GPU Stats does show me GPU information.

 

I have installed Unraid 7.0.0 from 2025-01-09. 

I have an NVDIA GTX 1070 TI installed

 

Last things I tried is Uninstalling the NVDIA Driver, reboot, Reinstall, Reboot, Docker Enable = No, Docker Enable = Yes , but the NVDIA Driver = Enable option isn't showing..  

 

I made sure the card is sitting properly in its slot, that 4g decoding and rebar are enable in the Bios. 

 

I am attaching Diag file hoping someone can point me to the right direction. 

 

Thank you!

 

 

 

nas-amd2700-diagnostics-20250117-0823.zip

36 minutes ago, Desret said:

I am attaching Diag file hoping someone can point me to the right direction. 

Did you read the second post in this thread what you have to add to a container to utilize the Nvidia card in the container?

Did you also follow the first post and the steps how to install the driver.

 

The command from the terminal is:

nvidia-smi

 

You have a typo in your screenshot.

First of all, I am total noob with this stupid typo .. ! I'm very sorry! I didnt want to waste your time! NVIDIA-SMI works. Looks like I had the same typo in the --runtime-NVIDIA which was killing my Immich docker. Well, all good now and working. Thanks so much!! 

Edited January 17, 20251 yr by Desret
Typo correction

I am having some trouble with getting my gpu working on 7.0 with my setup. I had it working with a debian setup so maybe there is something I am missing with my configuration.

Currently running a Minisforum MS-01 with a 1080ti in a Razer Core X eGPU enclosure. In the bios I have enabled 4G Decoding.

I have also included my diagnostics and I think the issue is with it falling off the bus, any help is greatly appreciated!

diagnostics-20250119-1645.zip

5 hours ago, tyler_staut said:

Currently running a Minisforum MS-01 with a 1080ti in a Razer Core X eGPU enclosure. In the bios I have enabled 4G Decoding.

Please also make sure that you enable Resizable BAR Support, just to be safe.

 

I also see that your Server has issues changing the power state here:

Jan 19 16:24:35 MiniLab kernel: nvidia 0000:30:00.0: Unable to change power state from D3cold to D0, device inaccessible

 

Is this maybe a Thunderbolt dock? Because you also have this in your logs:

Jan 19 16:24:35 MiniLab kernel: WARNING: CPU: 6 PID: 707 at drivers/thunderbolt/ctl.c:217 check_config_address+0x82/0x96 [thunderbolt]

 

 

I'm not 100% sure if this is solvable because Thunderbolt support is hit and miss on Unraid AFAIK and I also can't help any further because I don't have any Thunderbolt hardware at all.

Having issues getting my 1070 recognized by this plugin.  Card works as I previously had it passed through to a Win10 VM.  Made sure to ungroup in IOMMU and took the variables out of my Syslinux config.  Updated BIOS to the latest, changed my PCIe speeds to Gen3 just in case, tried 3 different PCie slots and still nothing.  GPU statistics sees the card identifier, but doesn't display anything.  Nvidia-smi says no card found.  Not sure how else to troubleshoot this.  Card is recognized in the system, just can't get this driver to detect it. Any help would be greatly appreciated!

 

 

tower-diagnostics-20250120-0752.zip

Edited January 20, 20251 yr by chesh
added syslinux config

38 minutes ago, chesh said:

Any help would be greatly appreciated!

hard to tell ...

 

its actually there as you shown it, error from syslog

 

Jan 17 17:46:48 Tower nvidia-persistenced: Started (26184)
Jan 17 17:46:48 Tower kernel: NVRM: GPU 0000:04:00.0: RmInitAdapter failed! (0x24:0x72:1516)
Jan 17 17:46:48 Tower kernel: NVRM: GPU 0000:04:00.0: rm_init_adapter failed, device minor number 0
Jan 17 17:46:49 Tower kernel: NVRM: GPU 0000:04:00.0: RmInitAdapter failed! (0x24:0x72:1516)
Jan 17 17:46:49 Tower kernel: NVRM: GPU 0000:04:00.0: rm_init_adapter failed, device minor number 0
Jan 17 17:46:49 Tower nvidia-persistenced: device 0000:04:00.0 - failed to open.
Jan 17 17:46:59 Tower kernel: NVRM: GPU 0000:04:00.0: RmInitAdapter failed! (0x24:0x72:1516)
Jan 17 17:46:59 Tower kernel: NVRM: GPU 0000:04:00.0: rm_init_adapter failed, device minor number 0

 

1/ sure enough Power ?

2/ may a bad firmware ... ? which may works in win ... cant really imagine but who knows ...

Running an EVGA Gold 850W, so it should be enough for my setup.  Any further troubleshooting you'd suggest to see what might be going wrong?  I've got a 970 that I can test with next to see if it can see that one.

 

3 minutes ago, chesh said:

Running an EVGA Gold 850W, so it should be enough for my setup.

more then enough ... if its well wired  sorry, here where many which "forgot" to properly check cables.

 

4 minutes ago, chesh said:

I can test with next to see if it can see that one.

your card is already seen, but not in a working state ... and of course, may try the 970 just to make sure

I do have another VGA power connector that I can test just to see.  I'll try the 970 as well.

 

11 hours ago, ich777 said:

Please also make sure that you enable Resizable BAR Support, just to be safe.

 

I also see that your Server has issues changing the power state here:

Jan 19 16:24:35 MiniLab kernel: nvidia 0000:30:00.0: Unable to change power state from D3cold to D0, device inaccessible

 

Is this maybe a Thunderbolt dock? Because you also have this in your logs:

Jan 19 16:24:35 MiniLab kernel: WARNING: CPU: 6 PID: 707 at drivers/thunderbolt/ctl.c:217 check_config_address+0x82/0x96 [thunderbolt]

 

 

I'm not 100% sure if this is solvable because Thunderbolt support is hit and miss on Unraid AFAIK and I also can't help any further because I don't have any Thunderbolt hardware at all.

Yeah I enabled resizable BAR as well as disabled DMA Control Guarantee in the bios but no change.

I noticed the power state not changing as well but I am using a Thunderbolt dock so that's probably where the issue is. I might dig a bit deeper into this as I was able to get it working with Debian. Thanks for taking a look!

11 hours ago, tyler_staut said:

I was able to get it working with Debian

The root cause is most likely the Thunderbolt case because Thunderbolt is known to not work on Unraid.

My assumption is because there can't be a proper handshake between Unraid and the Dock that no proper communication can be initiated and that's why the power state can't be changed and therefore you see this message in your syslog.

12 hours ago, chesh said:

I do have another VGA power connector that I can test just to see.  I'll try the 970 as well.

 

I would recommend that you clean up any leftovers or not working parts in your OS first because you have also this message 711 times in your syslog:

Jan 20 07:54:11 Tower crond[2164]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

that's probably cause because you do this in your go file:

cp /boot/monitor /usr/local/emhttp/webGui/scripts/monitor

 

Then I would recommend to upgrade to Unraid 7.0.0

 

May I also ask why you are booting into GUI mode? GUI mode on Unraid is most of the times only considered as troubleshooting mode.

10 hours ago, ich777 said:

I would recommend that you clean up any leftovers or not working parts in your OS first because you have also this message 711 times in your syslog:

Jan 20 07:54:11 Tower crond[2164]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

that's probably cause because you do this in your go file:

cp /boot/monitor /usr/local/emhttp/webGui/scripts/monitor

 

Then I would recommend to upgrade to Unraid 7.0.0

 

May I also ask why you are booting into GUI mode? GUI mode on Unraid is most of the times only considered as troubleshooting mode.

Removed that line from my go file.  I boot into GUI mode as the server is in the basement and usually the only time I turn on the monitor is so I can troubleshoot.  Just makes it easier than lugging a laptop around with me.

 

As for 7.0, probably holding off till 7.0.1 as I usually don't jump on the bandwagon when new versions come out.  Like for some of the bugs to be worked out first.  

 

I did try a different VGA header port on my PSU and a different cable this morning w/ the 1070, but still got the same result.  I then installed a 970 and that was detected right away.  1070 might just be fried.  cat /proc/drivers/nvidia/gpus/xxx/information did just give me nothing but ???? for the VBIOS and GPU UUID as well.  Whereas all the 970's info is populated.  Unfortunately, the 970 is a pretty weak card compared to current gen, so time to start thinking about buying a new card.  Thanks for all the replies though!