Seagate LBA = 0 and drive ID. I have fixed this with pc3k and received the drive ID an LBA back on the drive.

When cloning the drive I can get data from 0 to 94 000 000 then nothing. Did a hardware reset on the drive and the problem came back again. Tried to fix it again and it worked. Same issue when cloning and hardware reset. Now on third time I get this error in log and can not get the LBA fixed again on this drive.

F3 T>m0,2,2,0,0,0,0,22

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

F3 T>V4

Unable to load Diag Overlay

F3 T>

i fix the id but not the capacity
on capacity m0,2,2,0,0,0,0,22 i have this errors



Can anyone help me out on this one please or am I missing something on this fix. It is easy solution and easy fix with pc3k and I am not sure why this drive is giving me problems on this one.\


Thanks

_________________
Iorana Haraharaini

Looks like dead heads

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

Thank you so much. I will check this one out and see if heads need to be changed out.

_________________
Iorana Haraharaini

You say that you can get data until sector 94 000 000.

Afther this you can not copy any sector ?

Can you build head maps and see wich heads you can read it ?

The strange is this :

F3 T>V4
Unable to load Diag Overlay
F3 T>

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

No I can not build a head map on this one now. I only get errors. There might be problems in the heads now or maybe a head is stuck to the platter on this one.

_________________
Iorana Haraharaini

Maybe just a single head is OK? with this message in my experience it is usually associated with a head fault

Im having the exact same problem .I also could read first few sectors .probebly you also get not effected on the serial number check at seagate site . I think the overlay module on rom is not mach with the hardware or corupted. if there is a copy on SA ,or you can find a donor on pc3k database try that.

nope

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

would be please explain more?

just take it as a fact please or you can think that I'm wrong (it also happens sometimes)

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

No it is head problems on this drive. Doomer is right on this one. Thanks

_________________
Iorana Haraharaini

NOt that I think you are wrong reason for asking was solely to learning about the subject .

You mean in your case your not getting "unable to load diag overlay" when head is not connected?
would be nice if you could post the final outcome .

Thanks.

Persia2500, you are persistent aren't you?

Ok, let's see some facts
In the poehere's case drive was able to work a little and then stopped working showing unable to load overlays message which means drive WAS able to read overlays before and CANNOT now. So it is general reading problem isn't it? And it's very possible that it's heads problem
In your case you saying you are able to read some sectors, that would mean you don't have general reading problem, so it is unlikely heads
And the conclusion is - it is NOT exactly the same problem
So I chewed it for you and you just need to swallow and digest it (I mean find the real problem)

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

Doomer: Thanks. Now I know my own case might have been a dead head too. About the reading mine was also stop reading those few sectors after second repair.

In our country being persident is not some thing you ever wish for.

ahum is that a political remark?

_________________
All went well until I plugged the drive in.

ummmm...sorry yes however remotely ...
dont know how to delete it.

better left at the door...

_________________
All went well until I plugged the drive in.

I had similar problem but poehere seems to go further as my one stop around 92,000,000.

That occurs after applying solution for "HDD Lock "LED:0000CC".

Definitely not a head problem because I had already swapped in new head stack with same result.

This was the second one I encounter this week.

Acelab told me it was translator problem and may only be solved in future release, not now.

wait...