hectic-drug7389

Hello JorgeB, Okay will change out the flash drive. I've already run mem test for 3 passes at this point. While that's not conclusive... In my experience it gives some confidence that ram (and everything reading/writing to it) should be okay. In the past when I've had ram issues that test has failed very quickly.

Hello MrGrey, It's difficult to determine what exact contair is causing the problem (assuming its not a hardware issue or something). I've went to bed and woke up and the engine crashed. I just suspect is qbittorrent because it happened today when I was downloading a fair bit of data. What different containers do you use? Also what do you Mean by this?

So I've been experiencing this issue every other day now (usually when I'm downloading something via qbittorrent). The docker engine crashes during a download. Some of my containers continue to work after but others experience issues as a result. Every time I've encountered this issue, a reboot fixes the problem but its still annoying to have to do every other day. I've run diagnostics after the crash and will post below. From looking at the docker logs, the primary exception that's occurring is a signal SIGBUS. Which honestly makes me think this is a very obscure software issue, because that error typically means something is trying to access an address that flat out doesn't exist. Has anyone seen something similar to this before? The containers I'm using are the following: lscr.io/linuxserver/overseerr latest 3759456de73a 2 days ago 696MB qmcgaw/gluetun latest 6245640ddc88 2 days ago 43.5MB lscr.io/linuxserver/prowlarr latest 472700fa05fa 3 days ago 174MB lscr.io/linuxserver/plex latest 31f912e2a484 4 days ago 340MB lscr.io/linuxserver/radarr latest c55fd4a1b11f 5 days ago 196MB lscr.io/linuxserver/sonarr latest 810f09617a2a 7 days ago 300MB lscr.io/linuxserver/qbittorrent 4.5.5 ac570e5f1f88 12 days ago 204MB jlesage/nginx-proxy-manager latest 9a053fdf2c51 3 months ago 183MB What are your guys thoughts? I've attached the diagnostics. So far two things stick out to me: Docker Log: [8:24 PM] fatal error: unexpected signal during runtime execution [signal SIGBUS: bus error code=0x2 addr=0x1c9dabc pc=0x454a9a] runtime stack: runtime.throw({0x1bbc3c1?, 0x4590b0?}) /usr/local/go/src/runtime/panic.go:1047 +0x5f fp=0x152782df59b0 sp=0x152782df5980 pc=0x439bbf runtime.sigpanic() /usr/local/go/src/runtime/signal_unix.go:819 +0x369 fp=0x152782df5a00 sp=0x152782df59b0 pc=0x4504c9 runtime.getStackMap(0x152782df5e60, 0xb176e?, 0x70?) /usr/local/go/src/runtime/stack.go:1288 +0x13a fp=0x152782df5ac8 sp=0x152782df5a00 pc=0x454a9a runtime.scanframeworker(0x152782df5e60, 0x152782df5f48, 0x1?) /usr/local/go/src/runtime/mgcmark.go:967 +0x7e fp=0x152782df5b30 sp=0x152782df5ac8 pc=0x42189e runtime.scanstack.func1(0x2f53580?, 0x33c8e40?) /usr/local/go/src/runtime/mgcmark.go:801 +0x25 fp=0x152782df5b58 sp=0x152782df5b30 pc=0x4217e5 runtime.gentraceback(0x0?, 0x0?, 0x0?, 0x0?, 0x0, 0x0, 0x7fffffff, 0x152782df60a8, 0x0?, 0x0) /usr/local/go/src/runtime/traceback.go:345 +0xd0d fp=0x152782df5ec8 sp=0x152782df5b58 pc=0x4603cd runtime.scanstack(0xc0009c76c0, 0xc000071c40) /usr/local/go/src/runtime/mgcmark.go:804 +0x1da fp=0x152782df60d0 sp=0x152782df5ec8 pc=0x42125a runtime.markroot.func1() /usr/local/go/src/runtime/mgcmark.go:240 +0xc5 fp=0x152782df6120 sp=0x152782df60d0 pc=0x420085 runtime.markroot(0xc000071c40, 0x136, 0x1) /usr/local/go/src/runtime/mgcmark.go:213 +0x1a5 fp=0x152782df61c0 sp=0x152782df6120 pc=0x41fd25 runtime.gcDrain(0xc000071c40, 0x7) /usr/local/go/src/runtime/mgcmark.go:1069 +0x39f fp=0x152782df6220 sp=0x152782df61c0 pc=0x421dff runtime.gcBgMarkWorker.func2() /usr/local/go/src/runtime/mgc.go:1327 +0x6d fp=0x152782df6270 sp=0x152782df6220 pc=0x41e2ed runtime.systemstack() /usr/local/go/src/runtime/asm_amd64.s:492 +0x46 fp=0x152782df6278 sp=0x152782df6270 pc=0x46be66 [8:25 PM] System Log: Nov 3 19:56:10 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Nov 3 19:56:10 Tower kernel: SQUASHFS error: Failed to read block 0x299f1c8: -5 tower-diagnostics-20231103-2026.zip

