It was Seagate Momentus Thin ST500LT012 Firmware 0001 ( Yarra 5400)

When I got disk it was detected in UDMA with 0mb capacity .
I tried 0mb solution in udma but got error HDD capacity restrict , I checked head resistance as well.
So I decided to use magic spell ( m0,2,2,0,0,0,0,22) and Lo & Behold drive was showing full capacity,
All firmware modules can be read without errors.
but while accessing data I am getting read errors.
What should I do now ?

Did you save original SA before these operations?

_________________
http://www.alfadatarecovery.com

I can't see full capacity on either photos...
If you have drive showing the full model, firmware and capacity....and you can't read user area, my first search should be on translator.

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

BTW, on the pictures I see no full capacity. Drive isn't initialized completely. What about ctrl+x?

_________________
http://www.alfadatarecovery.com

Hi thanks all of you for valuable suggestions.

Yes martin I always take backup before doing any changes.
Terminal messages show translator related issue ,but all modules can be read perfectly.
As model /capacity was not visible ,I have taken few snaps of terminal and other tests.

m0,2,2 etc command does not take into account information in the defect lists; not a good option for modern Seagate disks unless there is no other option. It is necessary to now rebuild the translator as I presume that data after a certain LBA value is no longer readable? If you have a full backup of the SA before m0,2,2 was run then it will help. What version of PC3000 are you using?

_________________
CDR - Manchester Data Recovery Services
0161 408 4857
http://www.cheadledatarecovery.co.uk/

DR is such complex thing

even erasing alt list is dangerous as not all sectors are added in translator, whatever you do in ultimate technical sense ( from guru's eyes) its not correct .
as cheadledatarecovery has suggested I will restore SA backup first. But then detection will also go and again disk will become busy.
what should I do now ?

Did you look at V40 before m0,2,2? Look at your backups if NRG has entries. Or Restore everything and check V40. Then run m0,6,3 instead.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

Was anybody working with this drive before you? If you save all original modules, so just write back original ~002B module (FID 28).

_________________
http://www.alfadatarecovery.com

Hi Martin
I have confirmed no one has worked on the drive,

I have restored backed up modules then drive again lost drd dsc and become busy.
I tried to recover translator from LBA 0 , process continued till few thousand sectors were left. But disk gave FORK errors and reading was by single sector.
So I stopped this process.
After that disk again got detection with full capacity , but still disk was giving read errors.
So I tried regenerate translator instead of recover translator. Still no normal access to sectors is established.
Somehow this has something to do with translator.
Now I will run m0,6,3 and report outcome.

Write back original module 2B, after that T>F,,22, power off - power on, ctrl+x and bring report here.

_________________
http://www.alfadatarecovery.com

Thanks Martin your diagnostics & suggestions were right. I did as you suggested ,( I just opened Module 2 B and saved it.
Then I run m0,22 & disk gave smooth access.
I was able to recover 13.3GB photos of customers daughter , I did not charged customer for this recovery.
All credit goes to Martin . A big Thank you