ich777

Looks like you have no Cache disk installed. Can you change the "ServerFiles" path to: /mnt/user/appdata/valheim instead of /mnt/disk1/appdata/valheim? Maybe this will help in your case.

Some cards need a little load on it so that it actually can even drop down to a lower power state, but if you've enabled nvidia-persistenced that is really weird. Seems like a driver bug to me but can't tell for sure, what you can do is that you post on the Nvidia forums if someone already experienced such a behaviour.

So everything is working again for you? What CMD files are you talking about? Do you changed anything within steamcmd.sh?

This is not really a error, have to tell @Squid about that. Do you run the VM on Unraid or do you run it on a external machine?

Do you have nvidia-persistenced enabled? Are you sure that it actually uses more power or is this displayed on the dashboard, keep in mind this readings are often not that accurate. If you are in the same power state (P8 - seems that you have nvidia-persistenced already enabled) it should idle like it does before the Plex transcode.

Can you be a bit more specific please? I've now tried it and it works flawlessly, here is the output from the Docker pull command: Pulling image: ich777/steamcmd:valheim IMAGE ID [valheim]: Pulling from ich777/steamcmd. IMAGE ID [a2abf6c4d29d]: Already exists. IMAGE ID [2093c0a488bc]: Already exists. IMAGE ID [9164366befb9]: Pulling fs layer. Downloading 100% of 11 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [273c8055b36c]: Pulling fs layer. Downloading 100% of 2 KB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [753e1ebc1953]: Pulling fs layer. Downloading 100% of 3 KB. Download complete. Extracting. Pull complete. IMAGE ID [75859e523978]: Pulling fs layer. Downloading 100% of 3 KB. Verifying Checksum. Download complete. Extracting. Pull complete. Status: Downloaded newer image for ich777/steamcmd:valheim TOTAL DATA PULLED: 11 MB And here is the container log: valheim.log Everything is working as expected, at least on my server.

I really don't get the point from this post...

Container is now be fixed and is now wroking, thank you for the report! Please do a on the Docker page for the container.

Is your transcoding path set correctly and has the container write permissions to this directory?

Please look into the documentation: Click You need at least a VM with OVMF as the BIOS type then you should be good to go to change it like in the above mentioned documentation and you have to be at least on Unraid version 6.10.0-rc2

I'm only the maintainer for the template for Unraid, I'm not the creator from the application itself. Do you have Nextcloud? You can mount the import folder from Photoprism from the host to the Nextcloud container and then mount it through the External Storages plugin within Nextcloud so that you can manually upload pictures to a certain folder in Nextcloud manually.

If you plan to do a manual upload anyways would it maybe be a solution to mount the import folder also to your Nextcloud instance as an external source, of course if you have Nextcloud... If you do it like this you could easily use Nextcloud for uploading files manually. From what I know uploading photos is only possible to one directory and that is the import folder, however you can index multiple directories but that is a different thing because they are only indexed and not imported. Maybe try to open up a Issue on the official GitHub from Photoprism here to get a answer from the developers, if it's possible to import from multiple sources please let me also know: Click

Yes, a cache drive for Unraid? If yes, to what is the cache drive set in terms of Use Cache in the Share settings? Can you share a screenshot from your entire Docker template?

Can you try to create a variable like in this thread:

Is the container restaring or is it running? How much CPU and RAM did the container use? On what Unraid version are you? What CPU do you have?

I really don't know 7DtD good enough but from what you described it can only be a problem with your PC or files...

Did it work on your friends machine? I would recommend before you reinstall your OS that somebody else tries to connect to your server and see if they got the same issues. Have you anything simmilar hearlike this before @Spectral Force?

No I haven't changed anything in the last few weeks. That seems like an issue with the game itself and not the container, can you try to validate the files on your local computer? This was only a minor change and do not change anything if it's set to false. Does your friend experience the same that he falls out of the world? As said above, this sounds more like a issue with the game on your local computer itself.

If you run the server without the plugin it does work? Can you SSH into the server? If yes what does the command 'nvidia-smi' give you if you can SSH into your server? From what I can see in your syslog the driver crashes right after it is loaded. Do you have Above 4G Decoding enabled in your BIOS?

Just the Nvidia Driver plugin is enough if you want to use your Nvidia card for HW transcoding in Docker containers.

Can you maybe try a different file? Please send over a screenshot from your Playback settings in Jellyfin.

Isn't this a VP8/9 file since it tries to load the vpx libraries (keep in mind your processor doesn't support that)? Please go to the Jellyfin settings and enable only H264.

Please look at this table which will show the capabilities from your CPU (Haswell): Click Is not possible with this CPU since its basically to old. From what I know it even struggles sometimes with some higher tier h264 files. Are you really sure that this happens on your system with h264 files too?

Please post your Diagnostics, without the Diagnostics I can't help... Can you also be a bit more specific? I also run my Jellyfin container and it works flawlessly on Comet Lake and even on a J3155. What media type h264, h265,... do you want to transcode?

Habt ihr einen Monitor dran bzw. einen HDMI Dummy? Das ist meistens essenziell das er nicht crasht.