ich777

Have you also tried to delete the modified serverconfig.xml and restart the container since it downloads a fresh default copy of the serverconfig.xml and see if it starts up just fine? No, I don't say that... Of course you can do that. To what is the Share set that gamefiles are in terms of Use Cache "Prefer", "Only", "Yes"? Can you also eventually post the full log output? EDIT: You can also reach out to @Spectral Force for help with the 7DtD Container since I don't own the game personally, this is from his signature:

I think so because the driver "captures" the card from what I know and isn't available for the VM, I also think it is eventually possible to set persistence mode for only one or two cards but I'm maybe wrong about that (I personally use persistence mode, I will look this up). EDIT: @Mr_Jay84 I think it should be able to set it only for one or more cards: Click nvidia-smi -i <target gpu> -pm ENABLED Enabled persistence mode for GPU <target gpu>. All done. The <target gpu> should be the HW ID I think (something like 0000:01:00.0). As said above this is dependent on the card itself and how the manufacturer implemented this in the BIOS of the card. Exactly that's the only way to tell if they are in P8 since you can't easily get the power state if they are bound to VFIO. This is also dependent on the card in which power state they are if you shutdown the VM.

Have you also added '--runtime=nvidia' at Extra Parameters (to see that you have to enable the 'Advanced View' with the switch in the top right corner of the template page).

Yes I know but there is a workaround for this but I have to search it, this is because the watchdog in the Kernel is now enabled with 6.9.1 and it now displays this "Warning" nothing to worry about, you can try to uninstall the GPU Statistics Plugin then the "Warnings" should be minimized to a few... EDIT: Here is the post from @b3rs3rk how you can suppress this message (never tried this but it should work I think): Where can I send you the money... Not sure which post to answer first... Have you turned persistence mode on? That should be no problem because the Nvidia Plugin don't capture the cards only if you turn on persistence mode. You can theoretically use one single card for Docker Containers and for a VM but not at the same time and if you are not carefully then this could lead to hard system lockups like you described in your post, I never recommend using one single card for both Docker and VM's. I think you are asking because your cards don't go to idle if you are not using it for something or am I wrong? Some cards can go to idle even if they are not used for anything but that depends on the model of the card an how the manufacturer implemented it in the cards BIOS. I think what you can try to do is that you bind the card for the VM to VFIO, assign it to the VM, enable autostart of the VM, write a script for the User Script's Plugin that runs on every reboot that wait's for about 2 or 3 minutes (so that the VM is fully started) and then turns it off again after the wait time with the command: 'virsh shutdown YOURVMNAME' (something like this should work just fine) if that is what you want to achieve, is the card your in P8 (this is also dependent on the card how the manufacturer implemented this in the BIOS of the card). Hope this helps and is what you wanted to know...

I think something with the servername or password is wrong, please try to stop the container and then restart the container again and see if it works if you start it up with the default parameters. My container is not for the mobile version and the desktop version is not compatible with the mobile version. To disable the autoupdate is not possible in my container... Also as said above the mobile version is not compatible with the desktop version. One thing also to note is that the server for the mobile version is only available for Windows or am I wrong: Click

Kannst du mal nachsehen was in deinem BIOS für die iGPU eingestellt ist? Wenn du eine Dedizierte Grafikkarte im System hast musst du die primäre Grafikkarte auf die iGPU setzten da die sonst nicht gestartet wird und einfach nicht da ist. Das ist klar, wenn der Docker Dienst beim starten des Containers das Verzeichnis '/dev/dri' nicht findet kann er nicht starten, wirft einen Error und bleibt gestoppt. Hast du das Intel-GPU-TOP Plugin drauf (nicht den Docker Container!) das macht genau das gleiche und du musst deine "go" Datei nicht bearbeiten. Probier bitte mal folgendes: Lösche das Intel-GPU-TOP Plugin Setze deine "go" Datei zurück auf folgendes: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Danach startest du den Server einmal neu (Emby startet dann nicht) Installiere das Intel-GPU-TOP Plugin (mach evtl. einen screenshot nachdem das Plugin installiert wurde - bevor du auf DONE geklickt hast und poste den hier) Emby manuell starten und es sollte jetzt auch starten Neustart Emby sollte jetzt automatisch starten, wenn nicht bitte nochmal die Diagnostics hier posten Kannst du wenn es nicht funktioniert hat ein paar Screenshots deiner Emby einstellungen hier posten? Ein bekannter hat das Plugin auch drauf auf genau dem gleichen board und dort funktioniert es einwandfrei.

Can you try to delete the container including the directory that is created in the appdata directory and pull a fresh copy from the CA APP. What I can think about is that some kind of picture/video that he want's to import is not compatible with RapidPhotoDownloader. Eventually it has something to do with this issue: Click (are there black and white png's in the folder he want's to import?) I tried it now on my own and can't reproduce the issue:

@LUCASINO So auf die schnelle sehe ich auch nicht warum die Festplatte hier nicht funktioniert. Bei der sdl steht nur DISK INVALID dabei und somit heißt das für mich das die dort eigentlich nicht hingehört. Würde mal versuchen das du die Disk neu zuweist, also einmal ohne der 2. Parity starten und dann nochmal die 2. Parity auf den Platz zusweisen, sei dir aber bewusst das ein Partiy rebuild ausgelöst wird (zumindest glaube ich das, hab noch nie mit einer 2. Parity gearbeitet da ich kein so ein riesen Array hab... ).

