5 minutes ago, msalad said:

It now does seem unrelated to Nerd Tools plugin since I found that I can install a different plugin to fix the issue too. I'm just not sure where to go from here. Having to install/uninstall a plugin after every reboot and then manually start the affected containers isn't ideal for long term

Do you have any custom user scripts, third party packages, custom scripts or entries in the go file which maybe cause this?

Do you have any plugins installed that are maybe not supported, maybe a plugin is causing this?

Do you modify the /tmp directory in a Docker container or do you overwrite anything in there?

 

Sorry these are just wild guesses since it seems rather strange to me because it‘s not working on your system where it should work right OOB since it works on my test system and probably all orher users that use the Nvidia Driver plugin.

If plex thumb generator script is running while it tries to update, it causes this crash;

 

And I can't stop the thumb gen container (although it contiues to run normally it seems.) I have to disable docker, reboot, then it works fine. but i've noticed it happens during every update.

16 minutes ago, sunwind said:

If plex thumb generator script is running while it tries to update

What is the Plex generator script and what do you mean with update?

 

16 minutes ago, sunwind said:

but i've noticed it happens during every update.

What container are you using, Repository?

 

Diagnostics would also maybe help from after a "crash".

So i have reinstalled the Nvidia plugin after an issue with the driver and the latest NVIDIA Drivers & Rebooted the machine and turned the docker service on and off.

None of my containers that have been previously setup (and working) are using the GPU for transcoding Immich, Unmaninc, Plex and so on.

The device is correctly detected and showing up in the Itop plugin and in the system devices are showing correctly (Now)

Ive been looking for hours and nothing i do seems to be working, has anyone else has this issue since the upgrade or has any ideas on a fix!

tower-diagnostics-20250304-0754.zip

8 minutes ago, Rkpaxam said:

None of my containers that have been previously setup (and working) are using the GPU for transcoding Immich, Unmaninc, Plex and so on.

Are the containers starting?

 

8 minutes ago, Rkpaxam said:

Ive been looking for hours and nothing i do seems to be working, has anyone else has this issue since the upgrade or has any ideas on a fix!

I just tried it on my test server and everything seems to work fine.

 

9 minutes ago, Rkpaxam said:

So i have reinstalled the Nvidia plugin after an issue with the driver and the latest NVIDIA Drivers & Rebooted the machine and turned the docker service on and off.

From your Diagnostics I see nothing obvious, did you change the hardware or anything similar?

How do you check if the transcoding/machine learning is not working?

2 minutes ago, ich777 said:

Are the containers starting?

Everthing as normal 

2 minutes ago, ich777 said:

I just tried it on my test server and everything seems to work fine.

 

From your Diagnostics I see nothing obvious, did you change the hardware or anything similar? Nothings changed other than moving to 7+

How do you check if the transcoding/machine learning is not working?

Shows me on the main page what apps are using the gpu

 

3 minutes ago, Rkpaxam said:

Everthing as normal 

Then the runtime seems at least to be running/working fine.

 

3 minutes ago, Rkpaxam said:

Shows me on the main page what apps are using the gpu

Does Plex/Unmanic transcode anything or do you get a error message?

Please try to open up a terminal from Unraid and after that issue that command:

watch nvidia-smi

Leave the terminal open and start a transcode in Plex/Unmanic.

 

ATTENTION: Please make sure if you are forcing a transcoding you are doing it from a native App like Plex for iOS or Android, the Windows and Web Plex Client are known to just display a black screen after forcing a transcode in combination with Nvidia.

Hi, i was wondering if there were any issues with new 50 series graphics cards and this plugin. I tried to install the plugin and the latest drivers, but my gpu is not showing up. I have a 5070 ti and I do see it in the system devices too. Also, when i try to run nvidia-smi, it also says no devices found.

2 hours ago, c625v12 said:

I tried to install the plugin and the latest drivers,

did you try with the open source drivers ? i think rtx50 only works with opensource drivers

6 hours ago, c625v12 said:

50 series graphics cards

As @alturismo already said, 50 Series GPUs only support the OpenSource version.

Anyone having issues with Emby server and transcoding? This used to work perfectly for me but now it just fails to start any video stream if transcoding is required. The FFMPEG log that Emby generates shows it selecting the Nvidia card etc. but then just fails seemingly with no actual error.

 

I've tried the official Emby dockers and also the linuxserver versions and both fail the same way. I can see from the nvidia-smi output that ffmpeg at least attemps to start transcoding 3-4 times and then fails.

Edited March 5, 20251 yr by allanp81

1 hour ago, allanp81 said:

I've tried the official Emby dockers and also the linuxserver versions and both fail the same way. I can see from the nvidia-smi output that ffmpeg at least attemps to start transcoding 3-4 times and then fails.

Please post your Diagnostics.

40 minutes ago, ich777 said:

Please post your Diagnostics.

 

server-diagnostics-20250305-1145.zip

1 hour ago, allanp81 said:

 

server-diagnostics-20250305-1145.zip 259.88 kB · 0 downloads

Something weird is going on.

 

You changed your GPU as far as I can see correct? Can you please try to use not the OpenSource drivers.

I've been trying all of the driver versions offered to me, none work but I've just done some testing with Jellyfin this afternoon and HW transcoding appears to be working fine so this looks like it's unique to Emby for some reason.

14 minutes ago, allanp81 said:

I've been trying all of the driver versions offered to me, none work but I've just done some testing with Jellyfin this afternoon and HW transcoding appears to be working fine so this looks like it's unique to Emby for some reason.

The last driver that you tried is definitely not working because it‘s the open soucre one.

 

However did you restart in between changing the drivers?

