ich777

Sorry, I completely overlooked your post. Can you please post a screenshot from your template (maybe blur the token). May I ask for what Game ID did you create the token?

I need the Diagnostics not the Nvidia bugreport.

Are you really sure that your RAM is okay? As said my best guess is that there is something wrong with the RAM and the files not installing correctly. Are you on the latest BIOS version? There must be something else going on since I also tested this exact driver package and it is working fine over here.

Please make also sure that the files stay on this Pool and are not moved to the Array in the Share settings because otherwise you will run into problems again.

Have you yet tried to reboot? BTW, this is the wrong location the file is located in /usr/lib64 you are actually looking at the 32bit libraries in the screenshot above. Have you any special scripts in place that maybe modify the PATH variable on your system or something similar? I can't see anything obvious from your Diagnostics at a first glance. The only thing that is a bit strange that the driver got not installed early in the boot process since it should be installed and pick up the card early. You could of course try to: Remove the plugin Reboot Install the plugin Reboot May I ask why did you had to remove the docker.img? Hardware fault? My best guess else is that something is going on with the RAM but that is just a vague guess since the driver get's also installed into the rootfs which on Unraid is the system memory.

Please post your Diagnostics.

Why did you enable validation? Please disable it. On what system do you try to run the container? Did you change already some config files? Please note that I always recommend to use the real file path (this applies to the game files only) not the FUSE file path to the files. /mnt/user/... in this case is the FUSE file path and some games will segfault and refuse to start.

The path in the container to the gamefiles is always: /serverdata/serverfiles/ Sorry but I really don't know how to mod a ARK server.

Did you change something in the template? It seems the container can't find the files or is not able to start V-Rising. Are you sure that the path for the Gamefiles is correct? May I ask why did you enable verification from the game files? On what system are you trying to run the container?

Please always include Diagnostics. Anyways, you got a XID 79 error which you can read more about here. On what BIOS version are you? In which slot on your Motherboard is the card? Is Above 4G Decoding and Resizable BAR support enabled in the BIOS?

I would recommend that you create an issue over here on GitHub in the repository form @Frank Crawford since he is the maintainer for the driver and I only made a plugin that his driver is available for Unraid.

Support only in English over here, if you want/need help in German then please post in the German subforums. I usually can't help with modding containers since this is up to you because I can't know how every container handles mods.

Please remove your Steam credentials form the template, they are only required if the are not hidden away under the "Show more..." Section and marked with the red asterisk. I would recommend to stop the container, remove the directory from the appdata folder for the game and then remove the credentials and start the container afterwards.

Do you have Host access enabled in your Docker settings?

If nothing is using your iGPU actively the answer is no, what you are seeing is correct. What do you mean by that? You have to configure transcoding and even force a transcode to be able to see some utilisazion in the GPU Statistics plugin on the Dashboard or in intel_gpu_top

I think you all should mention @binhex here and not just only write which containers are affected.

But that is not the same problem. Do you see your iGPU in GPU Statistics? If yes and your only issue is that transcoding is not working please go to the support thread from the container that you are using for transcoding. Most of the times it‘s a container issue, for such new CPUs the container needs QSV and not VAAPI. If you are unsing Pley maybe try Jellyfin because it‘s free or try Emby and pay for a month to test.

The Fritzbox should be discovered automatically IIRC, sorry I don't have a Fritzbox, maybe @sonic6 or @alturismo can help here a bit.

Kannst du das hitte nochmal reproduzieren und wenn das dann passiert ist bitte kopiere von /var/log die datei syslog in deinen Bug Report. Verbind dich einfach mittels ssh mit WinSCP oder ähnlichem damit du die datei runter bekommst.

Ja kannst du auch. LXC is eben eine mischung aus Docker und VM, sprich es is mehr oder weniger einer VM jedoch mit geteilten resourcen so wie Docker, noch dazu bekommt jeder container eine eigene IP, du musst nicht mehrere komplizierte anleitungen schreiben, es is alles in einem image und vermutlich noch mehr was ich hier vergesse. Natürlich kannst das auch mit keepalived verwenden damit wenn dein Unraid server down ist oder der LXC container das ein backup PiHole/AdGuard (der zB auf einem RaspberryPi oder irgend einem SBC läuft) seamless übernehmen kann ohne dein eingreifen. Sieh dir dazu mal mein Image hier an: https://github.com/ich777/unraid_lxc_pihole Wenn du es testen willst lass es mich wissen (erfordert momentan nur ein kommando vom Terminal) und dann installation in der Unraid GUI. 😉

Oh, things where working quiet differently back then. However I would strongly recommend that you either get a card that is supported by the Nvidia Driver plugin but I will look into that but as said it will take some time. May I ask why you need GUI mode in the first place?

Look at this post here: Seems like you CPU doesn‘t support reporting RX and TX from the Integrated Memory Controller. If you don‘t see it in intel_gpu_top then your CPU simply doesn‘t report it and therefore it can‘t be displayed in the GPU Statistics plugin.

Kein ding, versteh ich zwar nicht wirklich weil es anders doch wirklich einfacher/sinnhafter wäre bzw. auch aus Sicherheitstechnischer Sicht besser wäre, aber wenn das Ding sowieso bei dir zu Hause steht is es auch egal. Solange es für dich funktioniert alles gut.

Naja warum sollte ich auch, ich will noch ein Leben auch haben. Warum sollte ich, bekomme eine Nachricht, KISS. Warum? Mein Backup ist doch bei mir zu Hause, wüsste nicht warum ich das verschlüsseln sollte. Oh no, das soll ein Mirror sein bei mir, inkrementell ist auch nicht 3-2-1. Wenn das dein einziges Backup ist verstehe ich das.

Naja, du schaltest die Synology an und dann zieht praktisch die Synology das Backup von deinem Server. Bei mir sieht das so aus das auf meinem Backup Server auch Unraid läuft und dort wird ein User Script bei jedem Start ausgeführt das mir eine Nachricht schickt das eben das Backup in 2 Minuten beginnt (falls ich noch abbrechen möchte oder so) dann wird das Backup in luckyBackup gestartet und am Schluss vom Backup wird ein "controll file" geschrieben das dem User Script dann sagt das es mir nochmal eine Nachricht schickt das eben das Backup fertig ist und dann wird der Backup Server automatisch heruntergefahren. (das User Script läuft die ganze Zeit im Hintergrund und prüft alle paar Minuten ob das "controll file" schon geschrieben wurde wenn es geschrieben wurde, wird es gleich wieder gelöscht und dann eben wie oben beschrieben Nachricht -> Shutdown) Sprich ich muss den nur an den Storm anschließen und auf die Nachrichten warten. Kommt eben drauf an ob du auf der Synology auch ein Script laufen kannst das mit dem Docker Dienst interargieren kann.