ich777

Most of the time this is a CDN/SteamCMD issue that not all CDN's are updated yet, please wait a few more hours and try later.

Please stop the container Delete the steamapps folder in your game directory Start the container again

I see a few issues with the docker run. Is DRINODE and DRI_NODE correct, I don't think that you need both, please also remove: --gpus all and try to add these environment variables (like mentioned in the second post): KEY: NVIDIA_VISIBLE_DEVICES VALUE: your GPU UUID from the Nvidia driver plugin KEY: NVIDIA_DRIVER_CAPABILITIES VALUE: all After that try to run the container and see what it does please.

I think I'm not in that Discord (even don't know which ono this is), could you please send me some screenshots please? It just shows no text channels. However I'm looking into that but TBH I have to say I don't even know where to start. Do you have a link from the container, how do you run the container, where is your docker run output, do you have any Diagnostics, do you use wayland,...?

I'll look into that, give me a few days.

That is in theory possible but would might cause incomplete backups. There would be workarounds to that but I'm not too sure if you use for example BTRFS as the storage backend and take a backup which means a downtime of about 5 seconds with snapshots enabled because the flow would be: Stopping the container Taking a Snapshot Starting the container Taking the Backup from the snapshot Deleting the Backup This would of course be only that quick if the container is using the BTRFS storage backend.

Can you please link the correct convo, you linked linuxserver.io directly

I would imagine that like container images and that is already possible with the current LXC implementation, as an example you can look here: https://github.com/ich777/unraid_lxc_pihole This is just an example and very outdated now. Was communicated already a few times but as said, that never took off. I also don't see the real point, on Unraid you should use Docker since they are more easy and versatile, sure for some things LXC makes more since for something like AMP or even DNS, PiHole and so on. Issue is that Proxmox has a completely different approach from what I know.

Remove the plugin, reboot, install the plugin again, reboot.

The Plugin date almost never changes but that doesn't mean that you have an outdated version since the plugin downloads the packages for your running Unraid version which is the date you see on GitHub. You don't have to do anything usually, install the plugin and reboot.

This was discussed a few times but never took off, don't know if there are further plans.

Please don't forget that this is almost like a real VM with it's own MAC address and so on, you have two options: Set a static IP address in your DHCP server for the containers MAC address Set a static IP address in the container (that always depends on which distribution is used and is out of scope for this thread)

Sorry but this is not really helpful, no Diagnostics, no logs, nothing... Don't know what to tell you other than: I think that might be a configuration issue in TVHeadend when the tuner is detected and scan fails (at least that's most of the times the issue). That was probably the error because it was drawing to much current from the USB Port and therefore it was reset by the system, some controllers are a bit more sensible to over current protection than others.

