Hyp3z

Sorry if this has been covered already but i couldn't find anything on it. I have had the Valheim container running perfectly since it pretty much was available. Today i went and set ValheimPlus to true. Since then when me or mates try to join we get an "Incompatible version" error. Here is the logs for the container starting, also attached some pics of the errors. Thanks in advanced. - Hyp3z ---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK ---Update Server--- Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK Success! App '896660' already up to date. ---Prepare Server--- ---ValheimPlus enabled!--- ---ValheimPlus Version Check--- ---ValheimPlus v0.9.4 up-to-date--- ---Server ready--- ---Starting Backup daemon--- ---Start Server--- ---Update Check for Valheim enabled, running automatically every 60 minutes.--- [S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK. CAppInfoCacheReadFromDiskThread took 1 milliseconds to initialize CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread) RecordSteamInterfaceCreation (PID 77): SteamGameServer013 / RecordSteamInterfaceCreation (PID 77): SteamUtils009 / Setting breakpad minidump AppID = 892970 RecordSteamInterfaceCreation (PID 77): SteamGameServer013 / GameServer RecordSteamInterfaceCreation (PID 77): SteamUtils009 / Utils RecordSteamInterfaceCreation (PID 77): SteamNetworking006 / Networking RecordSteamInterfaceCreation (PID 77): SteamGameServerStats001 / GameServerStats RecordSteamInterfaceCreation (PID 77): STEAMHTTP_INTERFACE_VERSION003 / HTTP RecordSteamInterfaceCreation (PID 77): STEAMINVENTORY_INTERFACE_V003 / Inventory RecordSteamInterfaceCreation (PID 77): STEAMUGC_INTERFACE_VERSION014 / UGC RecordSteamInterfaceCreation (PID 77): STEAMAPPS_INTERFACE_VERSION008 / Apps [S_API FAIL] Tried to access Steam interface SteamNetworkingUtils003 before SteamAPI_Init succeeded. RecordSteamInterfaceCreation (PID 77): SteamNetworkingUtils003 / RecordSteamInterfaceCreation (PID 77): SteamNetworkingSockets008 /

I had an unassigned SSD that changed its dev name. I have changed my boot script to use UUID instead. Everything is now working as you can see below. Thanks for the help @JorgeB & @itimpi

Phase 1 - find and verify superblock... - block cache size set to 1477912 entries Phase 2 - using internal log - zero log... zero_log: head block 0 tail block 0 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 0 - agno = 7 - agno = 4 - agno = 2 - agno = 6 - agno = 5 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:837510) is ahead of log (1:2). Format log to cycle 4. XFS_REPAIR Summary Sun Jan 17 23:47:02 2021 Phase Start End Duration Phase 1: 01/17 23:46:29 01/17 23:46:29 Phase 2: 01/17 23:46:29 01/17 23:46:39 10 seconds Phase 3: 01/17 23:46:39 01/17 23:46:41 2 seconds Phase 4: 01/17 23:46:41 01/17 23:46:41 Phase 5: 01/17 23:46:41 01/17 23:46:41 Phase 6: 01/17 23:46:41 01/17 23:46:41 Phase 7: 01/17 23:46:41 01/17 23:46:41 Total run time: 12 seconds done

Hi @itimpi Yes I was trying to add disk2. I have removed it from the array.

Added a new disk to the array today and stopped the clear that unraid was doing. Now I'm getting Unmountable: not mounted Jan 17 17:19:59 MirinServer root: mount: /mnt/disk1: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error. Jan 17 17:19:59 MirinServer emhttpd: /mnt/disk1 mount error: not mounted I have done the below: - Put array into maintenance mode - xfs_repair -nv /dev/md1 - xfs_repair -vL /dev/md1 I didn't know what "Clear" was so I cancelled it. Not sure if this is what caused the above error or not. Any help would be appreciated. Thanks - Kyle mirinserver-syslog-20210117-0630.zip