April 10, 20251 yr For several days now, when I log into Unraid, the docker tile is missing in the dashboard, and on the docker tab it says "Docker Service failed to start" with no dockers listed. BUT the dockers are in fact running perfectly fine. For the ones that I remember the port numbers for, I can go to their web guis just fine. Rebooting causes an unclean shutdown, and a parity check on boot, but all of the dockers come up cleanly. This only happens overnight. I dunno if its an accumulation/leak thing, or if something is scheduling overnight that triggers it. I have just enabled the log server, so I will post additional logs tomorrow. though its possible the interesting stuff is in the attached diagnostics. tower-diagnostics-20250410-0829.zip
April 10, 20251 yr Community Expert Solution Apr 9 22:07:01 Tower kernel: critical medium error, dev sda, sector 1841128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Apr 9 22:07:01 Tower kernel: I/O error, dev loop0, sector 79608 op 0x0:(READ) flags 0x800 phys_seg 11 prio class 2 Apr 9 22:07:01 Tower kernel: SQUASHFS error: Failed to read block 0x26dfaf4: -5 Apr 9 22:09:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 9 22:09:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Apr 9 22:09:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Apr 9 22:09:54 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 1c 17 e8 00 00 08 00 Apr 9 22:09:54 Tower kernel: critical medium error, dev sda, sector 1841128 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Apr 9 22:09:54 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 9 22:09:54 Tower kernel: SQUASHFS error: Failed to read block 0x26dfaf4: -5 Apr 9 22:09:54 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 9 22:09:54 Tower kernel: SQUASHFS error: Failed to read block 0x26dfaf4: -5 Flash drive issues, replace it.
April 10, 20251 yr Author Hrm, my "only overnight" commentis wrong, it just happened again. This is visible in the log : Quote Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5 Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5 Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5 Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5 Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5 Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5 Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5 Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5 Apr 10 09:09:31 Tower kernel: SQUASHFS error: xz decompression failed, data probably corrupt Apr 10 09:09:31 Tower kernel: SQUASHFS error: Failed to read block 0x26e9574: -5
April 10, 20251 yr Author 4 hours ago, JorgeB said: Flash drive issues, replace it. Drive replaced, so far painless so fingers crossed!
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.