ich777

You an do that over SMB, simply share the appdata directory and go to the palworld folder in there and there you will see a folder called Backups where all your backups are stored, you can then restore them in the Pal directory (please keep track of the folder structure and only replace move files when the container is actually stopped!).

Hope it is working for you after that change, if not and you experiencing the same error as above the savegame might be corrupt and there is not much I can do about that but you can always try to restore a backup <- but since it was configured wrong it could be that the Backups are also corrupt.

It is well enough to leave the game files path at /mnt/cache/... since some games have issues with the FUSE file path /mnt/user/... You can leave the SteamCMD path as is since it will work no matter to what you set it.

Yes: As you can see your primary storage is set to Cache and the Secondary to Array and most importantly your Mover action is set to Cache -> Array, this means that the Mover tries to move all files from the Cache to the Array that are not in use and that will cause issues. I recommend that you leave the appdata always on the Cache since it usually holds all your data for your containers and you want fast and snappy responses. If you now want to move the data from the Array back to the Cache, you now have to set Mover action to Array -> Cache and invoke the Mover afterwards (I recommend Stopping all containers so that the Mover is actually able to move all the files back to the Cache) and wait for it to finish. After that you can set the Secondary storage to None to ensure that the files will stay on the Cache and the Move is not invoked at all.

That's caused because a corrupt save game most likely because it was basically using two different paths and the mover was moving files that should belong on the cache. Have you yet checked to what your appdata share is set where the files should belong and if they are moved to the Array?

Please change the path in the Docker template for the game files to /mnt/user/appdata/... and see if it is working afterwards. Seems like the container even can't find the path for your data. Really not sure why it was working that long if the files where moved to the Array.

Does it work now for you? No worries at all, hard times currently for everyone... Good question, it all started because I was missing Game Servers on Unraid and I needed a dedicated server for CounterStrike: Source and that was basically where the journey began. Mostly I did them for fun and to kill a bit of spare time but nowadays with almost 200 containers in the CA App it is really hard to maintain them all. ...and no I don't benefit much and even haven't got barely time to play any games because of support requests.

Please issue the correct command again: ls -la ${SERVER_DIR}/Pal/Binaries/Linux/ Are you sure that you appdata share is set to stay on the Cache drive in the Share settings?

I can try that later today but you have to give me a few hours. Have you yet tried to connect via IP and connect with the LAN IP from your server in game?

Can you please share a screenshot from your Docker template within Unraid? Do you use /mnt/user/... or /mnt/cache/... in the template for the game files. If you are using /mnt/cache/... just make sure that the share stays on the cache and is not moved to the Array in the Share settings. Please open a container terminal (while the container is running) and execute: tail -n 10 /opt/scripts/start-server.sh ls -la ${SERVER_DIR}/Pal/Binaries/Linux/ and post the output here.

How did you update the container? Did you click force update on the container page: Did it pull a update from DockerHub? Everything is working over here:

No, should I? The description is good and all but it seems like that this script just installs the default hbbs and hbbr part from RustDesk and the API server on top. What is the main benefit? Is something wrong with RustDesk itself?

Thanks for the report. Please update the container itself and it will work again.

Then it's most likely a issue with the port forwarding, please double check the forwarded ports and also if the correct protocol is set. I would also recommend that you try it with the default settings and see if that is working properly (I would recommend if you try it with the default configuration that you at least change the server name). This is not an issue and nothing to worry about.

@Amane please create a bug report here: https://forums.unraid.net/bug-reports/stable-releases/ This is not the right place to report a bug.

Are you talking about ARK:Survival Evolved or ARK:Survival Ascended? Please note these are two different games and basically using a different Engine.

Just mark it as solved.

I had multiple people in this thread which had the same issue: Here is one who was able to solve it by upgrading the PSU: Here is one who never responded again but is seems to be fixed now (because I found a follow up Diagnostics from him and the card is properly recognized) : The next one is this here which I'm also not sure if it's fixed: However please keep in mind that Linux is a lot more sensitive to thermal issues or power delivery issues for example. I remember one user who had the GPU fall from the bus because of a thermal issue.

@KingHawk this is now solved in this post correct:

Can you please clarify that a bit more? According to the documentation (which is not very clear) you have to user ?Port=7779

Maybe they changed it again, I have already changed the description from the container so that it says to put the server token in the config.txt If you don't need VAC then don't enable it.

Die größte muss immer die Partiy sein. Ich vermute wir reden hier über das XFS Array, das kommt immer drauf an wie sie kaputt geht: Wenn sie ganz aus dem System fällt: Ja Wenn sie einen SMART fehler hat: Ja Wenn sie defekte Sektoren hat: Nur bei einem Parity Check Wenn sie Bitrot hat: Nein BTW, bitte keine Doppelposts!

Ich würde dir eher zu einem USB Stick raten. Such mal auf Amazon nach einem Transcend USB 2.0 zB. den hier. Bei einem SD Karten Reader läufst du immer gefahr das der keine gültig UUID hat und vergiss nicht die können auch kaputt gehen. BTW Bitte keine Doppelposts!

Sorry, I can't help here since the documentation here also says that you can enable VAC with: enableVAC on I think you have to set those values now in the config.txt (please be sure to do that also in the config file). EDIT: I just tried it on a fresh installation and it is working perfectly fine: Make sure to change these two lines: The file is located: .../theforest/config/config.txt <- please make sure to stop the container first and then edit the file.

Thanks. The first thing that I noticed is that your BIOS is out of date, make sure to update your BIOS. Please make also sure to disable C-States in the BIOS since these cause (at least on Linux) issues with Nvidia cards. I deleted the Diagnostics from above because there was something in the go file that didn't need to be public. BTW, I think that your Motherboard supports Resizable BAR support maybe it is named differently.