I have a VANTEC CB-ISATAU2 SATA/IDE to USB 2.0 Adapter. It's basically a USB dongle with PATA and SATA connectors on it, you can attach a laptop drive, a standard desktop PATA drive, or a SATA drive to it.
It works exactly as expected with PATA drives.
I have a SATA drive I'd like to get some data off of. However, I can't seem to get the drive to work correctly. I am somewhat limited in my ability to troublshoot this problem as I don't have another SATA drive and I don't have any other SATA interface, so I can't isolate either the drive or the adapter. Hopefully someone will see something here that will give me a better idea of what the problem is.
The partition table on the disk looks like this:
[root@snorlax ~]# fdisk -l /dev/sdc
Disk /dev/sdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 1305 10482381 83 Linux
/dev/sdc2 1306 10969 77626080 fd Linux raid autodetect
/dev/sdc3 10970 11034 522112+ 82 Linux swap / Solaris
/dev/sdc4 11035 19457 67657747+ 83 Linux
For what it's worth, the data I want is on the md partition 2. everything else is junk.
I am attaching the drive to my thinkpad T43 running FC6.
I seem to get different results every time I plug the drive in. For example, this time I plug it in and it never really sees the drive correctly at all.
Dec 11 11:10:15 snorlax kernel: usb 5-3: new high speed USB device using ehci_hcd and address 73
Dec 11 11:10:15 snorlax kernel: usb 5-3: configuration #1 chosen from 1 choice
Dec 11 11:10:15 snorlax kernel: scsi23 : SCSI emulation for USB Mass Storage devices
Dec 11 11:10:20 snorlax kernel: Vendor: Model: Rev:
Dec 11 11:10:20 snorlax kernel: Type: Direct-Access ANSI SCSI revision: 02
Dec 11 11:10:20 snorlax kernel: sd 23:0:0:0: Attached scsi disk sdc
Dec 11 11:10:20 snorlax kernel: sd 23:0:0:0: Attached scsi generic sg2 type 0
Dec 11 11:10:33 snorlax kernel: usb 5-3: USB disconnect, address 73
Dec 11 11:11:14 snorlax kernel: usb 5-3: new high speed USB device using ehci_hcd and address 74
Dec 11 11:11:14 snorlax kernel: usb 5-3: configuration #1 chosen from 1 choice
Dec 11 11:11:14 snorlax kernel: scsi24 : SCSI emulation for USB Mass Storage devices
Dec 11 11:11:19 snorlax kernel: Vendor: SAMSUNG Model: J1ML628192 Rev: 0-43
Dec 11 11:11:19 snorlax kernel: Type: Direct-Access ANSI SCSI revision: 02
Dec 11 11:11:19 snorlax kernel: SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
Dec 11 11:11:19 snorlax kernel: sdc: Write Protect is off
Dec 11 11:11:19 snorlax kernel: sdc: assuming drive cache: write through
Dec 11 11:11:19 snorlax kernel: SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
Dec 11 11:11:19 snorlax kernel: sdc: Write Protect is off
Dec 11 11:11:19 snorlax kernel: sdc: assuming drive cache: write through
Dec 11 11:11:23 snorlax udevd-event[32176]: wait_for_sysfs: waiting for '/sys/devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3:1.0/host24/target24:0:0/24:0:0:0/ioerr_cnt' failed
Dec 11 11:11:50 snorlax kernel: sdc:<6>usb 5-3: reset high speed USB device using ehci_hcd and address 74
Dec 11 11:12:00 snorlax kernel: usb 5-3: reset high speed USB device using ehci_hcd and address 74
Dec 11 11:12:36 snorlax kernel: usb 5-3: reset high speed USB device using ehci_hcd and address 74
Dec 11 11:12:36 snorlax kernel: usb 5-3: device descriptor read/64, error -71
Dec 11 11:12:36 snorlax kernel: usb 5-3: device descriptor read/64, error -71
Dec 11 11:12:36 snorlax kernel: usb 5-3: reset high speed USB device using ehci_hcd and address 74
Dec 11 11:12:37 snorlax kernel: usb 5-3: device descriptor read/64, error -71
Dec 11 11:12:37 snorlax kernel: usb 5-3: device descriptor read/64, error -71
Dec 11 11:12:37 snorlax kernel: usb 5-3: reset high speed USB device using ehci_hcd and address 74
Dec 11 11:12:37 snorlax kernel: usb 5-3: device not accepting address 74, error -71
Dec 11 11:12:37 snorlax kernel: usb 5-3: reset high speed USB device using ehci_hcd and address 74
Dec 11 11:12:38 snorlax kernel: usb 5-3: device not accepting address 74, error -71
Dec 11 11:12:38 snorlax kernel: usb 5-3: USB disconnect, address 74
Dec 11 11:12:38 snorlax kernel: sd 24:0:0:0: scsi: Device offlined - not ready after error recovery
Dec 11 11:12:38 snorlax kernel: sd 24:0:0:0: SCSI error: return code = 0x00050000
Dec 11 11:12:38 snorlax kernel: end_request: I/O error, dev sdc, sector 0
Dec 11 11:12:38 snorlax kernel: Buffer I/O error on device sdc, logical block 0
Dec 11 11:12:38 snorlax kernel: sd 24:0:0:0: rejecting I/O to offline device
Dec 11 11:12:38 snorlax kernel: Buffer I/O error on device sdc, logical block 0
Dec 11 11:12:38 snorlax kernel: sd 24:0:0:0: rejecting I/O to offline device
Dec 11 11:12:38 snorlax kernel: Buffer I/O error on device sdc, logical block 0
Dec 11 11:12:38 snorlax kernel: unable to read partition table
Dec 11 11:12:38 snorlax kernel: sd 24:0:0:0: Attached scsi disk sdc
Dec 11 11:12:38 snorlax kernel: sd 24:0:0:0: Attached scsi generic sg2 type 0
Dec 11 11:12:38 snorlax usb_id[32229]: usb_id: unable to access '/block/sdc'
Dec 11 11:12:38 snorlax scsi_id[32230]: scsi_id: unable to access '/block/sdc'
Dec 11 11:12:38 snorlax scsi_id[32239]: scsi_id: unable to access '/block/sdc'
Dec 11 11:12:38 snorlax kernel: usb 5-3: new high speed USB device using ehci_hcd and address 75
Dec 11 11:12:38 snorlax kernel: usb 5-3: device descriptor read/64, error -71
Dec 11 11:12:38 snorlax kernel: usb 5-3: device descriptor read/64, error -71
Dec 11 11:12:38 snorlax kernel: usb 5-3: new high speed USB device using ehci_hcd and address 76
Dec 11 11:12:39 snorlax kernel: usb 5-3: device descriptor read/64, error -71
Dec 11 11:12:39 snorlax kernel: usb 5-3: device descriptor read/64, error -71
Dec 11 11:12:39 snorlax kernel: usb 5-3: new high speed USB device using ehci_hcd and address 77
Dec 11 11:12:39 snorlax kernel: usb 5-3: device not accepting address 77, error -71
Dec 11 11:12:39 snorlax kernel: usb 5-3: new high speed USB device using ehci_hcd and address 78
Dec 11 11:12:40 snorlax kernel: usb 5-3: device not accepting address 78, error -71
Now, I try again a few seconds later and get a different result. This time, the system sees the disk. I can run fdisk and see the partition table. It even mounts partition 4, though it starts having trouble immediately.
Dec 11 11:14:21 snorlax kernel: usb 5-4: new high speed USB device using ehci_hcd and address 79
Dec 11 11:14:21 snorlax kernel: usb 5-4: configuration #1 chosen from 1 choice
Dec 11 11:14:21 snorlax kernel: scsi25 : SCSI emulation for USB Mass Storage devices
Dec 11 11:14:26 snorlax kernel: Vendor: SAMSUNG Model: J1ML628192 Rev: 0-43
Dec 11 11:14:26 snorlax kernel: Type: Direct-Access ANSI SCSI revision: 02
Dec 11 11:14:26 snorlax kernel: SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
Dec 11 11:14:26 snorlax kernel: sdc: Write Protect is off
Dec 11 11:14:26 snorlax kernel: sdc: assuming drive cache: write through
Dec 11 11:14:26 snorlax kernel: SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
Dec 11 11:14:26 snorlax kernel: sdc: Write Protect is off
Dec 11 11:14:26 snorlax kernel: sdc: assuming drive cache: write through
Dec 11 11:14:26 snorlax kernel: sdc: sdc1 sdc2 sdc3 sdc4
Dec 11 11:14:26 snorlax kernel: sd 25:0:0:0: Attached scsi disk sdc
Dec 11 11:14:26 snorlax kernel: sd 25:0:0:0: Attached scsi generic sg2 type 0
Dec 11 11:14:26 snorlax kernel: EXT3-fs: journal inode is deleted.
Dec 11 11:14:27 snorlax kernel: EXT2-fs: corrupt root inode, run e2fsck
Dec 11 11:15:13 snorlax kernel: scsi 22:0:0:0: rejecting I/O to dead device
Dec 11 11:15:25 snorlax last message repeated 2 times
Dec 11 11:15:25 snorlax kernel: Buffer I/O error on device sdb4, logical block 2056
Dec 11 11:15:25 snorlax kernel: lost page write due to I/O error on sdb4
Dec 11 11:16:40 snorlax kernel: usb 5-4: reset high speed USB device using ehci_hcd and address 79
Dec 11 11:16:50 snorlax kernel: usb 5-4: reset high speed USB device using ehci_hcd and address 79
Dec 11 11:17:34 snorlax kernel: usb 5-4: USB disconnect, address 79
Sometimes, it mounts both partition 1 and partion 4, but in every case, it eventually gets hosed up after five minutes or so.
Is there something else I should try? My feeling is that the next step is to return the USB adapter and try another one.