Mounting IDE drive via USB-IDE cable

[Mr. Creosote]

I found one or two threads on this topic that didn't provide a lot of help.  I'm new to Vector, coming from ZenWalk Linux.  I've got a Vantec SATA/IDE to USB adapter to pull some data off a couple of old drives. Drives are set to "Master".  I believe the drives are ext2 formatted but can't recall for sure.

I'm using VL 7.0

lsusb shows the device (Bus 005 Device 005 as below)

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 005: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 003 Device 002: ID 192f:0416 Avago Technologies, Pte.
Bus 003 Device 003: ID 045e:0750 Microsoft Corp. Wired Keyboard 600

However, dmesg | tail doesn't give me a device, rather it seems there is some connection problem or other with device descriptor read/64, error -71

[ 1270.871280] usb 5-2: SerialNumber: 922660404222
[ 1270.880524] scsi54 : usb-storage 5-2:1.0
[ 1271.988058] usb 5-2: reset full speed USB device number 53 using uhci_hcd
[ 1272.101042] usb 5-2: device descriptor read/64, error -71
[ 1272.465048] usb 5-2: reset full speed USB device number 53 using uhci_hcd
[ 1272.578060] usb 5-2: device descriptor read/64, error -71
[ 1272.939044] usb 5-2: reset full speed USB device number 53 using uhci_hcd
[ 1273.052046] usb 5-2: device descriptor read/64, error -71
[ 1273.406048] usb 5-2: reset full speed USB device number 53 using uhci_hcd
[ 1273.519053] usb 5-2: device descriptor read/64, error -71

I'm using fluxbox rather than xfce so I don't know if there is some automount process (HAL, vl-hot) that would run with that window system or not.

Any suggestions would be appreciated. 

-cam

[uelsk8s]

try this "in the terminal type: echo -1 >/sys/module/usbcore/parameters/autosuspend"
then reboot

[Mr. Creosote]

This looked promising however the last few lines suggest that the partition table on the drives can't be read.  Which is weird because they seemed to be working fine earlier today when I pulled them out.  Looks like I may have to try another method unless I'm missing something.

-dmesg-

[  129.282076] usb 5-2: New USB device found, idVendor=152d, idProduct=2338
[  129.282085] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[  129.282091] usb 5-2: Product: USB to ATA/ATAPI bridge
[  129.282097] usb 5-2: Manufacturer: JMicron
[  129.282101] usb 5-2: SerialNumber: 142690806022
[  129.291361] scsi6 : usb-storage 5-2:1.0
[  130.296138] scsi 6:0:0:0: Direct-Access     Maxtor 6 Y080L0                PQ: 0 ANSI: 2 CCS
[  130.296735] sd 6:0:0:0: Attached scsi generic sg1 type 0
[  130.301140] sd 6:0:0:0: [sdb] 160086528 512-byte logical blocks: (81.9 GB/76.3 GiB)
[  130.306117] sd 6:0:0:0: [sdb] Write Protect is off
[  130.306127] sd 6:0:0:0: [sdb] Mode Sense: 28 00 00 00
[  130.311126] sd 6:0:0:0: [sdb] No Caching mode page present
[  130.311135] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  130.326104] sd 6:0:0:0: [sdb] No Caching mode page present
[  130.326112] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  130.431051] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  130.545044] usb 5-2: device descriptor read/64, error -71
[  130.898046] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  131.165040] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  131.423046] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  131.723050] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  132.047046] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  132.563054] usb 5-2: device not accepting address 2, error -71
[  132.665047] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  132.858094] sd 6:0:0:0: [sdb] Unhandled error code
[  132.858102] sd 6:0:0:0: [sdb]  Result: hostbyte=0x07 driverbyte=0x00
[  132.858110] sd 6:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[  132.858132] end_request: I/O error, dev sdb, sector 0
[  132.858139] Buffer I/O error on device sdb, logical block 0
[  133.031046] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  133.287046] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  133.589047] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  133.899059] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  134.156048] usb 5-2: reset full speed USB device number 2 using uhci_hcd
[  134.353100] sd 6:0:0:0: [sdb] Unhandled error code
[  134.353115] usb 5-2: USB disconnect, device number 2
[  134.353130] sd 6:0:0:0: [sdb]  Result: hostbyte=0x07 driverbyte=0x00
[  134.353138] sd 6:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[  134.353160] end_request: I/O error, dev sdb, sector 0
[  134.353167] Buffer I/O error on device sdb, logical block 0
[  134.353304] Dev sdb: unable to read RDB block 0
[  134.353343]  sdb: unable to read partition table                                                  <-- doesn't look good
[  134.353713] sd 6:0:0:0: [sdb] READ CAPACITY failed                                            <- nor does this
[  134.353720] sd 6:0:0:0: [sdb]  Result: hostbyte=0x01 driverbyte=0x00
[  134.353728] sd 6:0:0:0: [sdb] Sense not available.
[  134.353817] sd 6:0:0:0: [sdb] Asking for cache data failed
[  134.353825] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  134.353834] sd 6:0:0:0: [sdb] Attached SCSI disk

