ich777

Sorry but I don‘t know what even is going on on your system and why the permissions are set wrong. Maybe try to delete the files in the File Manager plugin which is available in the CA App.

Yes. The permissions are set on each container start.

You should set to Use Cache in the Share settings to Only or Prefer for appdata. For all other shares you should set it to Yes.

4GB of are too less for the base system and the driver nowadays. You need at least 8GB of RAM for the driver to work since they are getting bigger and bigger with each revision.

Did you install a driver and put a 3D load too? Uh wait, how much RAM do you have in your system? How much space do you have on your USB Flash device?

Yes, plase head over to GitHub and read this issue: Click You have to extract the start command and put it in the variable then it will work. Hope that helps.

@KennySPT I had to hide your post, please read the first post and read the red text!

Are you really sure that the card was working before? Please test it if possible in another system. No.

Do you have by any chance a syslog from a crash? Can you still connect to Unraid via SSH after installing the drivers? Was the card working before? Nothing obvious in the Diagnostics from what I see.

It is available in the CA App, search for „SurviveTheNights“.

@Tristankin & @muzo178 you can at least try to change the container to the official one and see if that males a difference, they should be all interchangeable and you only have to replace the Repository in the template. But just to be sure create a backup from you plex directory in your appdata folder so in case that something goes wrong you can revert back <- but it shouldn‘t go anything wrong.

This is the same error as before, are you sure that your cache drive isn‘t dying? This indicates usually an issue with Docker.

The containers are not really big in terms of size because they download the game on the first start. Exactly. Just search for something like „ark linux dedicated server“ and you should find specifications on how big the games are in terms of size and what the recommended hardware specifications are (you should find then something like this) in case of ARK it is about 15GB. No, because dedicated game servers are documented usually really well and have their own wiki/forum/setup instructions which are up to date where as if I run a dedicated wiki for them it could be outdated and would be really difficult to maintain for me. Hope that makes sense to you. The container can do basically everything like if you run it on bare metal on a Linux server. As a little side note, modding from the containers is always up to the user because I simply can‘t know how to kod each individual game server but I try to help where I can.

You can disable transcoding in Plex or better speaking disable HW transcoding. No, if your system is fast enough to keep up with software encoding for the time you test Jellyfin it would be fine. Maybe test it intensely while playing a file over and over. Exactly, then you can take a picture of that and maybe we can see more... Please remember this is the non Alder Lake thread... Are you both on the official Plex version? Can you post your Diagnostics too @muzo178?

I don't see that you've enabled cgroup v2 like mentioned in the first post. You have to put "unraidcgroupv2" in the same line not below...

This is really weird, have to look into this, definitely strange. The Snapshot feature should also work fine, but please keep in mind if you take a snapshot leave the tab in the foreground.

No, you have to connect a monitor, swapping out the dummy plug with a real monitor won't work in most cases because the EDID is not the same on the dummy plug as on the monitor and because your system crashed the driver can't initialize the new EDID, hope that makes somewhat sense to you. But that is not the question, the question is if the same crashes happen on Jellyfin too...?

I just want to report my experience with it. I have VT-d on one system disable and on the other it's enabled. Please post your Diagnostics again from a 6.11.5 installation. I can't remember but have you tried Jellyfin back then and if it's the same? Are you also able to hook up a monitor to your system and issue this command from a Unraid console (this will prevent the monitor going to sleep): setterm --blank 0 With this you will be able to take a picture when the crash happens since most of the times the syslog server will not be able to record those issues.

I have now the following Intel CPUs tested with Unraid 6.11.5: i3-6100T, i7-7700, i5-8400, i5-10600, J4105, i5-6300U and G4400T Motherboards are Asrock, Asrock, Fujitsu Esprimo, ASUS, Fujitsu Futro, Fujitsu Laptop, Fujitsu Esprimo. None of them crashed so far after about a month of uptime and continuous transcoding with Unmanic on Unraid. Most of the systems don't have anything else installed than Intel-GPU-TOP and Unmanic.

Depends, GAME_PARAMS are appended on start from the dedicated server, usually you don't need anything in there, this is just if you have some weird mod or want to add a start parameter for whatever reason. Validate installation is basically the same as if you validate the game files on Steam (please never set this to true without a good reason because this will slow the start process from the container because it checks the game files if set to true on every container start). Explained WS_CONTENT above, if you don't need it, let it empty.

Yes. Yes.

I hope you've seen the Variable WS_CONTENT in the template, I can tell for sure that it's working because a buddy has also a server running with some mods on it. Please keep in mind that if the container starts to loop and doesn't starts properly one of the mods is not working properly.

I really don't know what causes that issue because I barely can't reproduce it and I'm pretty much clueless what it could be since Unraid runs from RAM and the package is also installed on boot, so this basically means everything is installed fresh on each reboot. I can only imagine that something in Docker prevents it from running properly because that's the only place in the chain where something is stored across reboots. Anyways, glad that everything is now working for you again!

There seems to be something wrong with Docker on your system. Are you sure you have enough space on the drive and also in you Docker image? Please post your Diagnostics.

Bad parameter is usually caused when the nvidia runtime isn‘t installed properly. Do you have any custom script installed that messes with the daemon.json file? Other versions from the driver also doesn‘t work as you‘ve wrote above? What did you change to fix the fan issues that you where having? Is there maybe a setting that you‘ve changed that could affect the Nvidia Driver? This happened once to me but a force update from the container fixed this issue for me back then on my test server. Back then I tried also to downgrade to a previous version from Unraid and upgraded again but I couldn‘t reproduce it.