MultiDrive – free backup, clone & wipe disk utility from Atola Technology

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 8 posts ] 
Author Message
 Post subject: 7200.12 now ok but can't access data
PostPosted: June 18th, 2014, 7:34 
Offline
User avatar

Joined: October 30th, 2007, 17:58
Posts: 464
Location: Egypt
Hi all
i have ST31000528AS 7200.12 it was busy . i solve it in normal way all are ok . but i can't access any sector of the drive
any help please ?

_________________
Tawfeek Mokhtar
http://alsafwapc.net
Alsafwa Data Recovery Egypt


Top
 Profile  
 
 Post subject: Re: 7200.12 now ok but can't access data
PostPosted: June 18th, 2014, 7:40 
Offline

Joined: August 18th, 2010, 17:35
Posts: 3669
Location: Massachusetts, USA
have to check heads (to make sure are ok for translator work) and then translator

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


Top
 Profile  
 
 Post subject: Re: 7200.12 now ok but can't access data
PostPosted: June 18th, 2014, 7:41 
Offline
User avatar

Joined: June 3rd, 2014, 14:18
Posts: 79
Location: Mitakihara - Japan
Greetings !
Do you have the latest version of PC-3000 UDMA or EXPRESS with you ?
If so you can try to fix the translator with the fork method.
When you attempted to fix the bsy problem on the 7200.12 drive you might have ended up with the partial access problem due to the non-resident g-list.
Also you should do a head test.


Top
 Profile  
 
 Post subject: Re: 7200.12 now ok but can't access data
PostPosted: June 18th, 2014, 8:17 
Offline
User avatar

Joined: October 30th, 2007, 17:58
Posts: 464
Location: Egypt
labtech wrote:
have to check heads (to make sure are ok for translator work) and then translator

thanks for reply
head test

F3 T>/7

F3 7>X

Head 00 Resistance 00E6
Head 01 Resistance 0183
Head 02 Resistance 00F8
Head 03 Resistance 0142


Madoka wrote:
Greetings !
Do you have the latest version of PC-3000 UDMA or EXPRESS with you ?
If so you can try to fix the translator with the fork method.
When you attempted to fix the bsy problem on the 7200.12 drive you might have ended up with the partial access problem due to the non-resident g-list.
Also you should do a head test.


thanks for your reply
the recover translator report is

G-List erase...

Translator regeneration...
Result.................................. : Ok

HDD ID reading...
Detecting defects hiding cmd type...
G-List erase...

