LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   usb hdd not found in /dev or with lsusb (http://www.linuxquestions.org/questions/slackware-14/usb-hdd-not-found-in-dev-or-with-lsusb-605869/)

/y0shi 12-10-2007 03:37 PM

usb hdd not found in /dev or with lsusb
 
Hey folks,

I bought a external hdd (usb 2.0 to 1.8'' IDE) with 20GB it was fat formatted and worked nicely (I checked it with dosfsck).

Than I decided to plug it into my ipod 3gen, so I repartitioned it and used dd to put the firmware on it. The ipod worked with that until the battery was empty well after that no more.

So I decided something went wrong with dd or so. I did put the drive back into the usb2ide case and was planing to repartition it again.

Well it is no longer detected?

lsusb shows nothing

there is no /dev/sdaX etc.

and in dmesg I found something like:

Code:

usb 2-1: new full speed USB device using uhci_hcd and address 12
usb 2-1: configuration #1 chosen from 1 choice
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 12
usb-storage: waiting for device to settle before scanning
usb 2-1: reset full speed USB device using uhci_hcd and address 12
usb 2-1: device descriptor read/64, error -110
usb 2-1: device descriptor read/64, error -110
usb 2-1: reset full speed USB device using uhci_hcd and address 12
usb 2-1: device descriptor read/64, error -110
usb 2-1: device descriptor read/64, error -110
usb 2-1: reset full speed USB device using uhci_hcd and address 12
usb 2-1: device not accepting address 12, error -110
usb 2-1: reset full speed USB device using uhci_hcd and address 12
usb 2-1: device not accepting address 12, error -110
usb 2-1: USB disconnect, address 12
scsi 5:0:0:0: scsi: Device offlined - not ready after error recovery
usb-storage: device scan complete
usb 2-1: new full speed USB device using uhci_hcd and address 13
usb 2-1: device descriptor read/64, error -110

this is an old thinkpad with usb 1

Does anyone know what happened? How can I get access to the harddrive?
Thanks for any help!

hitest 12-11-2007 07:59 AM

Did you edit /etc/group and add your regular user to plugdev?

evilDagmar 12-12-2007 02:22 AM

You could at least read what people post before you suggest a fix. That can't have anything to do with the fact that the device is flatly refusing to initialize on the USB port.

http://www.linux-usb.org/FAQ.html#ts6 is what the user needs to look at. Offhand, I'd say if it worked plugged into that laptop and port before, then it wasn't put back into the external case properly, or the case has died.

hitest 12-12-2007 08:56 AM

what do the following commands give you? Sometimes a USB device can be read in different ways on boot-up as I've discovered with my USB card reader for my Nikon digital camera.

#fdisk -l

#blkid

evilDagmar 12-12-2007 11:59 AM

Guys, as long as the last thing in the logs is stuff like:

Code:

usb 2-1: device not accepting address 12, error -110
usb 2-1: device descriptor read/64, error -110

...it's not going to show up under any of the tools you're trying to use. It might as well not be on the bus at all.

/y0shi 12-13-2007 05:31 AM

Hi thanks for your replays!

Was not available for a few days so ...

Quote:

Originally Posted by evilDagmar (Post 2988433)
...it's not going to show up under any of the tools you're trying to use.

Thats right it is not showing under any tools like fdisk -l blkid etc.

Also being in the plugdev group or not or running hald etc. does make no difference.

Quote:

Originally Posted by evilDagmar
Offhand, I'd say if it worked plugged into that laptop and port before, then it wasn't put back into the external case properly, or the case has died.

Thats also right it worked beforhand and now it does not. This 1.8'' disk fits only in one position into that case, so it's definitly pluged in right - I don't understand why the case should be dead, it worked open (nothing was dropped etc.).

I have to admit, I dont understand http://www.linux-usb.org/FAQ.html#ts6 to well, but a BIOS issue it can't be right? (I did not change the BIOS)
This external hdd is usb2 capable, but my thinkpad x30 is not, so it can't be that eather. (I tried two different cables)

This
Quote:

You may have some problem with your PCI setup that's preventing your USB host controller from getting hardware interrupts.
I don't understand

Code:

bash-3.1# cat /proc/interrupts
          CPU0     
  0:    373293    XT-PIC-XT        timer
  1:      5842    XT-PIC-XT        i8042
  2:          0    XT-PIC-XT        cascade
  6:          5    XT-PIC-XT        floppy
  7:          2    XT-PIC-XT        parport0
  8:          1    XT-PIC-XT        rtc
  9:      9786    XT-PIC-XT        acpi
 11:    209451    XT-PIC-XT        Intel 82801CA-ICH3, Intel 82801CA-ICH3 Modem, uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, yenta, yenta, ohci1394, eth0, i915@pci:0000:00:02.0
 12:        95    XT-PIC-XT        i8042
 14:      9772    XT-PIC-XT        ide0
NMI:          0
ERR:          0

Thanks anyway!

evilDagmar 12-13-2007 09:58 AM

Yeah, unfortunately it's definitely smelling like hardware failure. Find someone you know locally and test plugging it into their machine, or open the thing again and double-check that everything is plugged in exactly as it's supposed to. Something might not be plugged in all the way...

It can't be the interrupt issue mentioned, because well, it would really be saying that, specifically, in English, in the syslog if it were. UCHI is the right driver for a USB 1.1 chipset, and if it worked before on that same machine then we can also rule out that the drive enclosure is one of the rare ones that only do USB 2.0. That pretty much leaves you with it being a problem with the cable, or the enclosure, i.e., this is almost assuredly a hardware problem.

gregby 12-19-2007 05:41 PM

One more thing you could look at.

I was having the same problem myself, which led me to this thread. I too wrote it off as a hardware issue, and was in the process of changing disks in the enclosure when I noticed my own id10t error. I'd left the jumper on the drive that told it it was a master with slave attached. Removed that jumper and it all worked fine.

Can't guarantee that your problem is the same, but at least check that the drive knows that it's alone on the IDE bus.

Cheers
G


All times are GMT -5. The time now is 07:22 AM.