I see that in your log, it mentions an overcurrent: Apr 8 19:00:42 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in cold state, will try to load a firmware Apr 8 19:00:42 Unraid kernel: dvb-usb: downloading firmware from file 'dvb-usb-id5530.fw' Apr 8 19:00:42 Unraid kernel: tbs5530: start downloading tbs5530 firmware Apr 8 19:00:42 Unraid kernel: usb 1-2: USB disconnect, device number 4 Apr 8 19:00:43 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in warm state. Apr 8 19:00:43 Unraid kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. ### [PREVIOUS LINE REPEATED 1 TIMES] ### Apr 8 19:00:43 Unraid kernel: dvbdev: DVB: registering new adapter (TurboSight TBS 5530) Apr 8 19:00:43 Unraid kernel: tbs5530: read eeprom failed. Apr 8 19:00:43 Unraid kernel: dvb-usb: MAC address reading failed. Apr 8 19:00:43 Unraid kernel: i2c i2c-8: cxd2878:Can not detect the chip. Apr 8 19:00:43 Unraid kernel: i2c i2c-8: cxd2878:error attaching frontend. Apr 8 19:00:43 Unraid kernel: dvb-usb: no frontend was attached by 'TurboSight TBS 5530' Apr 8 19:00:43 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected. Apr 8 19:00:43 Unraid kernel: usbcore: registered new interface driver tbs5530 Apr 8 19:00:43 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully deinitialized and disconnected. Apr 8 19:00:44 Unraid kernel: usb 1-2: new high-speed USB device number 5 using xhci_hcd Apr 8 19:00:44 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in cold state, will try to load a firmware Apr 8 19:00:44 Unraid kernel: dvb-usb: downloading firmware from file 'dvb-usb-id5530.fw' Apr 8 19:00:44 Unraid kernel: tbs5530: start downloading tbs5530 firmware Apr 8 19:00:44 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in warm state. Apr 8 19:00:44 Unraid kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. ### [PREVIOUS LINE REPEATED 1 TIMES] ### Apr 8 19:00:44 Unraid kernel: dvbdev: DVB: registering new adapter (TurboSight TBS 5530) Apr 8 19:00:45 Unraid kernel: dvb-usb: MAC address: 00:22:ab:c0:7c:c7 Apr 8 19:00:45 Unraid kernel: i2c i2c-8: Detect CXD2878/CXD6822(SiP2) chip. Apr 8 19:00:45 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 0 (TurboSight TBS 5530 DVB-T/T2/C/C2,ISDB-T/C,ATSC,J83B)... Apr 8 19:00:45 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in cold state Apr 8 19:00:45 Unraid kernel: i2c i2c-8: downloading firmware from file 'dvb-demod-m88rs6060.fw' Apr 8 19:00:46 Unraid kernel: e1000e 0000:01:00.0 eth1: NIC Link is Down Apr 8 19:00:46 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in warm state Apr 8 19:00:46 Unraid kernel: i2c i2c-8: firmware version:30 Apr 8 19:00:46 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 1 (TurboSight TBS 5530 DVB-S/S2/S2X)... Apr 8 19:00:46 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected. Apr 8 22:55:27 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 0 (TurboSight TBS 5530 DVB-T/T2/C/C2,ISDB-T/C,ATSC,J83B)... Apr 8 22:55:28 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in cold state Apr 8 22:55:28 Unraid kernel: i2c i2c-8: downloading firmware from file 'dvb-demod-m88rs6060.fw' Apr 8 22:55:29 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in warm state Apr 8 22:55:29 Unraid kernel: i2c i2c-8: firmware version:30 Apr 8 22:55:29 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 1 (TurboSight TBS 5530 DVB-S/S2/S2X)... Apr 8 22:55:29 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected. Apr 8 22:59:52 Unraid kernel: usb usb2-port1: over-current condition In your testing was the USB TV Tuner connected to the same USB Port? You also have a lot of that in your log: Apr 10 09:01:49 Unraid kernel: usb usb2-port1: over-current condition Apr 10 09:01:49 Unraid kernel: usb usb1-port10: over-current condition Apr 10 09:01:49 Unraid kernel: usb usb2-port1: over-current condition Apr 10 09:01:50 Unraid kernel: usb usb1-port10: over-current condition ### [PREVIOUS LINE REPEATED 5 TIMES] ### Apr 10 09:01:50 Unraid kernel: usb usb2-port1: over-current condition Apr 10 09:01:51 Unraid kernel: usb usb1-port10: over-current condition Apr 10 09:01:51 Unraid kernel: usb usb2-port1: over-current condition Apr 10 09:01:52 Unraid kernel: usb usb1-port10: over-current condition Apr 10 09:01:52 Unraid kernel: usb usb2-port1: over-current condition Apr 10 09:01:52 Unraid kernel: usb usb1-port10: over-current condition ### [PREVIOUS LINE REPEATED 1 TIMES] ### Apr 10 09:01:53 Unraid kernel: usb usb2-port1: over-current condition Apr 10 09:02:15 Unraid kernel: usb usb1-port10: over-current condition Apr 10 09:02:15 Unraid kernel: usb usb2-port1: over-current condition Apr 10 09:02:15 Unraid kernel: usb usb1-port10: over-current condition ### [PREVIOUS LINE REPEATED 4 TIMES] ### Apr 10 09:02:16 Unraid kernel: usb usb2-port1: over-current condition Apr 10 09:02:17 Unraid kernel: usb usb1-port10: over-current condition Apr 10 09:02:17 Unraid kernel: usb usb2-port1: over-current condition

@digitaldoctor sorry, seems like I can't quote anything, however possibly, the tutorial is there. But I can't guarantee that it works but since it's LXC it should. However I also can't tell if it's safe.

Looking good to me.

Please try to reseat the card but this seems like an issue with the PCI bus but I could be also be wrong about that. Is your Power Supply up to the task? Please also try to update the BIOS if there is a newer BIOS version available and maybe also try to reset the BIOS back to defaults, sometimes it's only a small setting that needs to be changed.

How did you add that exactly? Diagnostics alongside your docker run command would be good to know.

Please do the following from a Unraid Terminal: echo "blacklist nouveau" > /boot/config/modprobe.d/nouveau.conf after that reboot (you will get no output from the command). This is caused because the card is bound to the nouveau instead to the nvidia driver as you can see here: 0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) Subsystem: EVGA Corporation Device [3842:3975] Kernel driver in use: nouveau Kernel modules: nouveau, nvidia_drm, nvidia

Please always post your Diagnostics, without them troubleshooting is impossible.

@SimonF would you mind taking a look at that since this would revert pretty much everything from your PR. @Valtos depending on what @SimonF says, does the PR or better speaking also take into consideration that a user has multiple GPUs installed in his system? If so is there an index displayed? I would also like to turn the logic around for the driver so all drivers are OpenSource except for the legacy 580.x driver version, so to speak OpenSource goes away and it says Legacy there.

Please create an issue in the appropriate support thread, this is the support thread from the Prometheus Plugins not Prometheus itself. Click on the Docker icon in your WebUI and click Support.

Are you 100% sure that there is no space at the beginning, it looks like there is one space there:

I don't think that Unraid is the culprit here since I just tested it and with Jellyfin everything is working as expected.

Did the container start with --runtime=nvidia If yes, then the issue lies somewhere else.