Recovery Partitions ST2000DM001 - please help

[asRobi]

Hello,

6 months ago I detected that the OS was slow when startup: apps not open, not detected inalambrics devices until 20- 60sec passed. I thought the operating system was corrupt and I did not give it much importance.

The last week there were times when I shutdown the computer and it did not shutdown completely, showed a black screen and only the CPU fan working. When i power on it showed the black screen again without reaching the POST and did not detect peripherals like keyboard (cable).

I found the HDD (ST2000DM001) that was giving problems but it was late because two hdd were corrupted: WD RED and ST2000DM001. they both used the same lane sata3 asmedia (sata3a_0, sata3a_1).

I completely recovered the WD RED but I can't get with it ST2000DM001.

Status ST2000DM001:
- Hard Drive Power L-tab or shape is broken. (link: https://imgur.com/R8xXKI6)
- Bios not detect hdd
- Windows manager detect for initialize the drive.
- Crystal Disk info not Detect
- Test Disk detect but not found partitions for recovery.

Disk Info: https://imgur.com/xGxT9hf

SN:W1E1KTAQ
MODEL: ST2000DM001
PN: 1CH164-300
FW: CC43
DATE: 13136 Site: WU

PCB:100687658 rev B https://imgur.com/q3oVC2W

I Scan with EaseUS Partition recovery, Testdisk, MiniTool Partition Wizard. EaseUS data recovery wizard but found nothing.

I'm noob. I would need suggestions and what steps follow for recover the disk.



Log of Testdisk is too big(3gb) i only attach resume:

Code:

Partition table type defaults to Intel
Disk /dev/sde - 2000 GB / 1863 GiB - ST2000DM001-1CH164
Partition table type: Intel

Analyse Disk /dev/sde - 2000 GB / 1863 GiB - CHS 243201 255 63
Current partition structure:

Partition: Read error

search_part()
Disk /dev/sde - 2000 GB / 1863 GiB - CHS 243201 255 63
file_pread(8,16,buffer,32(0/0/33)) ReadFile Se ha especificado un dispositivo que no existe.

file_pread(8,3,buffer,48(0/0/49)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,3,buffer,95(0/1/33)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,8,buffer,111(0/1/49)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,11,buffer,158(0/2/33)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,2,buffer,2080(0/33/2)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,2,buffer,51(0/0/52)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,2,buffer,98(0/1/36)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,2,buffer,119(0/1/57)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,2,buffer,169(0/2/44)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,2,buffer,2082(0/33/4)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,16,buffer,63(0/1/1)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,3,buffer,79(0/1/17)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,3,buffer,126(0/2/1)) ReadFile Se ha especificado un dispositivo que no existe.

------------------------ file_pread() repeat x3269008 times ---

---- last part Scan -------------

file_pread(8,8,buffer,3907029070(243201/79/29)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,11,buffer,3907029117(243201/80/13)) ReadFile Se ha especificado un dispositivo que no existe.

file_pread(8,2,buffer,3907031039(243201/110/45)) lseek err Invalid argument
file_pread(8,1,buffer,3907029010(243201/78/32)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,1,buffer,3907029057(243201/79/16)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,1,buffer,3907029078(243201/79/37)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,1,buffer,3907029128(243201/80/24)) ReadFile Se ha especificado un dispositivo que no existe.
file_pread(8,1,buffer,3907031041(243201/110/47)) lseek err Invalid argument

Results

interface_write()

No partition found or selected for recovery

interface_write()

No partition found or selected for recovery
simulate write!

write_mbr_i386: starting...
file_pread(8,1,buffer,0(0/0/1)) ReadFile Se ha especificado un dispositivo que no existe.


Partition: Read error
Store new MBR code
write_all_log_i386: starting...
No extended partition
SIGHUP detected! TestDisk has been killed.

Attachments

[data-medics]

This is a Grenada family Seagate drive. The failure rate is extremely high on these, most often due to faulty media cache and bad sector reallocation functions. Usually, the issue is triggered as soon as the drive develops any bad sectors. The drive is obviously passing the initial initialization as it's reading it's ID properly, but it's probably getting stuck in a busy state shortly after that. It should be a simple recovery for a professional data recovery lab, but not likely something you can handle yourself.

I know we charge a flat $450 for most cases like this. Just to give you a baseline of cost.

If the drive shows its ID, the broken L connector isn't likely causing any issue. It's just a coincidence.

[pcimage]

This is a Grenada family Seagate drive. The failure rate is extremely high on these, most often due to faulty media cache and bad sector reallocation functions. Usually, the issue is triggered as soon as the drive develops any bad sectors. The drive is obviously passing the initial initialization as it's reading it's ID properly, but it's probably getting stuck in a busy state shortly after that. It should be a simple recovery for a professional data recovery lab, but not likely something you can handle yourself.

I know we charge a flat $450 for most cases like this. Just to give you a baseline of cost.

If the drive shows its ID, the broken L connector isn't likely causing any issue. It's just a coincidence.

Agree with above, nothing to do with PCB at all.

If the data is at all important then send it to a recovery lab, it shouldn’t be expensive at this stage. But the more you mess with it, the worse it will get!

[asRobi]

This is a Grenada family Seagate drive. The failure rate is extremely high on these, most often due to faulty media cache and bad sector reallocation functions. Usually, the issue is triggered as soon as the drive develops any bad sectors. The drive is obviously passing the initial initialization as it's reading it's ID properly, but it's probably getting stuck in a busy state shortly after that. It should be a simple recovery for a professional data recovery lab, but not likely something you can handle yourself.

I know we charge a flat $450 for most cases like this. Just to give you a baseline of cost.

If the drive shows its ID, the broken L connector isn't likely causing any issue. It's just a coincidence.

Agree with above, nothing to do with PCB at all.

Do you suggest the problem may be in the firmware (pcb or hdd) or is it a physical problem?

[asRobi]

Any good recovery lab in Spain that you recommend?