IDE/SATA to USB adapter not working properly

nass · 05-19-2012, 11:33 AM

Hello everyone,
I recently bought a Digitus DA - 70200 IDE/SATA to USB in order to transfer data from a somewhat old laptop disk (the laptop died).

I try to connect this drive in my pc (slack64 - 13.37 , kernel 2.6.37.6 modified generic) but it doesn't showup properly!
when i connect the USB device is identified:

Quote:

usb 1-1: new high speed USB device using ehci_hcd and address 2
usb 1-1: New USB device found, idVendor=152d, idProduct=2338
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
usb 1-1: Product: USB to ATA/ATAPI bridge
usb 1-1: Manufacturer: JMicron
usb 1-1: SerialNumber: 43527242080A
Initializing USB Mass Storage driver...
scsi14 : usb-storage 1-1:1.0
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi 14:0:0:0: Direct-Access FUJITSU MHT2080AT PQ: 0 ANSI: 2 CCS
sd 14:0:0:0: Attached scsi generic sg14 type 0
sd 14:0:0:0: [sdm] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
sd 14:0:0:0: [sdm] Write Protect is off
sd 14:0:0:0: [sdm] Mode Sense: 28 00 00 00
sd 14:0:0:0: [sdm] Assuming drive cache: write through
sd 14:0:0:0: [sdm] Assuming drive cache: write through

and try to see the partitions with cfdisk /dev/sdm

after a few seconds of frozen terminal i get a prompt back and check dmesg again"

Quote:

usb 1-1: reset high speed USB device using ehci_hcd and address 2
usb 1-1: reset high speed USB device using ehci_hcd and address 2
usb 1-1: reset high speed USB device using ehci_hcd and address 2
usb 1-1: reset high speed USB device using ehci_hcd and address 2
usb 1-1: reset high speed USB device using ehci_hcd and address 2
sd 14:0:0:0: Device offlined - not ready after error recovery
sd 14:0:0:0: [sdm] Unhandled error code
sd 14:0:0:0: [sdm] Result: hostbyte=0x05 driverbyte=0x00
sd 14:0:0:0: [sdm] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
end_request: I/O error, dev sdm, sector 0
Buffer I/O error on device sdm, logical block 0
sd 14:0:0:0: rejecting I/O to offline device
sd 14:0:0:0: rejecting I/O to offline device
sd 14:0:0:0: rejecting I/O to offline device
sd 14:0:0:0: rejecting I/O to offline device
sd 14:0:0:0: rejecting I/O to offline device
sd 14:0:0:0: rejecting I/O to offline device
Dev sdm: unable to read RDB block 0
sd 14:0:0:0: rejecting I/O to offline device
sd 14:0:0:0: rejecting I/O to offline device
sdm: unable to read partition table
sd 14:0:0:0: [sdm] Attached SCSI disk

I can't find any info about connecting this (or similar) digitus products in linux, apart from the following in their wiki of a similar product:

Quote:

Sometimes the problem occurs that your hard disk drive uses an unsupported file system. The following file systems are supported if you use this adapter cable:

FAT (up to FAT32) and NTFS Single User

seriously, is it possible that the disk is identified in filesystem level???
The disk I'm trying to access is formatted in xfs, but i somehow feel this shouldn't matter....

any clues?
thank you all for your help.

Doc CPU · 05-19-2012, 11:57 AM

Hi there,

Quote:

Originally Posted by nass

I recently bought a Digitus DA - 70200 IDE/SATA to USB ...

no, it's exactly the other way: A USB to IDE/SATA adapter. With that kind of adapters, you usually mention the host-side interface first (like USB to RS232 or IDE to Compact Flash).

Quote:

Originally Posted by nass

I try to connect this drive in my pc (slack64 - 13.37 , kernel 2.6.37.6 modified generic) but it doesn't showup properly!

The adapter is being recognized ("USB to ATA/ATAPI bridge"), then the attached drive is recognized and the standardized generic USB Mass Storage driver is used. A moment later, the drive is getting disconnected again. Unfortunately, the logs don't tell why.

Quote:

Originally Posted by nass

seriously, is it possible that the disk is identified in filesystem level???

No.

Quote:

Originally Posted by nass

The disk I'm trying to access is formatted in xfs, but i somehow feel this shouldn't matter...

You're right, it shouldn't.
But there's another trail to pursue: How does the disk drive get its power? From the USB adapter?

Especially with older drives, the power supplied by a USB port (500mA max. at 5V) is often not enough.
What happens then is that the drive is recognized correctly, but when it spins up, the USB current limit is exceeded and the device is being shut down again by the USB controller. I've had that several times.
You might try operating the drive with an extra power source.

[X] Doc CPU

nass · 05-19-2012, 12:11 PM

hello doc_CPU,
the DA-70200 modem has an external PSU that can powerup any connected drive. the pictures should give you an idea
http://www.computerfood.gr/index.php...oduct_id=30868

so it can't be that.
do you have this adapter?
if yes, have you managed to connect it?

Thank you

Doc CPU · 05-19-2012, 12:31 PM

Hi there,

Quote:

Originally Posted by nass

the DA-70200 modem has an external PSU that can powerup any connected drive. the pictures should give you an idea
http://www.computerfood.gr/index.php...oduct_id=30868

so it can't be that.

yes, I agree. After all, it was just a guess.

Quote:

Originally Posted by nass

do you have this adapter?
if yes, have you managed to connect it?

No, and I'm not using slackware either. But I have two or three different USB/IDE and USB/SATA adapters, and they work fine with my Linux and Windows PCs. And I see no reason for that digitus adapter not to work with your configuration. Maybe you can check it by attaching another disk drive that is known to work, so you know the adapter itself works with your system.
However, it's recognized correctly by the system, the logs are plausible at least for the moment the unit is attached.

Maybe I'd have a clue if I had all the stuff on my own table, but from the distance, I'm running out of ideas.

[X] Doc CPU

Lirey · 05-19-2012, 07:20 PM

Hi,

That device looks like an upgraded version of the no-name adapter that I've used for years. The one I have is a pretty simple/dumb device - it doesn't recognize or care about the filesystem, so it will work reliably with pretty much everything. I've used it with FAT, NTFS, ext3, ext4, and reiserfs. I'm not sure if I've used it with xfs, but I might have. The only times I've had problems are when there was a problem with the disk (either the drive was bad or the file system was already corrupted).

There is one undocumented trick to using the device that I have. Many desktop drives, particular older ones, need to start up before the device is plugged in, otherwise either the adapter or drive can end up in a state where they are not communicating. Basically, with the device I have, I plug the adapter and power cable in to the disk drive. I turn on the power to the drive and wait for it to spin up. When in doubt, I'll wait for 30 seconds to 1 minute. Then I finally plug the USB cable into the computer. Wait another 15 seconds, or so, for the computer to recognize the adapter and drive. At that point you should be able to mount the disk.

If that doesn't work, see if the drive and adapter will work in another computer, or if the adapter works with another drive.

Lirey

sofasurfer · 08-13-2012, 03:19 AM

Lirey. Your sugestion worked. hook up he power, start the pc, wait for spinup, plug in USB. Good to go. Thanks.