@Waddoo tried it now on my own on my DevServer with an GTX1050Ti and it should work: Here are a few screenshots from my template (please check also if you got no leading space at Nvidia Visible Devices) : This is the output from 'nvidia-smi' when I transcode from 4K to 480p: This is the output form 1080p to 480p: Here are my settings from Jellyfin: Have you eventually activated the last checkbox 'Tone Mapping active'? Can you send a few screenshots from your settings? Does this also happen when you transcode from 1080p to something different? I think something isn't working at passing through your Nvidia card to the container.

Was war das Problem?

Just upgrade and the iSCSI Plugin will update itself on the start of the server.

Hast du das Intel-GPU-TOP Plugin noch drauf? EDIT: Das darf eigentlich nicht passieren da mein Plugin unter anderem das gleiche macht wie du im go script. Wichtig ist nur das es installiert ist.

Ich kann mir sehr gut vorstellen das es generell durch die modprobe ausgelöst wird, und bitte räum dein go file ein wenig zusammen... #!/bin/bash # Start the Management Utility modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri /usr/local/sbin/emhttp & So wäre es besser: #!/bin/bash # Load Intel Kernel Module modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri # Start the Management Utility /usr/local/sbin/emhttp & Aber, wenn du mein Plugin installiert hast (Intel-GPU-TOP) brauchst du im go file nichts mehr einzutragen da mein Plugin die modprobe macht. Schau mal ob du das verzeichnis '/dev/dri' nach dem aufwecken aus dem Sleep noch hast, ich könnte mir vorstellen das deswegen der Container weg ist (öffne ein Terminal und gib 'ls -la /dev/dri' ein. Hast du sonst noch irgendwelche tweaks aktiviert? Sleep und Linux bzw. Unraid kann oftmals problematisch sein...

Hast du zufällig das Nvidia-Driver Plugin installiert und das Sleep Plugin? Die Nvidia treiber machen immer gerne mal Probleme mit Linux und Sleep. Leider ist das log zu wenig, du müsstest schon deine Diagnostics teilen (Tools -> Diagnostics -> Download -> die zip Datei hier in die Textbox ziehen.

Ja sicher kannst du Emby/Jellyfin nehmen, ich hab selbst auch Emby und bin sehr zufrieden damit.

@RicoWalker & @kripy BepInEx is now integrated. Pull a fresh copy from the CA App and you should see the option to enable it in the template.

Please update the container, fix is released and on the next update nothing should be overwritten.

I think there is something wrong with your settings (you should only enable the featureset of the tuner that you want to use something like in my case DVB-C and in your case only DVB-T): Then be sure to assign the Network to the tuner like so: and after that you should be able to create a Mux (something like in my case for DVB-C but only for DVB-T): Then it should hopefully start to scan and find all channels.

I'm not really into modding but can you give me the details which file is used to configure ValheimPlus, so that I can update the start script to back up the file and then copy it back over to the Valheim directory? EDIT: Is this the directory 'BepInEx/config/'?

The Plugin is done and working... I've already contacted @b3rs3rk about his GPU Statistics Plugin.

Kannst auch hier mal nachsehen welche, wieviele theoretisch (die consumer Karten haben ein Limit von 3 gleichzeitigen simultanen Transcoding Sessions) schaffen und ob die h265 können sprich HEVC: Klick

Nein, das gehört für Intel iGPU's bzw. AMD. Was verwendest du zum Transcoding Emby/Plex/Jellyfin (grad gelesen... Plex... )? Bitte mach dir bewusst das die GTX750Ti meines wissens nach kein h265 kann, also 4K transcoding wird trotzdem über die CPU laufen. Bitte installier das Nvidia-Driver Plugin aus der CA App und folg der Anleitung (1. Post und 2. Post): EDIT: Kannst auch direkt hier mal nachsehen was die theoretisch (Nvidia consumer Karten haben ein limit von 3 simultanen Transcoding sessions) schaffen: Klick EDIT2: Was hast du für ein System?

Yes, because the Kerne-Helper can't load the module inside the container and I don't like to hide errors since this is actually bad for troubleshooting but this is a common thing to happen in the Kernel-Helper. But if you install the images it should work all or am I wrong?

Oh sorry should be a little more specific, is it possible that you connect a monitor to the server and take a picture of what it displays when it's not booting? Oh yes, then it is the Nvidia Plugin. If you also need the Nvidia Drivers then simply make a build with the Nvidia Drivers and the vendor-reset patch (first uninstall the Nvidia Plugin, you can then install the Unraid-Kernel-Helper Plugin to see the UUID from your GPU).

Can you take a picture of the error when you are booting? I think three users (you included) reported this issue but have no fix so far, also created a issue on their Gitlab but no one responded yet. Can you post your diagnostics? I think it's some kind of weird combination of HW and SW but I can't tell exactly what it is. On my Intel i5 10600 with an ASUS Z490-E GAMING it works flawlessly.