ich777

Sure, but I just wanted to point that out that the post that you‘ve linked was made because of my plugin. Anyways, really strange that your shared folders are dropping. Have you somewhere posted your diagnostics to investigate further what‘s going on there but I guess that‘s now too late because as you‘ve wrote above you moved on to ESXi.

Then may I ask why you link to the post? This was definitely a issue with my plugin and was only a issue when the LXC plugin was installed but after I was informed about that I looked into that and updated the plugin so that this won't happen anymore in a matter of days IIRC. But please keep in mind I'm a community developer and not related to Unraid.

Please try this, the issue is that I only show the latest 8 drivers in the plugin and the 470 driver version is on position 9 or even lower (I will maybe change that so the 470 driver shows up all the time, but that this will take a few days). To install the 470 series driver issue this command: sed -i "/driver_version=/c\driver_version=470.141.03" /boot/config/plugins/nvidia-driver/settings.cfg from a Unraid terminal, after that go to the plugin page or simply reload it and click "Update & Download" (please note that none of the radio buttons should be selected). After you did that you should see that it downloads driver version 470.141.03 (please note this will only work on 6.11.5) after it finished downloading reboot your system.

The only Nvidia GPU that I see in your system is a GTX680: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 680] [3842:3688] Kernel modules: nvidia_drm, nvidia 01:00.1 Audio device [0403]: NVIDIA Corporation GK104 HDMI Audio Controller [10de:0e0a] (rev a1) And the syslog also tells you that it is a GTX680 and that this card is actually supported by the 470.xx series driver: Mar 1 09:01:32 MumboJumbo kernel: nvidia: loading out-of-tree module taints kernel. Mar 1 09:01:32 MumboJumbo kernel: nvidia: module license 'NVIDIA' taints kernel. Mar 1 09:01:32 MumboJumbo kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 245 Mar 1 09:01:32 MumboJumbo kernel: NVRM: The NVIDIA GeForce GTX 680 GPU installed in this system is Mar 1 09:01:32 MumboJumbo kernel: NVRM: supported through the NVIDIA 470.xx Legacy drivers. Please Mar 1 09:01:32 MumboJumbo kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Mar 1 09:01:32 MumboJumbo kernel: NVRM: information. The 530.30.02 NVIDIA driver will ignore Mar 1 09:01:32 MumboJumbo kernel: NVRM: this GPU. Continuing probe... Mar 1 09:01:32 MumboJumbo kernel: NVRM: No NVIDIA GPU found. Are you sure that this is actually a GTX1080Ti and that this card was working before with the 500.xx series driver?

Are we talking about driver updates or the actual plugin? What is not happening? Is the driver not working? What do you see on the plugin page (screenshot)? You haven't provided any information what's not happening... Please post your Diagnostics for further help.

No, if you doing just simple tasks (browsing the web, text editing) by using RDP you don't need a GPU. Usually not. But as said, I would recommend doing only light tasks since no HW acceleration is in place in the VM and everything is done on the CPU.

Both at the same time is not possible and I even don't recommend using it even if users are doing it that way. You can use one card for multiple Docker container but not for Docker and VMs at the same time.

I think the issue lies here within the custom version from ZFS for TrueNAS, I could be really wrong about that but maybe someone like @BVD or @Marshalleq can help here.

You have a Quadro 4000 and this card is simply to old to be supported by this plugin: Feb 28 20:55:01 Tower kernel: nvidia: loading out-of-tree module taints kernel. Feb 28 20:55:01 Tower kernel: nvidia: module license 'NVIDIA' taints kernel. Feb 28 20:55:01 Tower kernel: Disabling lock debugging due to kernel taint Feb 28 20:55:01 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 245 Feb 28 20:55:01 Tower kernel: NVRM: The NVIDIA Quadro 4000 GPU installed in this system is Feb 28 20:55:01 Tower kernel: NVRM: supported through the NVIDIA 390.xx Legacy drivers. Please Feb 28 20:55:01 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more Feb 28 20:55:01 Tower kernel: NVRM: information. The 525.89.02 NVIDIA driver will ignore Feb 28 20:55:01 Tower kernel: NVRM: this GPU. Continuing probe... Feb 28 20:55:01 Tower kernel: NVRM: No NVIDIA GPU found. For what do you want to use the GPU? This GPU won't do much in terms of transcoding because it simply too old, the next thing is that you can't use the legacy driver for Docker containers because you need at least a driver based on version 4xx.xx

