ST35003200AS after CC error. Cylinder stuck at 42%

I had this Seagate Baracuda ST35003200AS 500GB, it been lying down for years with a "LED CC" error(it was a notorious screw-up from Seagate back in the 2010s). In 2013 the disk stopped being detected by the system. It was due to some firmware bug.

Now I finally managed to bring it back to life(with rs232-ttl cable and a few tutorials), but the disk is seeing RAW on Windows and asking to create new table, which I ofc didnt. On Linux it cant be mounted, but at least disks utility and lsblk show 2 partitions. Both on LINUX and Windows when ussing TESTDISK I managed to see some part of filesystem, and even recover some files with photorec (about 7gb).

But the problem is that when I try to copy or clone the disk with ddrescue it stuck at 1.43% and the rest files are read errors. The TESTDISK when analyzing the partitions it gives:
Disk /dev/sdd - 500 GB / 465 GiB - CHS 60801 255 63
Analyse cylinder 26110/60800: 42%


so it stuck at 42% (btw I dont know if that 42% related to the whole disk capacity or only the cylinder, because its strange why the disk cant recover more than 1.43% if it stuck on 42%, there are a lot of space from 1.43 to 42).

Now i have another problem: after some 15-20 sec after being plugged the disk is kinda turn itself off so hddsuperclone cant finish cloning - or maybe its because it got onto 1.43% sector and kinda send to the disk I'm out and the disk as well, Im out too. idk. Or it cant read after 1.43 because the disk turns off??? (though i recovered the disk multiple times and every time its on 1.43, so cant be the timing)


Is there some possible ways to clone the disk without bad cylinder area?
I read something about recover partitions with hyperterminal command m0,2,2,,1 or something. Or maybe TESTDISK have some advanced features?


Sorry for the long post.
 
Last edited:

Jared

Administrator
Staff member
You can try throwing in the -R trigger in your ddrescue command to make it image backward from the highest LBA to the lowest. If it's just one area of bad sectors, you can perhaps image both ways up to the bad area.

Even better, try using hddsuperclone to image it. It's better at skipping around damaged areas, especially if the true culprit is a failed head.
 
Top