Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SOLVED: Crash after connecting an empty unassigned USB-drive

Featured Replies

Something very weird just happened.

I connected an empty USB-drive (at least, it's supposed to be empty, I erased it last month) and when I came back to my PC upstairs, nothing was responding. I could ping it, but no containers were reachable, the webUI was not reachable, SSH wasn't reachable,... I could only ping its IP, but no containers custom IPs.

After searching for half an hour, I gave up and power cycled the server. After booting back up, everything seemed fine.

The stored syslog shows a whole lot of read errors from the moment I connected the drive. The complete file is attached.

1 20:25:32 Willow kernel: usb 5-2: USB disconnect, device number 2

Jun 1 20:25:33 Willow kernel: sd 6:0:0:0: [sdf] Synchronizing SCSI cache

Jun 1 20:25:33 Willow kernel: sd 6:0:0:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK

Jun 1 20:25:33 Willow kernel: I/O error, dev loop0, sector 1202912 op 0x0:(READ) flags 0x800 phys_seg 8 prio class 2

Jun 1 20:25:33 Willow kernel: SQUASHFS error: Failed to read block 0x24b5c56b: -5

Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read fragment cache entry [24b5c56b]

Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read fragment cache entry [24b5c56b]

Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read page, block 24b5c56b, size 7b49

Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read fragment cache entry [24b5c56b]

Jun 1 20:25:33 Willow kernel: SQUASHFS error: Unable to read page, block 24b5c56b, size 7b49

Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30688) failed

Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30689) failed

Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30690) failed

Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30691) failed

Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30692) failed

Jun 1 20:25:33 Willow kernel: FAT-fs (sdf1): Directory bread(block 30693) failed

What could this be? Is that drive at fault, or did I bump something while connecting it at the back of the server?

Just trying to understand what happened to avoid it in the future. As said, the server is running fine now it's rebooted with the drive disconnected.

crash.txt

Edited by bartdejonckheere

Solved by JorgeB

  • Community Expert

If sdf is the flash drive, it got disconnected, or there are issues with it.

  • Author

Looks like that was indeed my drive, since sdf normally isn't used. But why does that bring my server down if it's just an unassigned device?

  • Community Expert
  • Solution

The problem was the flash drive dropping offline

11 hours ago, bartdejonckheere said:

1 20:25:32 Willow kernel: usb 5-2: USB disconnect, device number 2

This should not happen when you just use another USB port

  • Author
Just now, JorgeB said:

The problem was the flash drive dropping offline

This should not happen when you just use another USB port

Oooowh, thanks a lot! Yes, I put the USB-drive in the slot next to the flash, I might have bumped it...

I'm going to put in a USB-hub, so I can connect to it from the front of my server and don't need to touch anything in the back.

And I'm also going to move to internal boot anyway, sooner or later... 😅

  • bartdejonckheere changed the title to SOLVED: Crash after connecting an empty unassigned USB-drive

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.