Maxtor DiamondMax Plus 9 BAD Sectors - Translator issue?

[Friedrich]

Hello,
i've this 160 GB Maxtor DiamondMax Plus 9 which after power surge burned TVS diode on the pcb.
I replaced the diode and now the drive spins again, but windows doesn't detect it.
BIOS detects it but after 20 seconds about.

Maxtor DM9 SATA + ATA connector
CODE: YAR51EW0
6Y160M004551A
PCB: Calypso 301520104

MHDD surface scan shows bad sectors and mhdd smart shows a lot of reallocated sectors, so i cloned the good sectors with Mediatools Prosoft, now i want to recover also bad sectors if possible.
Usually Mediatools is able to read hdd bad sectors (after many read retrys) but not for this drive...
For this reason I suspect there is a problem with firmware translators.

On Barracuda 7200.11 if there are a lot of bad sectors sometimes the translator regeneration make it work again, sometimes helps also to reset G-list, but i don't have enough experience with DM9 hard drives, can you help me?

There is a way to reset G-list or to do translator regeneration on DM9?

This are the bad LBAs:

Code:

0
63 ----> 94
6.160.487 ----> 6.161.382
6.168.151 ----> 6.170.550
6.177.319 ----> 6.188.886
6.195.655 ----> 6.198.054
6.204.823 ----> 6.207.222
6.213.991 ----> 6.216.390
6.223.159 ----> 6.225.558
6.232.327 ----> 6.234.726
6.241.495 ----> 6.243.894
6.250.663 ----> 6.253.062
6.259.831 ----> 6.262.230
6.268.999 ----> 6.271.398
6.278.167 ----> 6.280.566
6.289.734 ----> 6.287.335
125.010.864
160.080.946 ----> 160.080.960
160.080.962 ----> 160.082.993
160.088.758 ----> 160.089.853
210.649.289
216.602.083
220.741.343
225.063.317
234.000.234
238.751.312
240.194.205
242.465.811
246.258.919
250.192.198
253.283.138
254.798.187
255.920.926
258.180.813
260.382.016
262.068.885
264.896.456
266.617.125
267.600.499
269.904.351
271.775.737
274.293.720
275.745.235
276.926.802
278.307.477
279.339.228
279.339.263
281.748.279
283.908.370
285.898.586
287.981.417
288.760.953
290.111.957
291.832.122
293.930.359
295.877.236
297.875.985
300.261.157
302.960.438
305.686.211
307.965.604
310.767.349
313.072.987
315.384.886
317.690.787

[mr_spokk]

You can do much more with professional tools...no SW program will recover all bad sectors.
And there is not a translator issue.

[jono-ats]

These drives tend show media or head degradation over time.

Are you familiar with the Myth of Sisyphus?

[mr_spokk]

Are you familiar with the Myth of Sisyphus?

It's time go down that mountain again and start push

[BlackST]

The problem is that "LASAGNE" are different from "köttbullar" , for unknown reasons...

[mr_spokk]

The problem is that "LASAGNE" are different from "köttbullar" , for unknown reasons...

[Friedrich]

Need data from this drive, but not so much important to spend hundreds of bucks.
I think the sector i have cloned are sufficient to get the data i need, tomorrow i will boot the cloning destination drive into windows and i will see, maybe i will need the help of winhex if MBR or MBT are corrupted.

Do you know what data should be written on hard drive to LBA "0" and LBAs from 63 to 94?
Should it be same for all drives, right? (the faulty drive had only one NTFS partition if i rememer well).
If it's the same for all NTFS partition i can rebuild those sectors on the destination drive by cloning those from a good hdd with NTFS partition, am i right?

[BlackST]

A parte che dovresti saperlo, il fatto è un altro : tutto dipende da cosa c'è in quei settori che il 'povero' MediaTool non riesce a leggere, e da cosa serve. P.s. Il problema è da un'altra parte.

You should know that, and everything depend on what's on the 'poor' MT can't read and what's needed. P.s. The problem is elsewhere.

[BlackST]

Won't work. At least not that way.

[Friedrich]

Head swap?
Doesn't seem to be a head issue to me...
Hey BlackST, i want to ask you if it may possible to clone bad sectors on this hdd with Data Compass.

[BlackST]

Perchè, ne hai uno ?

[BlackST]

Maybe but it is not sure if it should work 100% or partially - should try it "live".