ich777

Plex tries to use the iGPU, don't ask me why. I think you should really ask in the support thread from the container or the Plex forums itself. This seems not related to the Nvidia driver nor the GVT-g plugin.

And you are sure you've passed over the correct GPU with the correct GPU since you've mentioned in your previous post that you are using a P4000 and now that you are using the 1050Ti...? Just asking... And what is the error in Plex? The exact error, Plex refuses to transcode is pretty random... How do you test that? I hope you don't use the Plex Web Player, as if you have reported it in the correct thread Nvidia Driver thread then you maybe would have seen that since the last post was exactly about that.

I still don't get it why people are doing that. Never ever enable Privileged mode! Privado is working fine AFAIK. Please us the support thread that @Rysz pointed out (you'll also find that when you go to the Docker page -> click on the container icon -> click on Support.

Yes. Can you please be a bit more specific? What is not working? In which container do you use the card? Sorry but I only se a 1050Ti in your system an not a P4000: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) Subsystem: PNY GP107 [GeForce GTX 1050 Ti] [196e:11c3] Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia I only see in your syslog that you already have removed the driver and reinstalled it once, which btw will do nothing if you don't reboot in between. Please think again about it, you've done a BIOS update to get GVT-g working (which was in my opinion a wrong set option in the BIOS, because if you update the BIOS all settings are reverted to default) and maybe a setting is now set wrong but please be aware that I don't see any issues in you Diagnostics and it should work fine, it is even recognized fine by nvidia-smi.

TBH I never heard from someone that the web app crashes the whole server or makes it unusable… only that it stays black and the transcode never starts.

Please check your Plugins page if you have any plugins in the Plugins Error tab If so remove them, reboot, install them again from the CA App and reboot again if required.

Seems like a broken savegame. Did you enable the automatic backups? You could try to restore a previous backup. Not at all, my server is still running with the savegame from day one.

I think you completely missed that and the following post: The package is already part of the container.

I'm not sure, maybe it's also because it's running though WINE... I really can't tell. If you report it as not functional I'll deprecate the template.

Why not set it to the latest one? I would recommend that you reset your config and then try to strt the VM and see if it is working wothout the vGPU, after that you can try to add it again to the VM and see if it is working afterwards. Please try to assign the one with the 4 at the end. Maybe your BIOS is not fully compatible with GVT-g

You see there that it times out and this is exactly where it hangs (the few lines before will be displayed after it overcome this hurdle). After that it was able to connect. I have tried it multiple times and only once it was able to connect to their servers or better speaking there server to my server.

Please keep in mind that it is also possible this is caused because of WINE or because it was idle, did you experience any issues at that time <- this container is running with WINE and such messages are expected. That's the line where it tries to connect, you can always set registertolobby in your configuration.json to 0 so that it is not visible to circumvent that but maybe the connection from their servers is also flaky, I really can't tell... So it seems to work but sometimes, so I don't think that the container itself is the issue here because I've tried it today and also had no luck but I really can't tell why. I'll deprecate the container if you report it as broken.

Ich vermute du bist in DE, das ist mir zu weit weg...

Du kannst das im Terminal ausführen: echo " export TERM="xterm-256color" tmux" >> /root/.bash_profile danach machst ein neues Terminal auf (das fügt praktisch die Leerzeile und die beiden anderen Zeilen zu /root/.bash_profile hinzu und startet dir eine tmux session). Diese Lösung würde ich aber nicht empfehlen weil es glaub ich ziemlich sicher eine Fehlermeldung produzieren wird, dir eine neue tmux session auf machen wird und sicher noch andere Nachteile hat. Darf ich fragen warum du das überhaupt willst, auf Unraid selbst solltest du eigentlich nichts machen da dieser nicht als General Purpose Server vorgesehen ist und du solltest immer alles in Docker, LXC oder VM laufen lassen.

Are you sure that you are using my container, I don't have such a file in my container (/opt/tools/docker-entrypoint.sh). Please post a screenshot from your template configuration (make sure to enable Advanced View).

That's not entirely true, please also see the documentation: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces As @itimpi pointed out either use bridging with ipvlan (if you network gear supports it) or disable bridging and use macvlan.

Please update your Unraid version to the latest stable 6.12.8 and also make sure to use the latest Machine Type in your template. Do you have a screenshot from the plugin page please?

The package is now part of the container, please update the container itself and see if it is working.

IIRC there where quiet a few issues with these old Ryzen CPUs and PCIe cards especially Nvidia. I don't quiet remember but I think you have to disable C-States and maybe force PCIe Gen3 in the BIOS, it is maybe also a good idea to enable Above 4G Decoding and Resizable Bar support. Make also sure that you are on the latest BIOS version. I see nothing obvious in your Diagnostics, can you attach a Display to the card and see what happens when you start a transcode and maybe take a picture? As said above I remember quiet a few issues with those old Ryzen CPUs I think @SiRMarlon had similar issues.

Ich versteh noch immer nicht warum man das in Docker macht... Ich hab bereits einen fix vorgefertigten container dafür für LXC, sieh dir mal diesen Post an: Du kannst dann dort noch LANCache einpflegen. Ich weiß jetzt gerade nicht mehr was ich alles eingebaut hab in diesen Container weil das mal tests sind für die CA App integration damit mann dann fertige LXC container von der CA App installieren kann. Kannst dir mal alle container hier ansehen: https://github.com/ich777?tab=repositories&q=unraid_lxc&type=&language=&sort= Der PiHole container ist am "fertigsten" (mit Readme und allem, die anderen funktionieren natürlich auch alle OOB).

Please always include your Diagnostics.

Like a normal disk, iSCSI is only meant to share a block device or a image over the network, data integrity and maybe redundancy is up to you and how you set it up. Are you using a FileIO image on the Array? I wouldn't recommend that, instead I would put two disks in the server, share them over iSCSI and create a Storage Pool within Windows, that is way more efficient and would also heavily increase write speeds. You could also use ZFS if you really want too but I would not recommend using a FileIO image on the Array.

I'll look into that tomorrow.

You changed the port in the template but you changed it no where in the server config, so to speak that can't work... Please append that to the GAME_PARAMS: -port 27016 Source: https://developer.valvesoftware.com/wiki/Counter-Strike_2/Dedicated_Servers You always have to tell the dedicated server too on which port it is running because like you've done it now it simply can't work because you've forwarded the port 27016 (from inside the container, where the dedicated server is still running on 27015) so to speak the forwarding in the Docker fails... and yes, I know this is a bit complicated but otherwise it won't work. Always make sure to first change the ports in the container config, then delete the old ports from the template and then create new ones with the ports that you've set in the config for the dedicated server. Hope that helps, makes sense and explains it a bit more.

This is actually a indication that it restarts, are you sure that all ports with the correct protocol are forwarded? I can try the container myself tomorrow if you want me to.