May 19May 19 Hi everyone,I am experiencing an issue where multiple, unrelated Docker containers (Jellyfin, Radarr, etc.) are randomly crashing at different times on my Unraid server. The container logs consistently show Exit 139.In Jellyfin, this often causes the container to drop into an (unhealthy) state due to websocket timeouts and video stream packet corruption right before the crash.My Hardware Specs:CPU: Intel Xeon E5-2697A v4Motherboard: HUANANZHI X99-F8D PLUSMemory: 64GB DDR4 ECC Server RAMCache Pool: 2x NVMe SSDs in a ZFS Mirror (where appdata is hosted)What I Have Tested So Far:Memtest86+: Since Exit 139 is a Segmentation Fault (pointing to memory access issues), I ran Memtest86+ for nearly 8 hours (completed 1 full pass) and it returned 0 errors. The physical RAM sectors appear to be fine.ZFS Status: The pool shows as ONLINE, though I did find a corrupt file/inode (????????? permissions) inside Radarr's appdata directory right around the time these crashes started happening.System Boot Issue: After forcing a reboot to clear the app crashes, my motherboard temporarily hung at Debug LED Code 92 (PCI Bus Initialization).The Dilemma:Since Memtest passed completely, what else could be causing random Exit 139 segfaults across multiple containers?Could it be silent data corruption caused by memory timing instability on this Chinese X99 motherboard under heavy OS workloads (even if Memtest passes)? Or is it more likely that a failing NVMe cache drive/controller is causing file system corruption that triggers these segfaults when Docker tries to read the corrupted data?Any insights or troubleshooting steps on how to isolate this would be greatly appreciated. Thanks! tick-unraid-diagnostics-20260430-0921.zip
May 19May 19 Community Expert Try recreating the docker folder as a docker image. Many times I've seen strange errors with docker foldershttps://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-fileThen:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applicationsAlso see below if you have any custom docker networks:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks
May 19May 19 Author 7 minutes ago, JorgeB said:Try recreating the docker folder as a docker image. Many times I've seen strange errors with docker foldershttps://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-fileThen:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applicationsAlso see below if you have any custom docker networks:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networksThank you so much! I'll definitely give this a try as soon as my parity check finishes.Quick follow-up question: Since I will be switching to a Docker image file and I'm running around 5-6 containers (including Jellyfin and the full *Arr stack), what would be the recommended size for the docker.img? Can I just set it to a very large size (like 50GB-100GB or more) just to be safe, or does a larger size negatively impact performance?
May 19May 19 Community Expert I would think that 50 GB would be more than enough, and you can expand it later if needed.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.