in terminal make V4 and post here.

_________________
ZeBong
" что случилось в России - останется в России "
" Россия еще раз"

haven't I told you guys that it's not the head, it's another less wide spread bug, which Seagate refuse to make it public.

There is an error in translator regenerating making only partial translation. This means, all sectors before the error was encountered are accessible, all sectors after the error occurred remain inaccessible.

It is not 'another less wide spread bug', it is a result of incomplete repair of the 0 LBA fault.

Hi
meow did u try to read with "backward"Direction ? create Head Map and try again.

The problem is not that the reading method is wrong, it is that the specific LBA cannot be accessed. I will try to explain in a way not to confuse: The HDD has to translate between CHS, which the HDD uses for addressing, to LBA, which is the method of addressing we reference. While there is an error here the HDD does not know the appropriate CHS location for each LBA - effectively it does not know where a requested sector physically resides.

Professional tools are needed, but are useless without knowledge of the problem and knowledge of Seagate Terminal commands...

Zebong is right, show V4 info...

Thanks for all the input and special appreciation to hddguy who save my day.

After relocating the bad block then rebuild translator, data was copied.

Hddguy. Owe you this one

When a firmware has a buffer overflow issues usually it overruns the max buffer, for example, by 2 bytes you get busy symptom how ever a fewer wide spread problem might be that it overrun the buffer by 16 bytes and overwrites the translator overlay data Since. in my own case and some other guys it happened as a first problem before doing any LBA REPAIR so it could not be the result of that. How ever people might mistaken
this by the usually wide spread one and apply the fix making it worse.

I have a drive with the same problem. What tool did you use to relocate the bad sector?

You'll need terminal access to the drive. This can be via commercial tools or a homemade version using hyperterminal or similar.

Hello. I'm digging this old thread. I have the same question as jpllal. I've got a failed 7200.11 disk, detected with 0 LBA size. But its behavior differs a little from what i've seen in forums. It takes command well with terminal, command N1 does NOT return a message as "Unable to load Diag Overlay", but it fails later at m0,2,2,0,0,0,0,22 with :

Error 1008 DETSEC 0000500E Process Defect List Error
R/W Sense 00000002, R/W Error 841C0087, List Offset 00000000, File Error 00000001

Is a sector bad preventing the command to succeed ?

The disk doesn't make strange noise, but stays busy a little more than normal before returning to idle state (and then is detected, serial is ok, LBA is 0, smart is empty).

Also, I've seen in a russian forum that they use V1 then V4 before m0,2,2,0,0,0,0,22, would it be any help ? I have some difficulties believing this disk is dead...

Thanx.