Seagate Momentus 5400.6

[DR_Ireland]

I got a drive which comes up ready, gives ID and I can even start imaging but after LBA 12787881 returns only read-errors (black blocks). Tried random sectors all over the drive with the same errors.

Model: ST9500325AS / Firmware: 0001SDM1

Any suggestions?

[AJ2008]

I see this problem often and is generally caused by one of two problems:

Bad block that cant be relocated and stops translator loading

Weak head

In the first case you can work out the location of the bad block in hex (138344) and hard relocate

In second case, as far as i remember building head map and turn off head in DE, may work.

[DR_Ireland]

I tried the second solution before that but no luck. I tried to rebuild the translator manually after I got the answer. From terminal on PC3000 using the m0,2,2,0,0,0,0,22 command but after I pressed enter I just got 2 lines like this:

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewri... etc... (only 1 line here)
Successful Format - Elapsed Time 0 mins 0 secs

I might wrong but I think this command is not working with laptop drives. Is it correct?
If yes, then please help me how to solve this problem.

Thank You in advance.

[pcimage]

I'm kinda struggling with one of these too.

I hard relocate the suspect block with G6c,xxxxx (xxx= hex address of bad block) command on level 1 and regen translator, but get the same 0m 0sec response and the block remains and cannot access any LBA beyond that point.

Any more details on the correct procedure anyone?

[AJ2008]

I hard relocate the suspect block with G6c,xxxxx (xxx= hex address of bad block) command on level 1 and regen translator, but get the same 0m 0sec response and the block remains and cannot access any LBA beyond that point.

It seems this only seems to work well on the slim versions with HPxx firmware code, im not sure why. I dont have one with this problem at he moment, ill try dig an old case out when I have time. In meantime, new version of PC3000 is released today, this has support for reading modules, ROM, CP pages, and ID pages. Might be worth playing about with the firmware of a test disk. I have a list of modules that are affected when 0 LBA problem is present, Ill find it and write here. May be good place to start.

[Amarbir[CDR-Labs]]

I'm kinda struggling with one of these too.

I hard relocate the suspect block with G6c,xxxxx (xxx= hex address of bad block) command on level 1 and regen translator, but get the same 0m 0sec response and the block remains and cannot access any LBA beyond that point.

Any more details on the correct procedure anyone?

Sean ,
did you Try Out The New Version Of UDMa On These Please .

Regards

amarbir

[Issam]

I faced same problem with two drives, without success. I think ACE team should look closely to this drive family. I am sure that it is a firmware problem, that ACE team should be able to solve in the newer versions, it is becoming a global problem for this drive family.

[AJ2008]

I think ACE team should look closely to this drive family.

I am sure Ace will develop a solution, but in the meantime it may be best to try and look into this yourself, without depending on hard work of others

[Issam]

I have two exactly same cases, can you tell me please the seps of hard re-allocation.