5400.5 problem

[derp]

Hi,

Anybody experienced this :

Drive reads perfectly from sector 0 to 25 xxx xxx (25MIL+) with MHDD scan and others.

Not a single sector after an exact LBA (25 xxx xxx) will read at all.

zone table ? adapatives ?

Seen more than one similar drive with this symptom.

[dmarques]

Hi,

I already had some with that problem.
Have you tried to regen translator?

[BlackST]

First thought goes to translator... agree. Can you read completely and access the SA ?

[derp]

Thanks for reply, translator regen, I don't have anything like pc udma,
but use terminal commands. Yes, SA can be read easily.

Need to know if regen of 5400.x , 7200.11 varies for models, don't want
to do wrong m0,,,,,,,,,,,,, command

[Doomer]

that's translator problem
somebody tried to recalc it

[derp]

Thanks for reply, translator regen, I don't have anything like pc udma,
but use terminal commands. Yes, SA can be read easily.

How did you read it ?

Terminal - as the normal way.

[derp]

that's translator problem
somebody tried to recalc it

Thanks Doomer,
not sure if someone else worked on this drive. Will check with the owner.

Be interesting to know what can go wrong with regen (m0)
for 5400.x drives and if commands vary for different drives.

[BlackST]

Different arch = different command. Careful!

[derp]

Different arch = different command. Careful!

Agreed, just applied 7200.11 m0 command to good working 5400.5 and
got the same result.
Different family different command - different command options, and
no help for commands. Who's got this for 5400.5 ??

Code:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewr
ite Retries = 00C8
User Partition Format   0% complete, Zn 00, Pass 00, SoftCnt:0, SoftPBA:0, SoftE
rrCode:0, ZnReWrite:0, ZnReCertify:0, IsRd:0, HardPBA:0

User Partition Format Successful - Elapsed Time 0 mins 00 secs
Total Grown Defects:0 XFatalBlkAddr_PBA:0


[Doomer]

Be interesting to know what can go wrong with regen (m0)
for 5400.x drives and if commands vary for different drives.

many things can go wrong
from my experience such "things" happen on all 5400.5, 5400.6 and 7200.3 drives

[Doomer]

Agreed, just applied 7200.11 m0 command to good working 5400.5 and
got the same result.

Congratulations
If you didn't backup SA before that will be realy hard to fix the drive back

[derp]

Anyone here who can fix such situation ? - location UK.

[derp]

Owner confirmed original drive was sent to other DR company.
Owner reported that drive was not detecting at all.
So, based on this info if true, 5400.5 has same problem as 7200.11.

Does anyone know if pc3000 has included support for 5400.5 models to do
translator regen?

[HDD Spaz]

Why don't you contact the other company see what they did to it? Out of interest, was it a large company and where are they based?

[BlackST]

If he has a SA backup it's not so problematic, if not...it's the realm of data reconstruction.

[derp]

I do appreciate the responses, however my question is

Does pc3000 udma support model 5400.5 ?

I am not expecting anyone to list the commands for 5400.5, these will be found shortly,
but does anyone know the answer to the following question :

Does pc3000 udma support model 5400.5 ?

thanks

[Doomer]

derp, if your question is "Can PC3000 UDMA fix this drive?" the answer will be - no

[derp]

derp, if your question is "Can PC3000 UDMA fix this drive?" the answer will be - no

Thanks, I thought so. Just have to dig some more.

[BlackST]

If SA is gone, I think you can only put a fresh Fw and selfscan... At least you have the drive (not the data).

[derp]

Hi BlackST,

Which parts of SA, in your professional opinion, do you know
are modified by incorrectly using m0 for 7200.11 for 5400.5 ?

Are you able to restore 5400.5 drive (with data) as in this case ?