[M0E-lnx]

With the drive plugged in issue "fdisk -l " without the quotes.  Post your results.

[Mr. Creosote]

fdisk -l shows only my internal drive partitions. I hadn't posted it earlier because I thought the output wasn't contributory, sorry about that.

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00039bac

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048   204802047   102400000   83  Linux
/dev/sda2       204802048   245762047    20480000   82  Linux swap
/dev/sda3       245762048   655362047   204800000   83  Linux
/dev/sda4       655362048  1953523711   649080832   83  Linux


In other news, my old 600X laptop running VL 6.0 Light Final found and installed the drive in /mnt/vl-hot effortlessly. I don't see the vl-hot directory in my 7.0 install.  Did I miss something on my install?   I'm a little fuzzy on how HAL may mount peripherals as opposed to vl-hot if vl-hot has been deprecated.

[bigpaws]

The two notes ( I believe they are yours) about this not being good
from the output of dmesg is correct. The drive is recognized but
not mounted. That is why it does not show up under fdisk -l.

I found this from an Ubuntu:

http://ubuntuforums.org/showthread.php?t=7977890

I would first check the output of:

less /sys/module/usbcore/parameters/autosuspend

Then try:

echo -1 >/sys/module/usbcore/parameters/autosuspend


Then try the device, you may need to reboot.

If that does not work the revert to the old autosuspend
config.

Bigpaws

[Mr. Creosote]

Thanks bigpaws.  The link you provided is dead end, unfortunately although I have done other searches for similar problems in different platforms.  I'll see if I can't track down the post but I've done a reasonable search for this issue and tried solutions that worked in other distros (setting SATA mode to AHCI rather than IDE, allowing the drive to powerup before connecting, removing module uas, adding usb_storage to module.conf).

The detailed format that I annotated was after running the echo -l command which was also suggested by uelsk8s.  I got the detailed recognition and failure information after running the command and rebooting.

Given that 6.0 on my laptop seemed to recognize the drive, I downloaded the 6.0 Live iso to try that, but when I went to burn it, k3b informed me it couldn't find the optical drive (which is also external) and asked if hal was running.  ps -aux suggests that the hal daemon is running:

root      9519  0.0  0.0   3680  1208 ?        S    00:50   0:00 hald-runner
root      9548  0.0  0.0   3776  1028 ?        S    00:50   0:00 hald-addon-input

Similarly to the drive on the cable, the optical drive shows up and is recognized in lsusb but does not appear in fdisk -l and dmesg complains about it as well.

[ 1860.787765] end_request: I/O error, dev sr0, sector 0
[ 1860.787792] EXT4-fs (sr0): unable to read superblock
[ 1860.806090] sr 298:0:0:0: [sr0]  Result: hostbyte=0x00 driverbyte=0x08
[ 1860.806101] sr 298:0:0:0: [sr0]  Sense Key : 0x5 [current]
[ 1860.806111] sr 298:0:0:0: [sr0]  ASC=0x21 ASCQ=0x0
[ 1860.806119] sr 298:0:0:0: [sr0] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 01 00 00 00
[ 1860.806143] end_request: I/O error, dev sr0, sector 0
[ 1860.806171] FAT-fs (sr0): unable to read boot sector

