It turned out that hdd from the previous post
http://forum.hddguru.com/seagate-serial-number-change-5400-t22908.html
had damaged head.
The heads have been changed and we started to clone it.
We started from LBA 200 mln becouse we noticed a lo of slow/damaged sectors in LBA 0-200mln.
When we finished lba 200-end , we started lba 0-1mln.
It turned out it was heavily damaged (2% bads).
Then we wanted to clone lba 150-200mln. The disc started to get BUSY (becouse of UNCR ?) more frequently and cloning has been impossible.
So we returned do the beginning and cloned lba 1-2mln. It get BUSsier every minute.
The we scanned it with MHDD (2xF4) looking for udamaged area in 2-200mln. So we jumped (arrow up , arrow down) through it.
We found that 150-175mln looks promising. So we started to clone.
In DMDE the area turned out to be unreadable. We started to scan 150-175 again in MHDD and now it was unreadable (UNC, 'x' and '!' in MHDD).
We checked the area we cloned first (200-end) and to our surprise it was unreadable too.
We thought that head/heads were dead although lba 0-1mln looked the same (readable, with some bads).
We put the heads to hd it came from (donor) and it worked like a charm.
So we put them back into our hd.
In terminal in T>V4 it shows that bads are distribiuted equally on the heads.

Question: What should we do get access and copy these lba 2-200 ?

After a few attempts to clone, the hdd was identified with 0 LBA.
We used 'standard' solution for .11 series, and it worked.
Now we have to figure out how to clone LBA 2-200 mln.

Is it possible there is something wrong with PCB ?

Is degradation of over 90% of area in a few minutes possible (heads are working good) ?

I've found something
5400-problem-t12166-40.html
Maybe it's the same problem.

Is it possible to fix it ?

So many Gurus and no answer ?

possibly problem with the translator. PC3K has a momentus .6 translator regeneration / translator restoration function that helps in this case.

Is there other way to solve it ?

There's link
http://yura.projektas.lt/files/seagate/s3ku.html
with information of translator regeneration.

m0,2,2,,,,22 2= 0010
m0,2,2,0,0,0,0,22 2 = 0010
m0,3,2,,,,22 3= 0011
m0,3,2,0,0,0,0,22 3 = 0011
m0,6,2,,,,22 6= 0110
m0,6,2,0,0,0,0,22 6= 0110
m0,a,2,,,,,22 a= 1010
m0,a,2,0,0,0,0,22 a=1010
m0,e,2,,,,,22 e=1110
m0,e,2,0,0,0,0,22 e=1110
m0,f,2,,,,,22 f=1111
m0,f,2,0,0,0,0,22 f=1111

What's the difference between them ?
Can they be used for Momentus ?

The difference is in how certain critical firmware elements are rebuilt.

Whatever you do, do NOT randomly issue these commands as they can make the data on the drive inaccessible, forever.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

Which one should i use ?

I think there are confused or NO ideas about "translator regeneration" , what "translator" does and some other things , unfortunately this cannot be discussed here.

Anyway DON'T play with "random" command or you'll more or less f**k data.

I don't want to "play" with command. I'm looking for the correct one or someone who knows it and wants to share it.

Use the most famous command in the w.w.w., though I think you probably already tried, no?

However, based on your description, the likely reason the drive init. with 0GB at this point is because the heads are damaged.

Does the drive run smoothly with no clicks when powered on?

In terminal, what does the heads test show?

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts