tower-diagnostics-20260702-1452.zip

In the syslog.txt file it states that the server ran out of memory so it killed shfs.

Jul  2 14:45:57 Tower kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=shfs,pid=14909,uid=0
Jul  2 14:45:57 Tower kernel: Out of memory: Killed process 14909 (shfs) total-vm:1371552kB, anon-rss:958604kB, file-rss:60kB, shmem-rss:1464kB, UID:0 pgtables:2036kB oom_score_adj:0

Does unraid not restart this process automatically?

If not, should it not since it is critical to the base functionality of Unraid?

The main reason for the high ram usage I suspect is my two new ZFS drives I added to the array. I thought that 48 GB of ram for 28 TB of ZFS would have been enough, but I guess not.

Other than that, can anyone figure out what was the other source of high ram usage before the crash based off the diagnostic?

Unlikely to be the ZFS drives - more likely a docker contaoiner.

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

shfs was just the victim; you need to figure out what caused the OOM, a container like mentioned is a good suspect.

12 hours ago, Gray J said:

The main reason for the high ram usage I suspect is my two new ZFS drives I added to the array. I thought that 48 GB of ram for 28 TB of ZFS would have been enough, but I guess not.

ZFS doesn't "need" the RAM, it just uses it if some is available and frees it when something else needs it.