Old external drive

bricem13 · 10-04-2022, 01:47 PM

Hi guys

I have an old IDE drive that I put in an external usb connector box.

It's pretty old hardware but the data on it has some interest to me - I try now to recover it and then will throw the drive away.

So it's a mass-storage device which filesystem should be ext2fs (old drive I told).

Unfortunately I have errors at connection:

Code:

[root@TuxBox brice]# dmesg 
...
[ 1764.352846] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1764.352860] Buffer I/O error on dev sda, logical block 0, async page read
[ 1764.353527] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 1764.353537] sd 1:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[ 1764.353545] sd 1:0:0:0: [sda] tag#0 Add. Sense: Invalid command operation code
[ 1764.353551] sd 1:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[ 1764.353554] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1764.353565] Buffer I/O error on dev sda, logical block 0, async page read
[ 1764.353588] ldm_validate_partition_table(): Disk read failed.
[ 1764.354151] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 1764.354159] sd 1:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[ 1764.354165] sd 1:0:0:0: [sda] tag#0 Add. Sense: Invalid command operation code
[ 1764.354171] sd 1:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[ 1764.354175] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1764.354185] Buffer I/O error on dev sda, logical block 0, async page read
[ 1764.357916] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 1764.357928] sd 1:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[ 1764.357936] sd 1:0:0:0: [sda] tag#0 Add. Sense: Invalid command operation code
[ 1764.357943] sd 1:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[ 1764.357946] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1764.357962] Buffer I/O error on dev sda, logical block 0, async page read
[ 1764.360751] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 1764.360761] sd 1:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[ 1764.360766] sd 1:0:0:0: [sda] tag#0 Add. Sense: Invalid command operation code
[ 1764.360771] sd 1:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[ 1764.360773] critical target error, dev sda, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1764.360784] Buffer I/O error on dev sda, logical block 0, async page read
[ 1764.360808]  sda: unable to read partition table
[ 1764.360889] sd 1:0:0:0: [sda] Attached SCSI disk
[ 1764.382591] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 1764.382597] sd 1:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[ 1764.382599] sd 1:0:0:0: [sda] tag#0 Add. Sense: Invalid command operation code
[ 1764.382602] sd 1:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 ff ff ff 80 00 00 00 08 00 00
[ 1764.382603] critical target error, dev sda, sector 4294967168 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1764.383164] sd 1:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[ 1764.383168] sd 1:0:0:0: [sda] tag#0 Sense Key : Illegal Request [current] 
[ 1764.383170] sd 1:0:0:0: [sda] tag#0 Add. Sense: Invalid command operation code
[ 1764.383172] sd 1:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 ff ff ff 80 00 00 00 08 00 00
[ 1764.383173] critical target error, dev sda, sector 4294967168 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1764.383178] Buffer I/O error on dev sda, logical block 536870896, async page read
[root@TuxBox brice]#

I have no clue which tool could help me, I found some topic here and tried smartctl but:

Code:

[root@TuxBox brice]# smartctl -a /dev/sda 
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.12-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sda: Unsupported USB bridge [0x04b4:0x6830 (0x001)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

[root@TuxBox brice]#

and here I am stuck...

any advice please?

thank you
Brice

Emerson · 10-04-2022, 01:54 PM

I think the interface you are using is a POS. If I was in your shoes I'd use ddrescue and pull a full image of this drive, then mount partitions-filesystems in this image and see what's intact and can be used.

jefro · 10-04-2022, 03:01 PM

Guess you can check the jumpers. Not sure which way they might need to be or even if in.

elgrandeperro · 10-04-2022, 03:06 PM

Make sure the drive is fully spun up before you plug it in via usb. That sometimes works.

You aren't getting any reads, so something (if the drive is good) is wrong.

mrmazda · 10-05-2022, 01:29 AM

Quote:

Originally Posted by jefro

Guess you can check the jumpers. Not sure which way they might need to be or even if in.

IOW, without correctly setting drive jumpers according to the instructions for the USB container, you cannot expect to mount or read whatever the drive contains. Correct jumper settings depend on both the drive and the container, as not all PATA drives require the same jumper setting for the same purpose. Most likely the container requires use of either a master drive setting (e.g. for Seagate), or an only drive setting (e.g. for WD).

business_kid · 10-05-2022, 04:57 AM

From post #1:

The drive appears to be a dud from those errors. Forget it.

If you have an old PC, I'd remove it from it's external box, remove the jumpers and try it as a slave. The master jumper is usually marked if there's no other drive on that lead. Forget any external boxes. It's just an extra source of possible error.

When my diagnosis is confirmed, sling it.

jefro · 10-05-2022, 08:35 AM

A long time ago I played with those and found some cases and drives needed to have jumpers in non-standard locations. Play with them to see if it changes.

elgrandeperro · 10-05-2022, 09:19 AM

Give the drive make and model and someone can lookup the jumper settings.

michaelk · 10-05-2022, 10:45 AM

The other basic questions are, is the external power supply plugged in and do you feel it spinning?

bricem13 · 10-05-2022, 01:48 PM

hi

thank you for the replies.

Drive spins at power up and then stops after some seconds.

I tried under W.. and not able to initialize it.

I tried in an old computer directly on an IDE connector and got at start a "disk2 failure" (with or without the original IDE drive). I did not change the jumper settings at that time as it was previously working in the external box. I let the jumper as is and not as slave, I can give it a go but I have little hope...

Drive is a WD1600AAJB - 00WRA0.

BR

bricem13 · 10-05-2022, 01:50 PM

one more thing: now I seem not getting any "sda" mention at power up:

Output of dmesg:

Code:

[  612.781866] usb 1-3: new high-speed USB device number 6 using xhci_hcd
[  612.922953] usb 1-3: New USB device found, idVendor=04b4, idProduct=6830, bcdDevice= 0.01
[  612.922961] usb 1-3: New USB device strings: Mfr=56, Product=78, SerialNumber=100
[  612.922964] usb 1-3: Product: USB2.0 Storage Device
[  612.922966] usb 1-3: Manufacturer: Cypress Semiconductor
[  612.922968] usb 1-3: SerialNumber: ############
[  612.924063] ums-cypress 1-3:1.0: USB Mass Storage device detected
[  612.924220] scsi host1: usb-storage 1-3:1.0

mrmazda · 10-05-2022, 02:01 PM

Quote:

Originally Posted by bricem13

I let the jumper as is and not as slave, I can give it a go but I have little hope...

You have a one chance in four doing that. Master, Slave, Only, CS are the usual WD options, IIRC.

michaelk · 10-05-2022, 04:31 PM

Stops after some seconds and no sda in dmesg is not a good sign.

computersavvy · 10-05-2022, 06:12 PM

Given the errors related to the USB interface, what happens if you try a different IDE-USB interface. It easily could be either the drive itself, or the external case / adapter you connected it with. Should you happen to have access to older PC hardware with a mobo that has the ide interface it might be possible to connect directly to the drive and eliminate the usb interface entirely.

Smartctl often does not communicate with a drive connected by USB, though for better quality interfaces it may.

bricem13 · 10-06-2022, 10:59 AM

ok got the old computer back up.

drive in slave, other IDE drive is master. Bios output drive 2 error... not good

anyway I got a knoppix live-CD and can get the computer to start.

but then, what to do next? there is only gparted on the live-cd and it only recognizes the master drive.