The plugin and also the module is installed and loaded successful from what I see from your syslog. Did you create your Zpool like in the tutorial from the first post?

Ja, das empfehle ich auch immer.

The container is set up properly… I really don‘t play L4D2 much often but on random ocasions you will get people which will connect if their matchmaking settings match the ones from your server. L4D2 has it‘s own matchmaking system and will assign you to a random match if you search for one and servers with players on them get choosen first. I really don‘t know what you mean here, are you talking about the dedicated server or if you create a match on your local computer? I really can‘t help with that, back in the day when I was playing L4D2 with a friend of mine people joined and left randomly and everything was working as intended. TBH you are the first one who is reporting this for L4D2 and I‘m also assuming that it still works for others because I know for sure that this container is well used…

This is only true for L4D2… Usually you have a Server Browser, for example try to set up a basic CS:Source server, this is working completely different. Sorry I meant I shut down my server. As said above, by default you don‘t have a Server Browser in L4D2 and this is silply a „hack“ that you open it with the console…

I've edited the message above, I've now shut down the server because people started connecting to it (at least two)... Have you even read what I wrote above? The game isn't intended to be connected to a server like that...

At the custom tab and then hit refresh but you have to wait very, very, very long since L4D2 isn't intended to play or at least to connect to a server that way because you usually don't have the server browser by default there (you have to do the workaround with the console right?). You usually give your domain name like "mycoolserver.net:27015" to your friends and they'll add it and then you can start play and random players can connect to it if you are lucky. EDIT: I have now shut down the server because random people started connecting...

Please try to search for a game named: L4D2Mrtj18 I can see it and shows my public IP.

You can do it but that would be really complicated because every time a new Unraid version is released you have to compile the Kernel, afterwards you can build the driver, create a package for yourself and set it up so that it is installed on every boot. Sorry for the bad news but I'm scratching my head a long time to solve this issue but there is no real good solution in sight.

Can you please post your Diagnostics, people would be able to help more easily.

I will look into this and report back.

This is not (easily) possible because of the unique design from Unraid (because it runs out of ram) and you need the GRID guest driver which is not available to the public which I can't create a plugin/package for that because distributing the GRID driver would ultimately violate the EULA from Nvidia, I've explained it a bit more in depth here:

First of all I would strongly recommend that you remove the nvidia.conf file in the modprobe.d directory, you are not using the OpenSource Driver module... Have you yet tried to boot with CSM (Legacy) instead of booting with UEFI mode? Please also make sure that you are on the latest BIOS version, that you've enabled Above 4G Decoding and Resizable BAR Support in the BIOS. I would also try to switch from MACVLAN to IPVLAN in the Docker settings first. Is this only happening with Tdarr (if yes, IIRC this is nothing new that Tdarr can crash your server but TBH I really don't know if that was fixed already). Have you yet tried to disable Tdarr and see if this is happening too with Emby/Jellyfin/Plex? Do you can test the card in another system (install the drivers and put some 3D load for about 10 minutes on it, something like FurMark should do the Job just fine).

Please post your Diagnostics.

Use the mv command but please make sure that you have a backup from the whole LXC directory where it's currently located. Do something like this: First stop the LXC Service in the Settings tab Move the whole LXC folder from the current location to the new location with something like: mv /mnt/disk1/lxc /mnt/disk2/ (please keep in mind that the move process can take a really long time and make sure that you leave the terminal from Unraid in front or even better connect through SSH to it and please don't close it!!!) Change the path to match the new path in the LXC Settings Start the LXC Service As said above, I've never done this but the above should at least work (make sure as pointed out above that you create a backup from the old directory first!

I can't display a error message when there is nowhere one to be found... You only can start the container with: lxc-start -F CONTAINERNAME and hope that you see a error message but I don't think you will see one if you have a typo somewhere. Nice that you've figured it out.

Then you just have missed the space or something like that, the --restart=unless-stopped does not harm anything... You have to use a space and not a semicolon.