Please try to switch back to the latest driver, reboot and see if it‘s working again.

The open source driver worked within jellyfin but not Emby. I have rebooted after selecting a different driver to test. I have switched back to the production driver and will try Emby again but I suspect it'll still not work.

 

It seems that it's an Emby issue though and nothing to do with the nvidia driver so I'll go back to Emby. I paid for it so I will try and get some support from them...

9 hours ago, ich777 said:

As @alturismo already said, 50 Series GPUs only support the OpenSource version.

So, I assume eventually the 50 series will be able to use the other nvidia drivers? I only ask because I’m having trouble using that specific driver. My use case right now is using my gpu to pass to a code server docker for doing deep learning. 

1 hour ago, c625v12 said:

So, I assume eventually the 50 series will be able to use the other nvidia drivers?

What other drivers?

 

Only the OpenSource drivers are working with 50 series.

 

1 hour ago, c625v12 said:

My use case right now is using my gpu to pass to a code server docker for doing deep learning. 

Did you yet install the OpenSource driver yet and rebooted?

 

Please post Diagnostics after you‘ve done that.

5 hours ago, ich777 said:

What other drivers?

 

Only the OpenSource drivers are working with 50 series.

 

Did you yet install the OpenSource driver yet and rebooted?

 

Please post Diagnostics after you‘ve done that.

Hey thanks for the help. I realized my issue wasn't with the driver itself. That was working correctly.

On 2/23/2025 at 7:37 PM, ich777 said:

What is the Plex generator script and what do you mean with update?

 

What container are you using, Repository?

 

Diagnostics would also maybe help from after a "crash".

 

sorry it's this one; https://github.com/stevezau/plex_generate_vid_previews

 

I'll get more log info next time I see it. but basically just had to hard reset after the update because the container wouldn't stop again.

5 hours ago, sunwind said:

but basically just had to hard reset after the update because the container wouldn't stop again.

Please do keep in mind that applications inside a container and of course on the host can crash your server.

 

Can you please try to disable this script and see if your server crashes without the script running?

If your server doesn‘t crash I assume the script causes that.

I'm having trouble after upgrading from 6.12.13 to 7.0.1.

 

I keep getting an error that states

docker: Error response from daemon: unknown or invalid runtime name: nvidia.

 

I have uninstalled, reboot, and re-installed, reboot. Nothing seems to help.

 

Here is the full output from trying to spin up a container (frigate):

docker run
  -d
  --name='frigate'
  --net='dxsproxy'
  --ip='172.18.0.226'
  --pids-limit 2048
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="DXSUNRAID"
  -e HOST_CONTAINERNAME="frigate"
  -e 'FRIGATE_RTSP_PASSWORD'='enterpassword'
  -e 'NVIDIA_DRIVER_CAPABILITIES'='all'
  -e 'NVIDIA_VISIBLE_DEVICES'='GPU-52a8c529-6891-5577-59e0-4b5aab1807c4'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:5000]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/yayitazale/unraid-templates/main/frigate.png'
  -p '5000:5000/tcp'
  -p '8554:8554/tcp'
  -p '8555:8555/tcp'
  -p '8555:8555/udp'
  -p '1984:1984/tcp'
  -p '8971:8971/tcp'
  -v '/mnt/user/appdata/frigate/config':'/config':'rw'
  -v '/mnt/user/media/frigate':'/media/frigate':'rw'
  -v '/mnt/cache/swap/':'/swapfile':'rw'
  -v '/etc/localtime':'/etc/localtime':'rw'
  --device='/dev/apex_0'
  --shm-size=512mb
  --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000
  --memory=8g
  --restart unless-stopped
  --runtime=nvidia 'ghcr.io/blakeblackshear/frigate:stable'

docker: Error response from daemon: unknown or invalid runtime name: nvidia.
See 'docker run --help'.

The command failed.

 

Nvidia-smi and diagnostics attached. Please let me know if you need anything else.

nvidia-smi.log dxsunraid-diagnostics-20250309-2304.zip

1 hour ago, TheEyeTGuy said:

I keep getting an error that states

The issue is this line here in your go file:

# Copy Docker daemon JSON
mkdir -p /etc/docker
cp /boot/config/daemon.json /etc/docker/daemon.json &

 

What contents do you have in that file (boot/config/daemon.json) and why do you even change the daemon.json?

Hey guys, I made a post here with the full details, but in short, I believe my system is completely locking up due to my GPU and this plugin and I'm trying to find some help to validate the 3090 TI is supported. I can't easily replicate the failure, and when it does fail, the system is completely locked, so I have to power cycle it.

 

I can't post a screen shot as I've physically pulled the pulled the power cables from my 3090 so I can verify the system is stable (runs for more than 24 hours) and also let the parity check complete. I can verify the GPU was found and properly working (I've got ollama setup to use it) so I know the nvidia-smi command was properly finding the GPU.

 

I also saw something about how using this in a VM and docker-container can cause a hard freeze, but I'm not doing that. I had experimented with both, but I've unbound things from the VFIO page, and I also don't have any VMs currently setup.

 

Since it's a hard freeze, getting any logs is problematic. I did setup a syslog server, but the only message from around the time of the freeze was "monitor_nchan: Stop running nchan processes"

 

I also had similar issues when I was running a dedicated build of Ubuntu on this server (before installing Unraid 7.0.1) and I was able to resolve it by eventually finding the right driver version (I think I took several steps backwards/downgrading) but I haven't had that same luck here.

 

If I have to plug the GPU back in and run any additional diagnostics I'm happy to, I just need to know what commands I can do to start figuring out exactly what might be going wrong.

serenity-diagnostics-20250310-0838.zip