Start scanning...
"Fork" searching: 0 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1D3(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1D3(1)! Tech state 0x72, 0x03110081
LBA : 0
"Fork" searching: 1 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1D4(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1D4(1)! Tech state 0x72, 0x03110081
LBA : 1
"Fork" searching: 2 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1D5(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1D5(1)! Tech state 0x72, 0x03110081
LBA : 2
"Fork" searching: 3 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1D6(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1D6(1)! Tech state 0x72, 0x03110081
LBA : 3
"Fork" searching: 4 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1D7(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1D7(1)! Tech state 0x72, 0x03110081
LBA : 4
"Fork" searching: 5 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1D8(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1D8(1)! Tech state 0x72, 0x03110081
LBA : 5
"Fork" searching: 6 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1D9(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1D9(1)! Tech state 0x72, 0x03110081
LBA : 6
"Fork" searching: 7 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1DA(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1DA(1)! Tech state 0x72, 0x03110081
LBA : 7
"Fork" searching: 8 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1DB(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1DB(1)! Tech state 0x72, 0x03110081
LBA : 8
"Fork" searching: 9 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1DC(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1DC(1)! Tech state 0x72, 0x03110081
LBA : 9
"Fork" searching: 10 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1DD(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1DD(1)! Tech state 0x72, 0x03110081
LBA : 10
"Fork" searching: 11 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1DE(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1DE(1)! Tech state 0x72, 0x03110081
LBA : 11
"Fork" searching: 12 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1DF(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1DF(1)! Tech state 0x72, 0x03110081
LBA : 12
"Fork" searching: 13 - 1953525167
Verify sectors ext error Device error detected "UNC"
"Right fork", LBA = 00000000013, pattern 0x00 (TNE!)
Defects hiding (P)...
Moving defects to Slip-List...
Translator regeneration...
"Fork" searching: 13 - 1953525167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 0:0:1E1(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 0:0:1E1(1)! Tech state 0x72, 0x03110081
LBA : 13
"Fork" searching: 14 - 1953525167
Verify sectors ext error Device error detected "UNC"
"Right fork", LBA = 00000000014, pattern 0x00 (TNE!)
Defects hiding (P)...
Moving defects to Slip-List...
Translator regeneration...
"Fork" searching: 14 - 1953525167
Verify sectors ext error Device error detected "UNC"
Translation "fork" direction detection ambiguity!
Correct it manually!
LBA : 14
----------------------------------------------------------
just 2 defects and i add them

_________________
Tawfeek Mokhtar
http://alsafwapc.net
Alsafwa Data Recovery Egypt


Top
 Profile  
 
 Post subject: Re: 7200.12 now ok but can't access data
PostPosted: June 18th, 2014, 8:40 
Offline
User avatar

Joined: October 30th, 2007, 17:58
Posts: 464
Location: Egypt
another note
every time i clear NRG list and ALT list and samrt then translator after pw off/on the NRG come with the same 7 entries
----------------------------------
F3 T>V40
Nonresident GList 7 entries returned
Total entries available: 7
PBA Len Flags Phy Cyl Hd PhySctr SFI
3A36CCF2 6 0 19588 3 BB 9B2E8
3A36CD22 6 0 19588 3 EB A1363
3A38539E 6 0 19589 3 351 D3745
3A3853F1 6 0 19589 3 3A4 DDE01
74732C0E 36 0 3AAD9 3 73 1A8A1
74732C60 16D 0 3AAD9 3 C5 24D9D
74732E20 236 0 3AAD9 3 285 5D323

F3 T>
Rst 0x20M
(P) SATA Reset

ASCII Diag mode

F3 T>V40
Nonresident GList 0 entries returned
Total entries available: 0
PBA Len Flags Phy Cyl Hd PhySctr SFI

F3 T>

_________________
Tawfeek Mokhtar
http://alsafwapc.net
Alsafwa Data Recovery Egypt


Top
 Profile  
 
 Post subject: Re: 7200.12 now ok but can't access data
PostPosted: June 18th, 2014, 8:45 
Offline
User avatar

Joined: June 3rd, 2014, 14:18
Posts: 79
Location: Mitakihara - Japan
Hello again !
Are you using the latest version of PC3K ? Because the latest version have considerable changes to the fork method code to make it work better...
Assuming you have the latest version i would clear the g-list and slip list and try again. Also sometimes errors to the p-list can cause translator issues. You can fix thd p-list with pc3k...
Read the last lines of your log, pc3k couldn't fix the translator properly and asks you to execute a manual task.
If you have the Salvation data Seagate tool the one click fix for the partial access problem might solve the problem as well, assuming there is no problem with the p-list.


Top
 Profile  
 
 Post subject: Re: 7200.12 now ok but can't access data
PostPosted: June 18th, 2014, 9:15 
Offline
User avatar

Joined: October 30th, 2007, 17:58
Posts: 464
Location: Egypt
thanks a lot MR.Madoka . i will

_________________
Tawfeek Mokhtar
http://alsafwapc.net
Alsafwa Data Recovery Egypt


Top
 Profile  
 
 Post subject: Re: 7200.12 now ok but can't access data
PostPosted: June 18th, 2014, 9:39 
Offline
User avatar

Joined: June 3rd, 2014, 14:18
Posts: 79
Location: Mitakihara - Japan
tawfeek_mokhtar wrote:
thanks a lot MR.Madoka . i will


No problem !
I've send you a private message ! Please tell us if it helped/worked out !
Good luck.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 8 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 15 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group