RoyalJackV

Were you able to find a solution? I began encountering the same issue this morning. UPDATE: I was able to resolve by changing my NVIDIA driver from "latest: v590.44.01" back to "Production Branch: v580.105.08" and rebooting the server.

That wasn't me but in testing with friends I had the same result.

I agree with ich777. My rule matches the one they shared. Also I do not check the LAN option. While on LAN I connect with my local IP. My friends use my external IP.

It is a SSD(pny cs900 500gb) connected via SATA cable. Intel® Xeon® CPU E5-2620 v3 @ 2.40GHz. I have a similar concern with TRIM. My CACHE also gets a lot of writes and then transfers data to my Synology NAS. I've never gone a period of time with TRIM disabled so I do not know what performance impacts I'll see.

My noob understanding is that btrfs no longer needs TRIM after a certain version of UnRaid so the TRIM command may not actually be doing anything to your btrfs drives. Is there an advantage to use one or the other (xfs vs btrfs)? @ich777 with TRIM disabled I did not hit the stuck main thread this morning. I've at least confirmed that it is something to do with TRIM. I still don't really understand why the TRIM impacts only this container. For now I'll leave TRIM turned off and see if I notice any performance problems after a few weeks. I am still having issues getting my world to display in the global list so I've been having to provide friends with my IP address since the game GUI doesn't allow you to enter a URL. I have the port forwarding and firewall rules set up in PFSENSE so I'm assuming I've missed something somewhere.

I'll be honest, I don't know how critical the TRIM function is in UnRaid. I've seen a lot of mixed interpretations on whether its actually needed or not. Perhaps I'll disable TRIM and see if the issue goes away completely or change the frequency to something less often.

@ich777 the stuck main thread did follow the SSD Trim to 8AM Central. my appdata is set to prefer cache, my cache is a single xfs SSD. My Valhiem docker doesn't run into this so its something unique between V-Rising and the scheduled TRIM. I'll continue to experiment but if you have any additional ideas I'd love to hear them. Thank you!

Thank you for the quick reply. My appdata is set to prefer Cache. This did help me though! My SSD TRIM is scheduled for 10AM daily and my cache is on an SSD. I am surprised the TRIM would cause a freeze though. I'll adjust the TRIM schedule to 8AM and see if that changes when things hang up.

Hello, first of all thank you so much for all of the amazing work on your various dockers! I've been running your unraid v-rising docker for a few weeks and it works perfectly outside of one weird issue I haven't been able to replicate on a friends unraid server. For some reason the server gets a stuck main thread every day at 10AM Central. The docker is still in a "started" state but we can't log in. When I check the logs for the v-rising docker it says something about a stuck primary thread. If I restart the docker it works fine until exactly 10am central the next day. Any thoughts? Stuck main thread detected. Last system started: ProjectM.ServerBootstrapSystem. Last system finished: ProjectM.ServerDebugSettingsSystem. Last subnode: PrefabGuid: 0 NodeIndex: 0. UnityEngine.Logger:Log(LogType, Object) UnityEngine.Debug:Log(Object) Unity.Entities.<>c__DisplayClass8_0:<Initialize>b__0(Object) System.Runtime.Serialization.DeserializationEventHandler:Invoke(Object) System.Threading.SendOrPostCallback:Invoke(Object) System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean) System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object) System.Runtime.Serialization.DeserializationEventHandler:Invoke(Object)