Issues after Unraid update [Solved]

[BurningPhoenix]

I will start by saying that I am not sure that the following issues are directly related to updating the unraid OS, but these did start happening after the update. Onto the topic.

 

Server was running fine for over a year with no issues. Updated because i was always getting the "Version unavailable" under the docker screen and it was getting annoying to force update the dockers to figure out if they are up to date.

Updated my unraid OS from 6.8.3 to 6.9.2.

Worked fine for about a day or 2, then everything came to a halt due to "rootfs" reaching 100% and taking almost all of my ram.

Attempted to download diagnostics from server, would not download. GUI was now functioning properly.

Restarted the server.

Worked fine for 6 days, then got the same issue with rootfs. Attempted to download Diagnostics, would not download. GUI not working right again.

restarted server again.

Ark Server Docker will not start now, but it started just fine yesterday.

attempted downgrading from 6.9.2 to 6.8.3.

Ark docker will not start. (Error in start up log is the following: Signal 11 caught /opt/scripts/start-server.sh: line 71: 61 Segmentation fault ./ShooterGameServer ${MAP}?listen?SessionName=${SERVER_NAME}?ServerPassword=${SRV_PWD}?ServerAdminPassword=${SRV_ADMIN_PWD}${GAME_PARAMS} ${GAME_PARAMS_EXTRA}  

and

Loading Steam API...Warning: failed to init SDL thread priority manager: SDL not found)

have checked the settings for the dockers and nothing appears to be amiss, but i could have missed something.

 

System Specs

Asus SAbertooth 990fx R2.0

AMD FX6300

24GB DDR3 Ram

 

Dockers Installed:

PlexMediaServer

ArkSurvivalEvolved

Mineos-node (Was stopped when issues happened)

binhex-preclear (Was stopped when issues happened)

 

I can submit more information if asked.

Thank you in advance for the assistance.

Edited September 4, 2021 by BurningPhoenix
Changed title

[trurl]

Get diagnostics even if it is after reboot since it can tell us useful information about your configuration.

 

Setup syslog server so you can get us syslog later if things require reboot.

https://wiki.unraid.net/Manual/Troubleshooting#Persistent_Logs_.28Syslog_server.29

 

[BurningPhoenix]

I have enabled the Syslog server according to that page trurl linked. I am also including the latest diagnostics that i downloaded an hour and a half ago.

gryphon-diagnostics-20210831-1839.zip

[trurl]

You don't seem to have a cache currently. Is that correct?

 

If you have any docker host paths specifying cache, that path would be in rootfs since you don't have anything mounted there.

[BurningPhoenix]

It is correct that i do not have any cache drives currently. They are next on my list of upgrades for the system.

 

As for dockers paths specifying cache, i don't think i have any that are pointing to the cache. All of the options appear to be pointing to

/mnt/user/appdata/plex

/mnt/user/appdata/steamcmd

/mnt/user

/mnt/disk1/appdata/ark-se

 

the Mineos is pointing to /mnt/cache/minecraft, but it was stopped when the issues happened.

[trurl]

2 minutes ago, BurningPhoenix said:

/mnt/cache/minecraft

As mentioned, that is a path in rootfs since there is no cache mounted.

 

Make sure you check all the host paths. Turn on Advanced View on the Docker page and click the down arrow of each of the Volume Mappings listings to expand them.

[BurningPhoenix]

I have already directed that one to a disk location. Including image. wont know for a couple days if the rootfs issue is solved.

Still getting the issue with the ark docker not loading.

Log for ARKSurvivalEvolved.txt

[trurl]

13 minutes ago, BurningPhoenix said:

Still getting the issue with the ark docker not loading.

I don't use that, maybe ask on its thread. You can go directly to the correct support thread for any of your dockers by clicking on its icon and selecting Support.