ddrescue and 2.5" USB external drive. MacOS.
My background: I did 1½ years of comp sci at uni some years ago, worked in tech support for an SME and then doing home PC repairs etc. I'm quite familiar with Linux, do some simple programming occasionally in bash, perl and in the past C.
I've used ddrescue quite a lot in the past, but am now out of practice - it's probably about 10 years since I did, and I'm now retired and living on a boat.
My Western Digital "Elements" portable hard drive has died, and when I unshucked the drive from its case I was surprised to find it has no SATA connector, but instead its USB connector (wide-flat type) is directly part of the drive's PCB. No doubt this has been common for years, as I suppose it makes a lot of sense.
Otherwise, the drive is obviously based on a 2.5" laptop drive - it's 5TB in size, although it was partitioned into 750MB and ~4TB, and I only care about the 4TB partition.
The data on this drive is not valuable, but I'm trying to recover it so long as it doesn't cost me anything. I don't have access to Linux at the moment, although I suppose I might be able to run it in a VM or from a liveCD.
So far I have compiled ddrescue-1.27 on my M2 MacBook and have started cloning from the dead drive to a new one, e.g.:
sudo ddrescue -f -v -n -i299999MB -s4250410942464 -u /dev/disk4s3 /dev/disk5s3 rescue_map.txt
I'm quite pleased to have succeeded at copying about 60% of the drive (well, 60% of the important partition) off it overnight, but what I keep finding is that everything freezes solid when I get to a bad part of the drive - I have to reboot the laptop, plug the drive back in (usually it's recognised if I give it a bit of a break) and then start again.
It stalled at about 70000MB so I restarted at 99999MB, then stalled again around 250000MB so I restarted at 299999MB - the cloning continued successfully to 2664GB overnight. I've had some false starts today trying to restart at 2664GB, 2666GB and 2690GB.
It feels like the USB interface is insulating the drive from ddresecue, as the program just hangs when it's unable to get data. Finally ddrescue exits with an error message and I restart a bit further on.
Whilst writing this I realise that I should probably be using /dev/**r**disk4s3 and not /dev/disk - I did try this at some point before, but must've got mixed up during one of my false starts. I believe this is faster, and will try again when I have another attempt later.
I don't seem to be able to use direct disc access, which I assume is because it's MacOS but I will try again when I try with /dev/rdisk later.
Sorry not to have any clear questions, but would be grateful for any advice or pointers if you see anything I'm doing wrong.
I'm guessing I'd be more likely to have success if I were able to replace the drive's PCB with an SATA one from a drive that was otherwise hardware identical, but this isn't practical for me. As I said, I don't think any of the data is valuable - it's not worth paying a specialist to recover it, so I'm really just futzing about to see if I can get the data back for free.
* https://i.imgur.com/q0XSq9x.jpg * https://i.imgur.com/ephm2Tg.jpg * https://i.imgur.com/3cG6RTz.jpg * https://i.imgur.com/r29DSes.jpg