-
-
[Support] ich777 - Gameserver Dockers
I am getting the error "cant find executable, putting container to sleep" here is my output to the commands above:
-
[Support] ich777 - Gameserver Dockers
I added "-nosteam -No-useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS" to the launch options in Steam but no success logging into my orginal character. Is this the correct paste location you were referring to in the text above?
-
[Support] ich777 - Gameserver Dockers
After updating my Palworld docker today my save data is gone. When logging into the server it appears to be a fresh start. When exploring the folder: appdata\palword\Pal\Saved\SaveGames\0\EC378850F2E843729CC75CB4CE85B241\Players It looks like there are 4 player saves which is the number of users I had on the sever before the update. I tried changing /mnt/cache/appdata/palworld to /mnt/user/appdata/palword and replacing the palword folder contents with old ones but that also did not change anythinig. This is the beginning of my log. /serverdata/steamcmd/steamcmd.sh: line 39: 84 Segmentation fault $DEBUGGER "$STEAMEXE" "$@" [S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK. CAppInfoCacheReadFromDiskThread took 5 milliseconds to initialize Setting breakpad minidump AppID = 2394010 [S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded. [S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded. [S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded. [S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.
-
Some or all files unprotected after trying new config and running parity check
Hello, I am experiencing issues with my Unraid setup, specifically concerning my files being reported as unprotected. Based on my research of past posts, it seems this problem might be related to how I initially assigned my cache drives and later decided to change their location. Ideally, I would like to completely remove Disk 4 and Disk 5 from my array and utilize both devices as part of the Nvme_cache_pool. I attempted to follow the steps outlined in a previous post, which involved creating a new configuration, removing Disk 4 from the array, and setting it up as a new cache pool. After performing a parity check, I hoped it would remove it from the array and establish it as its own working cache drive. However, the drive is now reported as "Unmountable: Unsupported or no file system," and it's showing as "Not installed" with contents emulated in the array. My files are now showing as unprotected. I will be posting my diagnostics file, and any assistance would be greatly appreciated. I'm aware there might be several issues with my setup, so please feel free to offer suggestions. Thank you! porkchop-diagnostics-20240127-0507.zip
CatDad49421
Members
-
Joined
-
Last visited