Docker Engine crashing

[hectic-drug7389]

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

[trurl]

Your system share has some files or folders on the array (disk1).

 

Do you have any VMs?

[hectic-drug7389]

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. 

[trurl]

Disable Docker and VM Manager in Settings.

Delete whatever is in system share on disk1

Delete and recreate docker.img

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

[trurl]

5 minutes ago, hectic-drug7389 said:

don't believe I've ever touched the system share

You probably enabled Docker or VM Manager without cache drive so they got created on the array

[hectic-drug7389]

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?

[trurl]

It would explain how system share has files on the array, which is not ideal and can be fixed as I explained. Possibly recreating docker.img will fix your actual problem.

[hectic-drug7389]

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.

[Squid]

Personally, I don't think this has anything to do with the docker image etc.  

 

This somewhat looks like memory issues.  You've got the usual false advertising memory sticks that are sold as 3200MT/s.  While you're not running them at the 3200 speed, but rather are running them at 2667, you should also try setting the BIOS to not run at any XMP profile and instead run the memory at the speed that you've paid for and not any falsely implied speed.  IE: Disable. the xmp profile and run them at the stick's actual speed of 2133. Everything else is an overclock and all overclocks introduce instability.

 

A memtest would also be a great idea from the boot menu.  If you're booting the system via UEFI you will need to temporarily switch to legacy boot (or setup a new flash drive via https://www.memtest86.com/

 

[Squid]

Also, your BIOS version is rather old, and one of the later versions of the BIOS does outright say "- Improve memory compatibility."