You are not logged in.

#1 2020-04-19 11:11:48

corey.taylor
Member
From: Dresden
Registered: 2020-04-14
Posts: 20
Website

usb 1-1.4: device descriptor read error/64, error -110, etc.

After absent-mindedly ripping out the cable of a USB HDD when I had ejected it, the drive was all of a sudden totally unreachable. From dmesg/syslog:

 - [ 3441.404743] usb 1-1.4: new high-speed USB device number 16 using ehci-pci
 - [ 3456.483721] usb 1-1.4: device descriptor read/64, error -110
 - [ 3471.666738] usb 1-1.4: device descriptor read/64, error -110
 - [ 3471.842942] usb 1-1.4: new high-speed USB device number 17 using ehci-pci
 - [ 3476.865238] usb 1-1.4: device descriptor read/8, error -110
 - [ 3481.987716] usb 1-1.4: device descriptor read/8, error -110
 - [ 3482.163481] usb 1-1.4: new high-speed USB device number 18 using ehci-pci
 - [ 3487.186053] usb 1-1.4: device descriptor read/8, error -110
 - [ 3492.308390] usb 1-1.4: device descriptor read/8, error -110
[...]

Couldn't mount it, see it in the file manager or lsblk/lsusb, etc. Googling turned up plenty of commands that didn't work and people saying the drive is dead, etc.

Long story short, nope. The solution? Just unplug all USB devices, wait a bit and reboot. Sure enough, the drive is back up and running no sweat. I did find it a bit strange that the USB over-current protection (i.e. shutting down the hub) was triggered not by a device sucking a lot of juice but by removing it. Apparently this can even be tripped when the hub has external power. But I guess, an unexpected spike is an unexpected spike regardless the cause. I'm sure people with more detailed understanding of firmware stuff will have a simple explanation.

I guess it's just worth noting for a few reasons. Mostly, for BL users not to panic about lost data as the fix is simple. A forum search didn't turn this message up and it's the first time I've seen this problem, despite the post above being from 2014 and quite a few being even older.

That said, the fact that there was seemingly no solution or diagnostics other than ripping the thing out worries me. I'm no kernel nerd so maybe this is a simple thing to those who know Linux back-to-front. But I'm curious, has anyone else had this sort of error before? And was there a way to diagnose it within Linux? I didn't see anything in the logs suggesting the hub itself had shut down, usb-specific commands suggested things were running. And maybe for the BL maintainers who really know Linux, is there any fix on the horizon or changes to how USB devices?

Cheers all.

Last edited by corey.taylor (2020-04-19 11:22:31)

Offline

#2 2020-04-19 22:14:21

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 407

Re: usb 1-1.4: device descriptor read error/64, error -110, etc.

Cuite common on Windows PC too. Mouse or digital dictations and so on suddenly dies. Instead of unplugg all usb-devices, shutdown the pc and unplug power for 5 min.


// Regards rbh

Offline

Board footer

Powered by FluxBB