ezm

I found the problem is from the m.2 cache drives I connected over PCIE slot. One time I happened to write the cache to total full, and tried to fix it. Since the read error corrected message shows right after the server recovering from freeze, I think I might to run a full test on the m.2 drives to fix the issue.

Also noticed that when I transfer big files, like 3 episode of TV shows each as 7GB, the CPU 100% and server freeze can be triggered easily. I copy from a windows machine directly to array via SMB. What I did: scrub the docker img file and corrected some error. Stopped Sonarr as it looks like causing problem with a bad indexer setting. The trigger of this server stuck remains unknown. I did find some posts about enable C6 power saving on BIOS. I vaguely recall that I could change the power related setting in the BIOS but right now is hard for me to verify it due to my hardware placement. Other than this clue, I have no idea.

Thanks for your explanation! I just found out that the problem doesn't go away. The CPU 100% usage still happens randomly. The previous method I said is not helping. Struggling to debug this...

Hi guys, I just found an ancient post but the main idea is to change all the docker appdata folder path setting from /mnt/user/appdata to /mnt/cache/appdata, assuming you have a cache drive and want to store appdata on cache drive. I now think the issue is that CPU is constantly checking the file between these two path and moving them. Before the redundant moving is finished, the whole docker service is just paused. At least it seems to solve my problem for now. I will update if anything.

I am experiencing the same issue here. My server is all good for the previous couple of months. I haven't upgrade to 6.12 for stability concerns, still 6.11.5. Recently I added a `CA Mover Tuning` plugin to make use of cache drives. Then my server would randomly stuck, none of WebGUI, Docker, SMB function works. The CPU usage soars to close to 100% (there is a specific pattern that some threads of the CPU is 100% and a couple of threads are ~0%, but the whole system just freezes until about 5 minutes later) As I manually assigned specific threads to docker instances, I originally assume some of the docker instances messed up but when I check the usage of all the dockers, they all seem fine. One more thing to add is that sometimes the CPU usage is only 25%, but the pattern is 25% of the threads are 100% used while others are ~0%. But the whole system is still freezing in this case, which surprises me because it looks less like a lack of performance, but the system flow is stuck somewhere very close to Docker service. Then I use `top` command to check the CPU usage. The CPU usage is not reported in real-time when the stuck is happening. But right after the system goes back to normal, I noticed `shfs` & `dockerd` & `java` have the most CPU usage, and all of them seem to have connection with Docker. I tried disable Docker but no good. I thought this situation is just me but then I found this post. There is a high possibility that a lot of users are experiencing the same performance issue.