ich777

I assume a download failed from the Nvidia Driver maybe with the update check but I can't tell for sure since there is a unfinished download in the Nvidia Driver Plugin folder. However I see that you are on Unraid 6.12.0, please consider upgrading to something recent since I really can't tell if everything is working on such an "old" version. I would also recommend that you consider buying Unraid instead of pirating it. @SpencerJ

I don't know, please post your Diagnostics, without them I can't say anything.

What Unraid version are you on? Diagnostics, please?

Can you point me to the ones that have reverted because of Nvidia not working? It is really obvious why it's not working in your case, because you've enabled for whatever reason the nouveau driver by creating the file /boot/config/modprobe.d/nouveau.conf Please remove that file and the driver will work again, even your syslog just tells that: Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: GPU 0000:42:00.0 is already bound to nouveau. Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s). Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: This can occur when another driver was loaded and Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: obtained ownership of the NVIDIA device(s). Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: Try unloading the conflicting kernel module (and/or Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: reconfigure your kernel without the conflicting Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: again. Jul 14 16:15:51 GKOPUNR-2 kernel: NVRM: No NVIDIA devices probed. BTW, these are the download counts for 7.1.4 and I think if that many people are having issues with the driver, this thread would be exploding: name: 6.12.24-Unraid, name: nvidia-565.77-6.12.24-Unraid-1.txz, download_count: 564, name: nvidia-570.144-6.12.24-Unraid-1.txz, download_count: 1626, name: nvidia-570.153.02-6.12.24-Unraid-1.txz, download_count: 2151, name: nvidia-570.169-6.12.24-Unraid-1.txz, download_count: 2085, name: nvidia-575.51.02-6.12.24-Unraid-1.txz, download_count: 14661, name: nvidia-575.57.08-6.12.24-Unraid-1.txz, download_count: 10163, name: nvidia-575.64-6.12.24-Unraid-1.txz, download_count: 8852, name: nvidia-575.64.03-6.12.24-Unraid-1.txz, download_count: 8570, name: nvos-570.144-6.12.24-Unraid-1.txz, download_count: 684, name: nvos-575.57.08-6.12.24-Unraid-1.txz, download_count: 458

Please, as mentioned in the first post, post your Diagnostics, I really can't tell anything without them (please note that I need Diagnostics from 7.1.4). Many people are using their cards just fine with 7.1.4

And that's the error, don't do that unless it's not hidden under Show more and only fill in when marked with the red asterisk.

Please post a screenshot from your template. What I would recommend doing: Remove the container Remove the folder for Rust in your appdata directory Grab a fresh copy from the CA and click Apply without changing anything Open the logs and wait for it to finish <- this might take some time, please don't restart the container even if it seems like it's frozen

By default the port mappings are: 21115-21119:21115-21119 & 21116:21116/udp At least that's what's in the template here.

No worries about that, it possibly couldn‘t get the update, however most of my containers are self maintaining and they pull updates on container restarts. This is a known thing if you are a few versions behind since Docker is out of date.

Possibly AMD related but I really can't tell since I don't have a 50 series card on hand however it seems that some cards run out of Kernel memory and that's why you are seeing this issue, to all of that why that happens I really can't tell whats happening there.

No, a dedicated server doesn‘t require a GPU. Only one and I wasn‘t able to reproduce. On what hatdware do you run the container and on what Unraid version are you? Did you change any configuration files?

So everything is working now?

Do you have Diagnostics please?

I would recommend that you try to upgrade and see if that works.

I'm on the latest version and it works just fine. Since you don't answered, on what hardware do you run Unraid?

Can't reproduce that over here, the server is just running fine without restarting, did you change by any chance any setting or is this all vanilla? On what Unraid version are you? What machine do you run the container on?

This is a known issue when you exceed the vGPU vRAM limits and you know, applications and even the OS changes over time an it might be the case that it was running for years fine but now because of some change in the OS/applications/driver you are now experiencing these issues. If you go through this thread you'll find a few such reports which ultimately are unsolved.

I already explained that a few times here in the thread and always depends on your preference and if you already have a build environment. My build environment got pretty complicated over the years, I use Jenkins with the Cloud Bees Docker plugin for Jenkins to build my containers in a dedicated LXC container and then push it locally from my Server to DockerHub and GHCR.io however nowadays one could easily set that all up with GitHub Actions, again it's always up to preference. Don't know if I can teach someone how to create a Dockerfile and bash scripts since what I do is basically automate the download/update check and starting the game server. You can always look at my GitHub or to be more specific into the SteamCMD repo and open the tags <- this is a bit unconventional but it works very well for me. https://github.com/ich777/docker-steamcmd-server It's all open source what I do.

On what hardware are you running the container? You are on Unraid 7.1.4 correct?

This seems perfectly fine, how much resources does the container consume?

It seems that the VM doesn't know from where to boot. No it shouldn't cause any issues.

Did you also remove the entire image, so to speak container, and also tried it with the default settings.

It might be possible that the savegame is too old and so the server doesn't run properly anymore. Can you try to set up a completely new install, of course back up your old instance first, and see if the new instance is running?

Can you try to set up a completely fresh installation from Satisfactory, of course backup your old instance first, and see if the new instance is running?

I'll look into that but if I can't get it running I might have to deprecate the container. I now tried it with a new instance and everything seems to work just fine without restarting.