Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Re: 7200.12 cloning problem

March 21st, 2013, 11:02

'm' command rebuilds translator based on specific lists such as slip lists. It does NOT take into account defects added to NRG, as these defects in NRG have an influence on Translator, rebuilding translator without NRG info will result in bad translator.
But UNC from starting sector is not common with this issue, maybe there is still some issue elsewhere.

Re: 7200.12 cloning problem

March 21st, 2013, 13:03

if it's not translator how do you explain access via CHS but not LBA?

Re: 7200.12 cloning problem

March 21st, 2013, 13:28

I never said it wasnt translator, just that its not common to start from first sector and maybe there is other issue. Because you rebuild translator without checking non resident list almost surely you have partial translator damage. Im just wondering if there are other issues also.

Re: 7200.12 cloning problem

March 21st, 2013, 15:12

Thinking of doing a head swap...what you think?

Re: 7200.12 cloning problem

March 25th, 2013, 4:01

hddguy....

ok..I have it reading until 5,000,000 aprox LBA...then it just stops...all unc errors.
This classic translator problem....what can I do? I have tried the leonardo method without success..
I think the heads are really bad...if I change them will I be able to rebuild translator you think?
The NRG is intact from what I can tell.


any help appreciated.
I just need this last step and I think I have it.

thanxs

Re: 7200.12 cloning problem

March 25th, 2013, 16:02

Leonardo method:
Code:
1. Backup all modules, etc
2. Clear Altlist = Glist (i4,1,22)
3. Power off/on
4. Scan drive with MHDD or search manually with "Sector View", etc. STOP and RECORD (write on paper) FIRST PROBLEM LBA
5. Make sure drive add this LBA to Glist you can check it with V4 command
6. REGENERATE TRANSLATOR ---- BUT use command to USE AltList: m0,6,3,,,,,22
7. REPEAT #4 --> 6

Re: 7200.12 cloning problem

March 25th, 2013, 16:35

Spildit
I haven't tried it yet, still collecting some more info. There are many similar cases, even here on hddguru.

Re: 7200.12 cloning problem

March 25th, 2013, 17:49

Yes..that's the method pushed by SD..it suppose to work....
I think my drive needs a head swap before it has a chance.

Re: 7200.12 cloning problem

March 25th, 2013, 21:07

lastest update...any comments guys?
Attachments
headstest.txt
(4.36 KiB) Downloaded 558 times

Re: 7200.12 cloning problem

March 25th, 2013, 21:45

Head 1 looks sick in those results IMHO :( (and head 3 doesn't look great either, though it's better than the results from head 1)

Re: 7200.12 cloning problem

March 25th, 2013, 23:30

yeah..none of them look great...I have doner drive on way...
As pre question----

Will bad heads cause translation generation problems?

Re: 7200.12 cloning problem

March 26th, 2013, 6:46

Heads still need to read sectors at SA, so if head is bad reading (and writing) error will prevent repair. But if there was error at heads it would be detected during initialize and heads will knock and spindle stop. So here SA does read and I guess head change now will probably only make things worse.

Re: 7200.12 cloning problem

March 26th, 2013, 12:23

I get this when trying reallocate



F3 1>G6C,9A64
vvvvvvvvvv
Hard reallocate LBA status:error = 00000002:04808781

F3 1>
any ideas?
Post a reply