less /sys/module/usbcore/parameters/autosuspend only seems to have a "-1"  in it with no other output.

The lack of recognition for the optical drive is a bit alarming.  I can mount it fine, but not being able to use it to burn is a problem. 

[Joe1962]

Optical drives do not show in fdisk, period. So that is not a problem. What I don't get is why it is showing EXT4-fs and FAT-fs messages with regards to sr0, which should be the optical drive. Is the drive using an external power adapter, or just USB power?

With regards to the hard drive, I have similar issues with a certain 2.5" 160GB IDE hard drive, with an enclosure and also with an adapter cable. It works well on some computers, not at all on others, and intermittently on some more... In fact, on a certain core 2 quad PC with Win7 (not mine) it always ends up becoming unreadable with the enclosure, while working for short periods with the adapter cable. I ended up attributing all this to the power requirements of this particular drive, which (I guess) are OK for some USB sockets, but not all. Also, the enclosure seems to draw more power than the adapter cable.

[Mr. Creosote]

Optical drives do not show in fdisk, period. So that is not a problem. What I don't get is why it is showing EXT4-fs and FAT-fs messages with regards to sr0, which should be the optical drive. Is the drive using an external power adapter, or just USB power?

With regards to the hard drive, I have similar issues with a certain 2.5" 160GB IDE hard drive, with an enclosure and also with an adapter cable. It works well on some computers, not at all on others, and intermittently on some more... In fact, on a certain core 2 quad PC with Win7 (not mine) it always ends up becoming unreadable with the enclosure, while working for short periods with the adapter cable. I ended up attributing all this to the power requirements of this particular drive, which (I guess) are OK for some USB sockets, but not all. Also, the enclosure seems to draw more power than the adapter cable.

Thanks for the heads up on fdisk and opticals.  The drive is recognized by the bios and will mount. It just seems that HAL is not recognizing it. The old laptop where it did mount was using VL 6.0 and vl-hot.  The optical drive has dual USB cables.  It will run on a single but the manufacturer recommends using the dual.

The hard drive is independently powered with it's own transformer so it's not a usb power issue.  I've played around a bit with the USB BIOS settings with no luck.  I've tried 3 live distros, none of which detected the drive at all although I may have pooched something playing around with the BIOS settings so I need to step back through that process.  I'm staring to lean to this being a hardware issue as you've suggested with . I'll have to look in to the device a bit more and make see if there are any compatibility issues.  The `pooter itself is new (Zotac Zbox) so there may be something with it's architecture that I need to play with.

[Mr. Creosote]

So ,still ticking away at this issue

I did find what appears to be a solution at https://bbs.archlinux.org/viewtopic.php?id=125831 with regards to the delay for usb_storage. I'm just not sure where or how to add "usb-storage.delay_use=5" to the kernel to test this out.  I'm not all that familiar with kernel options etc.

[ronsking]

In order for me to boot VL from my external USB hard drive I have to add

Code:

rootdelay=9

. I'm using a VL LiveCD to boot from so I enter that as a boot parameter.

[Mr. Creosote]

Thanks ronsking

My challenge is more that I'm unable to mount either an external hard drive or optical drive after booting. There is no problem booting VL on the box I'm using. The longer usb_storage.delay_use setting (5 seconds versus 1 second) allows firmware in the peripheral to get done whatever they need to do before being scanned by the kernel's usb_storage module.  At least, I'm hoping this will work.

-edit--  I did try the rootdelay=9 as a boot parameter via lilo but still no joy.  It's quite odd.  I've tried on a few live CD's that have the delay_use=5 setting with no luck. The box picks up a regular USB storage device no problem, my Galaxy S cell phone no problem, but it just can't seem to figure out this drive adapter. And it still shows as having no optical drive :-p.  It looks like I may have to use USB cards to transfer my data from the drive because my ancient laptop can pick it up no problem