September 28, 2025Sep 28 I've run into this problem now several times and I'm going to presume it's an issue with my USB drive itself that needs to be replaced but want to check here with the gurus to see if there is something else I should test first. Essentially every 3 days or so, I notice my server GUI goes down. The docker containers etc keep working. I can usually go into CLI and powerdown but not always. The system boots up fine afterwards but if it's an unclean shutdown, obviously end up having to do a parity check. Finally got my syslog server setup and you can see the attached log files. On this most recent issue, I couldn't run powerdown (said command not found) and tried a couple of other shutdown commands which also didn't work, forcing a hard reboot/unclean shutdown. I think the relevant part of the logs are below but the entire log file is also included. Where it seems my usb device disconnects, there are a ton of SquashFS errors, then the usb reconnects but it just is error after error after error once it comes back. For reference I have a Sandisk Mobilemate USB3.0 microsd reader that is no more than 2-3 months old....... When I check the drive on my windows machine it doesn't find any errors. Should I be replacing my card reader/sd card entirely here? Any other suggestions would be greatly appreciated. Sep 27 04:40:25 Unraid-MD kernel: eth0: renamed from veth041fd34Sep 27 04:40:25 Unraid-MD kernel: docker0: port 15(vetha90ed02) entered blocking stateSep 27 04:40:25 Unraid-MD kernel: docker0: port 15(vetha90ed02) entered forwarding stateSep 27 04:40:26 Unraid-MD kernel: usb 4-1: USB disconnect, device number 2Sep 27 04:40:26 Unraid-MD kernel: xhci_hcd 0000:80:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.Sep 27 04:40:26 Unraid-MD kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0sSep 27 04:40:26 Unraid-MD kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 18 24 20 00 00 08 00Sep 27 04:40:26 Unraid-MD kernel: I/O error, dev sda, sector 1582112 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0Sep 27 04:40:26 Unraid-MD kernel: device offline error, dev sda, sector 1582112 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0Sep 27 04:40:26 Unraid-MD kernel: I/O error, dev loop1, sector 344256 op 0x0:(READ) flags 0x800 phys_seg 5 prio class 0Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa818580: -5Sep 27 04:40:26 Unraid-MD kernel: device offline error, dev sda, sector 1582112 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0Sep 27 04:40:26 Unraid-MD kernel: I/O error, dev loop1, sector 344256 op 0x0:(READ) flags 0x800 phys_seg 5 prio class 0Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa818580: -5Sep 27 04:40:26 Unraid-MD kernel: device offline error, dev sda, sector 1582112 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0Sep 27 04:40:26 Unraid-MD kernel: I/O error, dev loop1, sector 344256 op 0x0:(READ) flags 0x800 phys_seg 5 prio class 0Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa818580: -5Sep 27 04:40:26 Unraid-MD kernel: device offline error, dev sda, sector 1585312 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0Sep 27 04:40:26 Unraid-MD kernel: device offline error, dev sda, sector 1585312 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0Sep 27 04:40:26 Unraid-MD kernel: I/O error, dev loop1, sector 347456 op 0x0:(READ) flags 0x800 phys_seg 10 prio class 0Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa9a8308: -5Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read fragment cache entry [a9a8308]Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read fragment cache entry [a9a8308]Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read page, block a9a8308, size 8d64Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa818580: -5Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa818580: -5Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa818580: -5Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read fragment cache entry [a9a8308]Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read page, block a9a8308, size 8d64Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0x1e5bc6ec: -5Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read fragment cache entry [1e5bc6ec]Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read fragment cache entry [1e5bc6ec]Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read page, block 1e5bc6ec, size 4d14Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read fragment cache entry [a9a8308]Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Unable to read page, block a9a8308, size 8d64.......Sep 27 04:40:26 Unraid-MD kernel: usb 4-1: new SuperSpeed USB device number 3 using xhci_hcdSep 27 04:40:26 Unraid-MD kernel: usb-storage 4-1:1.0: USB Mass Storage device detectedSep 27 04:40:26 Unraid-MD kernel: scsi host10: usb-storage 4-1:1.0Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa7edcfc: -5Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa7f2314: -5Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa7f2314: -5Sep 27 04:40:26 Unraid-MD kernel: SQUASHFS error: Failed to read block 0xa7f2314: -5Sep 27 04:40:27 Unraid-MD kernel: scsi 10:0:0:0: Direct-Access SanDisk SDDR-B531 2920 PQ: 0 ANSI: 6Sep 27 04:40:27 Unraid-MD kernel: sd 10:0:0:0: Attached scsi generic sg0 type 0Sep 27 04:40:27 Unraid-MD kernel: veth11dfeb8: renamed from eth0Sep 27 04:40:27 Unraid-MD kernel: docker0: port 16(vethe2c4938) entered disabled stateSep 27 04:40:27 Unraid-MD kernel: docker0: port 16(vethe2c4938) entered disabled stateSep 27 04:40:27 Unraid-MD kernel: vethe2c4938 (unregistering): left allmulticast modeSep 27 04:40:27 Unraid-MD kernel: vethe2c4938 (unregistering): left promiscuous mode syslog-192.168.1.142.log
September 28, 2025Sep 28 Community Expert Solution Flash dropped offline. You try a different USB port first; if the same thing happens, replace it.
October 13, 2025Oct 13 Author Thanks. Switched it to an internal USB2.0 direct connect with an adaptive and it’s been rock solid since.
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.