So, are those files supposed to be on the cache by default? I've tried recreating the docker.img before but that didn't seem to fix the issue.

That Is correct.... I believe at one point in time there wasn't a cache drive in my box when I started Unraid. Would that explain my issue you think?

Hello trurl, No I don't have any VMs setup. The box is primarily used for plex and torrenting. May I ask your thought process here? I'm new to unraid and to be honest I don't believe I've ever touched the system share.

So I've been experiencing this issue every other day now (usually when I'm downloading something via qbittorrent). The docker engine crashes during a download. Some of my containers continue to work after but others experience issues as a result. Every time I've encountered this issue, a reboot fixes the problem but its still annoying to have to do every other day. I've run diagnostics after the crash and will post below. I'm suspecting at this point this is a hardware issue, I'm just not exactly sure where. I've run memtest86 at this point for 3 full passed and there were no issues there. My only other thought would be my nvme cach drive. What are your guys thoughts? I've attached the diagnostics. So far two things stick out to me: Docker Log: [8:24 PM] fatal error: unexpected signal during runtime execution [signal SIGBUS: bus error code=0x2 addr=0x1c9dabc pc=0x454a9a] runtime stack: runtime.throw({0x1bbc3c1?, 0x4590b0?}) /usr/local/go/src/runtime/panic.go:1047 +0x5f fp=0x152782df59b0 sp=0x152782df5980 pc=0x439bbf runtime.sigpanic() /usr/local/go/src/runtime/signal_unix.go:819 +0x369 fp=0x152782df5a00 sp=0x152782df59b0 pc=0x4504c9 runtime.getStackMap(0x152782df5e60, 0xb176e?, 0x70?) /usr/local/go/src/runtime/stack.go:1288 +0x13a fp=0x152782df5ac8 sp=0x152782df5a00 pc=0x454a9a runtime.scanframeworker(0x152782df5e60, 0x152782df5f48, 0x1?) /usr/local/go/src/runtime/mgcmark.go:967 +0x7e fp=0x152782df5b30 sp=0x152782df5ac8 pc=0x42189e runtime.scanstack.func1(0x2f53580?, 0x33c8e40?) /usr/local/go/src/runtime/mgcmark.go:801 +0x25 fp=0x152782df5b58 sp=0x152782df5b30 pc=0x4217e5 runtime.gentraceback(0x0?, 0x0?, 0x0?, 0x0?, 0x0, 0x0, 0x7fffffff, 0x152782df60a8, 0x0?, 0x0) /usr/local/go/src/runtime/traceback.go:345 +0xd0d fp=0x152782df5ec8 sp=0x152782df5b58 pc=0x4603cd runtime.scanstack(0xc0009c76c0, 0xc000071c40) /usr/local/go/src/runtime/mgcmark.go:804 +0x1da fp=0x152782df60d0 sp=0x152782df5ec8 pc=0x42125a runtime.markroot.func1() /usr/local/go/src/runtime/mgcmark.go:240 +0xc5 fp=0x152782df6120 sp=0x152782df60d0 pc=0x420085 runtime.markroot(0xc000071c40, 0x136, 0x1) /usr/local/go/src/runtime/mgcmark.go:213 +0x1a5 fp=0x152782df61c0 sp=0x152782df6120 pc=0x41fd25 runtime.gcDrain(0xc000071c40, 0x7) /usr/local/go/src/runtime/mgcmark.go:1069 +0x39f fp=0x152782df6220 sp=0x152782df61c0 pc=0x421dff runtime.gcBgMarkWorker.func2() /usr/local/go/src/runtime/mgc.go:1327 +0x6d fp=0x152782df6270 sp=0x152782df6220 pc=0x41e2ed runtime.systemstack() /usr/local/go/src/runtime/asm_amd64.s:492 +0x46 fp=0x152782df6278 sp=0x152782df6270 pc=0x46be66 [8:25 PM] System Log: Nov 3 19:56:10 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Nov 3 19:56:10 Tower kernel: SQUASHFS error: Failed to read block 0x299f1c8: -5 tower-diagnostics-20231103-2026.zip