hi all....

I have a 7200.11 with a problem...

I have attached smart log and mhdd log.

I am unable to clone the drive because it will not come rdy,
or I should say it takes a long time to come rdy (see mhdd log).
For example to get the smart log included it took almost 20 mins for the drive to come rdy
and then after the single command it fell off line again.
Once I get an adapter I'll post terminal log....
No grinding or clicking sounds, although I can hear the drive repeatedly repositioning,


Any ideas would be appreciated!

Probably you need to disable relocation processes

ok.....how do I do that in terminal?
Remember F3 firmware not older drive.

Model: ST31000528AS
FW:cc38 upgraded to cc49

Can you tell us what tools you are using? Can you dump your teminal log here and post this one?

_________________
Iorana Haraharaini

This solution has been posted on this forum many times. Search for FIX BUSY STATE.

_________________
Recuperacion De Datos Dominican Republic

ok....here is terminal dump...and ideas will be appreciated.

the end is most interesting.

What were you using to clone?

Well if you check the smart log you will see how many 'pending' bad sectors there are.

Drive is in a bad way and I don't think you are going to be able to clone it safely without hardware imaging tools.

Smart needs to be switched off. You can use Mhdd or Victoria to do this.

Yes.I agree...bad heads/surface but that is not what is causing the drive NOT to come rdy...

Look at new log....this looks like some form of pending bug.

what is between 0x0041F4CD - 0x0042625C cyls on these drives?

that is not a valid command on F3 arch

better info



(DOS)STE NEED: 0x0041F4CD - 0x0042625C
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4CD!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4CE!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4CF!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D0!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D1!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D2!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D3!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D4!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D5!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D6!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D7!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D8!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4D9!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4DA!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4DB!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4DC!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4DD!
(DOS) Read Unrecoverable Error

InitiateMarkPendingReallocateRequest for disc_lba: 0041F4DE!
(DOS) Read Unrecoverable Erro

bad heads lead to pending bug

These models do have issues with relocation causing HDD to run very slowly and causes many read errors. Also, you cannot use LDR for F3 series.

This case I am sure can be resolved quite quickly and safely with the right knowledge and tools. All attempts to DIY this will only result in further deterioration of the media. Even now I guess it is in worse condition than when failure first appeared. The advice given to the op in this thread is more conflicting that helpful. If data is required, consult a professional and get a professional diagnosis on it.

So far it has been suggested that problem is with translator, pending bug and bad heads. Advice given to use LDR is invalid and all the more blind recommendations given will ultimately result in loss of the users data.

Based on what I see here it seems that the surface has some reading errors, and in addition to this there is a error with the relocation process, effectively similar to pending bug in pre F3 series.

for me, I would amend relocation options and perform a secondary diagnostic to identify any other issues before deciding best steps for this.




Not yet, but with repeated DIY attempts im sure it will only be a matter of time.

I've managed to get the drive out of it's reallocate loop (another words it's coming rdy now)...
I am getting unc returns on scan though....I believe this is a translation error...
I've tryied standard m command on T level..It stops before completion.
I believe this to be because of additional bad blocks which are not on G-list P-LIST or NRG.
(i.e. thse blocks are not being taken into consideration during translation table building)

any ideas would be appreciated..


Thanxs guys...

oh..more to add guys.....I can do a seek and read on level 2 and view the results in BUFFER.
No problem.....using CHS addressing...but when I try and use R command on level A
(i.e. use LBA) I get a error...again pointing to translation table problems.

any work arounds appreciated...

UNC errors from start or only after certain position?

You make translator regen with standard 'm' command.



This is right, but no steps were taken to avoid this.

Are you using specific hardware, or standard PC for recovery / testing?

I get UNC from start. but as I said....for now at least the heads check out...

seek, read and H on level T.

What I'm thinking is I get a return block (sector) where the translation process stops at about 10%.
If I can figure out a way to add this block to newly created NRG,P or G list than I can get past that problem...
slowly with alot of work.

The "m" command should not destroy NRG..but the i4,1,22 will (I think).

no..the translator has to be built first before MHDD will even begin to function (ATA) mode.