All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 17 posts ] 
Author Message
 Post subject: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 17th, 2017, 18:16 
Offline

Joined: April 10th, 2007, 9:53
Posts: 315
Had a Hitachi HTS725050A7E630 in that was able to slowly image at first. It's a friend of mine and they stated that it got slower and slower and eventually would not show up on their system and would click intermittently. It sounded as though it was a failed set of heads. I connected it to DDI and it calibrated and was recognized. Started cloning and it was extremely slow. It imaged a few thousand sectors and started clicking. I shut it off immediately. I tried to power it up again, but it started to click right away so I shut it off.

Got a parts drive that is identical in every way, just manufactured about 8 months later. Swapped the heads and the drive sounds perfectly normal. I can put it up to my ear, hear it make the normal calibration sound and it becomes Ready. When I refresh the screen, it errors out and does not identify. I hook it up to PC3K and it's the same thing. I went ahead and backed up the ROM and whatever modules were available for backup while I was in there. Drive sounds fine, just won't recognize by any system. Any ideas what could cause this, or anything else I should check out on it?


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 17th, 2017, 20:22 
Offline

Joined: March 19th, 2015, 15:01
Posts: 1261
Location: isreal
http://blog.acelaboratory.com/pc-3000-h ... lator.html


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 18th, 2017, 5:36 
Offline

Joined: October 24th, 2014, 4:57
Posts: 205
Location: Remote Raid Help on planet Earth
Not all the heads had pass through W/R test.

_________________
http://www.alfadatarecovery.com


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 18th, 2017, 9:28 
Offline

Joined: April 10th, 2007, 9:53
Posts: 315
It seems as though the most critical modules are being read. There are some read errors in some of the subsequent modules.

Code:
NV-RAM report
Loaded.................................. : Yes
ID...................................... : E2PR
mu-code................................. : 2002GH2OB420
FW Ver (part 2)......................... : ³2
Heads................................... : 2
Head map................................ : 0 1 F F F F F F F F

Used module table
-----------------

Report on module USAG,  "Main module table"
ABA..................................... : 3F0000004
Length (sectors)........................ : 6
Loaded.................................. : Yes
Identified.............................. : Yes




--------------------------------------------------------------------------------------------------------------------------------
ID  : Copy : Importn.:      ABA     :      ABA     :  Size :  Read :  Size  : Address in : Read :   Hdr : Description
     :      :         :              :  (original)  : (sect): (sect): (byte) :     RAM    :      :       :           
--------------------------------------------------------------------------------------------------------------------------------
RPSH :   0  :     B   :    3F0000000 :    3F0000000 :    4  :     4 :   2048 :  00000000  :  Yes :    Ok : SA marker
RPSH :   1  :     B   :    3F0100000 :    3F0000000 :    4  :     4 :   2048 :  00000000  :  Yes :    Ok : SA marker
USAG :   0  :     B   :    3F0000004 :    3F0000004 :    6  :     6 :      0 :  00000000  :  Yes :    Ok : Main module table
USAG :   1  :     B   :    3F0100004 :    3F0000004 :    6  :     6 :      0 :  00000000  :  Yes :    Ok : Main module table
RAMI :   0  :         :    3F000000A :    3F000000A :  128  :   128 :  57848 :  00019E08  :  Yes :    Ok :
RAMI :   1  :         :    3F010000A :    3F000000A :  128  :   128 :  57848 :  00019E08  :  Yes :    Ok :
RAM0 :   0  :     B   :    3F000008A :    3F000008A : 1024  :  1024 : 524288 :  0086C600  :  Yes :    Ok : Code module
RAM0 :   1  :     B   :    3F010008A :    3F000008A : 1024  :  1024 : 524288 :  0086C600  :  Yes :    Ok : Code module
PSHT :   0  :    Ad   :    3F0001400 :    3F0001400 : 1600  :  1600 : 357640 :  00800800  :  Yes :    Ok : P-List module
PSHT :   1  :    Ad   :    3F0101400 :    3F0001400 : 1600  :  1600 : 357640 :  00800800  :  Yes :    Ok : P-List module
RDMT :   0  :    Ad   :    3F0001A40 :    3F0001A40 :  256  :   256 :  40960 :  00908600  :  Yes :    Ok : G-List module
RDMT :   1  :    Ad   :    3F0101A40 :    3F0001A40 :  256  :   256 :  40960 :  00908600  :  Yes :    Ok : G-List module
RPOP :   0  :         :    3F0000498 :    3F0000498 :    2  :     2 :    420 :  000848CC  :  Yes :    Ok :
RPOP :   1  :         :    3F0100498 :    3F0000498 :    2  :     2 :    420 :  000848CC  :  Yes :    Ok :
SECI :   0  :     B   :    3F0008BA0 :    3F0008BA0 :    3  :     3 :   1536 :  0092C000  :  Yes :    Ok : Security information module
SECI :   1  :     B   :    3F0108BA0 :    3F0008BA0 :    3  :     3 :   1536 :  0092C000  :  Yes :    Ok : Security information module
SECB :   0  :         :    3F0008BA3 :    3F0008BA3 :    3  :     3 :   1536 :  0092C000  :  Yes :    Ok :
SECB :   1  :         :    3F0108BA3 :    3F0008BA3 :    3  :     3 :   1536 :  0092C000  :  Yes :    Ok :
ZONE :   0  :    Ad   :    3F0000566 :    3F0000566 :  128  :   128 :  34816 :  0091D000  :  Yes :    Ok : Zone allocation table module
ZONE :   1  :    Ad   :    3F0100566 :    3F0000566 :  128  :   128 :  34816 :  0091D000  :  Yes :    Ok : Zone allocation table module
SRVP :   0  :     B   :    3F0000494 :    3F0000494 :    4  :     4 :    720 :  00925800  :  Yes :    Ok :
SRVP :   1  :     B   :    3F0100494 :    3F0000494 :    4  :     4 :    720 :  00925800  :  Yes :    Ok :
SRVM :   0  :    Ad   :    3F00004A3 :    3F00004A3 :   30  :    30 :   6466 :  00926000  :  Yes :    Ok : Module contains cylinder defects table
SRVM :   1  :    Ad   :    3F01004A3 :    3F00004A3 :   30  :    30 :   6466 :  00926000  :  Yes :    Ok : Module contains cylinder defects table
CHNM :   0  :    Ad   :    3F00004C1 :    3F00004C1 :  165  :   165 :  32752 :  00915000  :  Yes :    Ok :
CHNM :   1  :    Ad   :    3F01004C1 :    3F00004C1 :  165  :   165 :  32752 :  00915000  :  Yes :    Ok :
IDNT :   0  :     B   :    3F0000492 :    3F0000492 :    2  :     2 :    584 :  0092BC00  :  Yes :    Ok : HDD ID data module
IDNT :   1  :     B   :    3F0100492 :    3F0000492 :    2  :     2 :    584 :  0092BC00  :  Yes :    Ok : HDD ID data module
SMRT :   0  :     B   :    3F0008B8E :    3F0008B8E :    8  :     8 :   4096 :  0092D400  :  Yes :    Ok : S.M.A.R.T. module
SMRT :   1  :     B   :    3F0108B8E :    3F0008B8E :    8  :     8 :   4096 :  0092D400  :  Yes :    Ok : S.M.A.R.T. module
SERL :   0  :     B   :    3F0008B89 :    3F0008B89 :    3  :     3 :   1536 :  0092CE00  :  Yes :  Skip : S.M.A.R.T. error log module
SERL :   1  :     B   :    3F0108B89 :    3F0008B89 :    3  :     3 :   1536 :  0092CE00  :  Yes :  Skip : S.M.A.R.T. error log module
IOPS :   0  :         :    3F0008B9E :    3F0008B9E :    2  :     2 :   1024 :  0092C600  :  Yes :    Ok :
IOPS :   1  :         :    3F0108B9E :    3F0008B9E :    2  :     2 :   1024 :  0092C600  :  Yes :    Ok :
SSLD :   0  :         :    3F0008B8C :    3F0008B8C :    2  :     2 :   1024 :  0092E600  :  Yes :    Ok :
SSLD :   1  :         :    3F0108B8C :    3F0008B8C :    2  :     2 :   1024 :  0092E600  :  Yes :    Ok :
SCTH :   0  :         :    3F0008BA6 :    3F0008BA6 :    1  :     1 :      0 :  00000000  :  Yes :    Ok :
SCTH :   1  :         :    3F0108BA6 :    3F0008BA6 :    1  :     1 :      0 :  00000000  :  Yes : Error :
FEAT :   0  :         :    3F0008B96 :    3F0008B96 :    8  :     8 :    376 :  00912600  :  Yes :    Ok :
FEAT :   1  :         :    3F0108B96 :    3F0008B96 :    8  :     8 :    376 :  00912600  :  Yes :    Ok :
CNFG :   0  :         :    3F0000490 :    3F0000490 :    2  :     2 :    658 :  00913600  :  Yes :    Ok :
CNFG :   1  :         :    3F0100490 :    3F0000490 :    2  :     2 :    658 :  00913600  :  Yes :    Ok :
WWNM :   0  :         :    3F00005E6 :    3F00005E6 :    1  :     1 :     54 :  0092BF00  :  Yes :    Ok :
WWNM :   1  :         :    3F01005E6 :    3F00005E6 :    1  :     1 :     54 :  0092BF00  :  Yes :    Ok :
RPSP :   0  :         :    3F000049A :    3F000049A :    8  :     8 :   2360 :  00913A00  :  Yes :    Ok :
RPSP :   1  :         :    3F010049A :    3F000049A :    8  :     8 :   2360 :  00913A00  :  Yes :    Ok :
SPTR :   0  :         :    3F000048A :    3F000048A :    2  :     2 :      0 :  00000000  :  Yes :    Ok :
SPTR :   1  :         :    3F010048A :    3F000048A :    2  :     2 :      0 :  00000000  :  Yes :    Ok :
ABLP :   0  :     B   :    3F00004A2 :    3F00004A2 :    1  :     1 :    180 :  00914A00  :  Yes :    Ok :
ABLP :   1  :     B   :    3F01004A2 :    3F00004A2 :    1  :     1 :    180 :  00914A00  :  Yes :    Ok :
DBGC :   0  :         :    3F000048C :    3F000048C :    4  :     4 :   1024 :  00914C00  :  Yes :    Ok :
DBGC :   1  :         :    3F010048C :    3F000048C :    4  :     4 :   1024 :  00914C00  :  Yes :    Ok :
ALSM :   0  :         :    3F00005E7 :    3F00005E7 :    4  :     4 :   2048 :  0092B000  :  Yes :    Ok :
ALSM :   1  :         :    3F01005E7 :    3F00005E7 :    4  :     4 :   2048 :  0092B000  :  Yes :    Ok :
ATIR :   0  :         :    3F00005EB :    3F00005EB :   20  :    20 :   4246 :  00928800  :  Yes :    Ok :
ATIR :   1  :         :    3F01005EB :    3F00005EB :   20  :    20 :   4246 :  00928800  :  Yes :    Ok :
AVZN :   0  :         :    3F00010D5 :    3F00010D5 :    1  :     1 :      4 :  00000000  :  Yes : Error :
AVZN :   1  :         :    3F01010D5 :    3F00010D5 :    1  :     1 :      4 :  00000000  :  Yes : Error :
CGDF :   0  :         :    3F0008BA7 :    3F0008BA7 :    8  :     8 :      4 :  0092EA00  :  Yes :    Ok :
CGDF :   1  :         :    3F0108BA7 :    3F0008BA7 :    8  :     8 :      4 :  0092EA00  :  Yes :    Ok :
AMPM :   0  :     B   :    3F0001003 :    3F0001003 :    1  :     1 :      0 :  00000000  :  Yes : Error : Factory tests log module (AMPM)
AMPM :   1  :     B   :    3F0101003 :    3F0001003 :    1  :     1 :      0 :  00000000  :  Yes : Error : Factory tests log module (AMPM)
RDM1 :      :    Ad   :    3F0001A40 :    3F0001A40 :   80  :    80 :      0 :  00000000  :  Yes :    Ok : G-List module (RDM1 - reference to RDMT)
RDM2 :      :    Ad   :    3F0101A40 :    3F0101A40 :   80  :    80 :      0 :  00000000  :  Yes :    Ok : G-List module (copy)
ELG1 :      :     C   :    3F0002700 :    3F0002700 :  512  :   512 :      0 :  00000000  :  Yes :  Skip : Log module
EVLG :      :     C   :    3F0002900 :    3F0002900 :  512  :   260 :      0 :  00000000  :   No :       : Log module (event log)
PID1 :      :     D   :    3F0000602 :    3F0000602 :    2  :     2 :      0 :  00000000  :  Yes :    Ok : Module contains information from label on PCB
PID2 :      :     D   :    3F0100602 :    3F0100602 :    2  :     2 :      0 :  00000000  :  Yes :    Ok : Module contains information from label on PCB
PIDM :      :     D   :    3F00005FF :    3F00005FF :    3  :     3 :      0 :  00000000  :  Yes :    Ok : Module contains information from label on PCB
PDM1 :      :    Ad   :    3F0001400 :    3F0001400 : 1600  :  1600 :      0 :  00000000  :  Yes :    Ok : P-List module (PDM1 - reference to PSHT)
PDM2 :      :    Ad   :    3F0101400 :    3F0101400 : 1600  :  1600 :      0 :  00000000  :  Yes :    Ok : P-List module (copy)
HLR1 :      :     B   :    3F0001068 :    3F0001068 :    5  :     5 :      0 :  00000000  :  Yes : Error : Factory tests log module (HLRC)
HLR2 :      :     B   :    3F0101068 :    3F0101068 :    5  :     5 :      0 :  00000000  :  Yes : Error : Factory tests log module (HLRC, copy)
MFGP :      :    Dr   :    3F0003E00 :    3F0003E00 :    1  :     1 :      0 :  00000000  :  Yes : Error : Self Test parameters module
MFGT :      :         :    3F0016421 :    3F0016421 :    1  :     1 :      0 :  00000000  :  Yes : Error :
DMP1 :      :         :    3F0010700 :    3F0010700 : 4096  :  4096 :      0 :  00000000  :  Yes : Error :
SDM1 :      :         :    3F0011700 :    3F0011700 : 4096  :  4096 :      0 :  00000000  :  Yes : Error :
SVLG :      :         :    3F0012B00 :    3F0012B00 : 1024  :  1024 :      0 :  00000000  :  Yes :    Ok :
DDD0 :      :     B   :    3F0001000 :    3F0001000 :    2  :     2 :      0 :  00000000  :  Yes :  Skip : DDD utility log module
DIAG :      :     B   :    3F0001004 :    3F0001004 :  100  :   100 :      0 :  00000000  :  Yes :  Skip : Native diagnostic utilities log module
WRT0 :      :     B   :    3F0012700 :    3F0012700 :   15  :    15 :      0 :  00000000  :  Yes :  Skip : Marker at head 0
WRT1 :      :     B   :    3F0112700 :    3F0112700 :   15  :    15 :      0 :  00000000  :  Yes :  Skip : Marker at head 1

Modules checking completed


Information about copy 0
------------------------


Report on module USAG,  "Main module table"
ABA..................................... : 3F0000004
Length (sectors)........................ : 6
Loaded.................................. : Yes
Identified.............................. : Yes



Report on module FEAT
ABA..................................... : 3F0008B96
Length (sectors)........................ : 8
Loaded.................................. : Yes
Identified.............................. : Yes

Capacity................................ : 976773168
Maximal LBA............................. : 976773167
AutoReassign............................ : ON
G-List overflow flag.................... : OFF


Report on module IDNT,  "HDD ID data module"
ABA..................................... : 3F0000492
Length (sectors)........................ : 2
Loaded.................................. : Yes
Identified.............................. : Yes

FW Ver (part 1)......................... : GH2O
Model................................... : HGST HTS725050A7E630                   


Report on module WWNM
ABA..................................... : 3F00005E6
Length (sectors)........................ : 1
Loaded.................................. : Yes
Identified.............................. : Yes

Serial.................................. :       TF0501Y93AUXVR
WWN..................................... : 5000CCA76CEF3390


Information about copy 1
------------------------


Report on module USAG,  "Main module table"
ABA..................................... : 3F0000004
Length (sectors)........................ : 6
Loaded.................................. : Yes
Identified.............................. : Yes



Report on module FEAT
ABA..................................... : 3F0008B96
Length (sectors)........................ : 8
Loaded.................................. : Yes
Identified.............................. : Yes

Capacity................................ : 976773168
Maximal LBA............................. : 976773167
AutoReassign............................ : ON
G-List overflow flag.................... : OFF


Report on module IDNT,  "HDD ID data module"
ABA..................................... : 3F0000492
Length (sectors)........................ : 2
Loaded.................................. : Yes
Identified.............................. : Yes

FW Ver (part 1)......................... : GH2O
Model................................... : HGST HTS725050A7E630                   


Report on module WWNM
ABA..................................... : 3F00005E6
Length (sectors)........................ : 1
Loaded.................................. : Yes
Identified.............................. : Yes

Serial.................................. :       TF0501Y93AUXVR
WWN..................................... : 5000CCA76CEF3390


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 18th, 2017, 9:59 
Offline

Joined: March 19th, 2015, 15:01
Posts: 1261
Location: isreal
then use a LDR
http://blog.acelaboratory.com/hitachi-i ... -mb-2.html


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 18th, 2017, 13:06 
Offline

Joined: April 10th, 2007, 9:53
Posts: 315
I'll need to find another drive to generate a loader, since I don't want to risk moving these heads back to the donor, generating a loader, and then swapping them back again.

One thing I find odd is, when I have the PSHT and RDMT loaded from a file, refresh the ID and go to sector edit, I can navigate to any sector. I can also just keep hitting "next" and it will go through and read each sector I go to. I can navigate all the way to the final sector. I can see data written to the sectors. However, as soon as I go into Data Extractor, it errors out when trying to read the Drive ID and then I have to reset everything.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 19th, 2017, 10:26 
Offline

Joined: April 10th, 2007, 9:53
Posts: 315
Having a hard time finding another match for this. I still find it odd that when I have the PSHT and RDMT loaded from a file, refresh the ID and go to sector edit, I can navigate to any sector.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 23rd, 2017, 10:38 
Offline

Joined: April 10th, 2007, 9:53
Posts: 315
Just bumping this one last time to see if anyone else has seen an issue like this.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 23rd, 2017, 10:45 
Offline
User avatar

Joined: January 9th, 2007, 11:12
Posts: 289
Location: Romania
Hi

Try to enter DE task with another(no matter what model) Hitachi 500GB drive, don't do nothing and power off , replace with your drive and try to read sectors.

Rgds

_________________
www.datasave.ro


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 23rd, 2017, 11:07 
Offline

Joined: November 29th, 2006, 10:08
Posts: 6893
Location: UK
gtd4242 wrote:
I'll need to find another drive to generate a loader, since I don't want to risk moving these heads back to the donor, generating a loader, and then swapping them back again.

One thing I find odd is, when I have the PSHT and RDMT loaded from a file, refresh the ID and go to sector edit, I can navigate to any sector. I can also just keep hitting "next" and it will go through and read each sector I go to. I can navigate all the way to the final sector. I can see data written to the sectors. However, as soon as I go into Data Extractor, it errors out when trying to read the Drive ID and then I have to reset everything.


You are deselecting the "soft reset" option before progressing through into DE, right?

_________________
PC Image Data Recovery
www.pcimage.co.uk


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 23rd, 2017, 14:16 
Offline

Joined: April 10th, 2007, 9:53
Posts: 315
I may have found a work around on this. The first thing I do is go into the HDD Translator Initialization in the Hitachi utility and load the PSHT and RDMT from the backup I created of all the modules.

Once I do this, I can refresh the ID and the drive shows up properly.

I've found that the trick is, whenever it hits an error or tries to reset itself, you have to go in and reload the PSHT and RDMT files. After you've done it the first time, it's just a matter of going back into that and hitting "OK" again. Then refresh the ID again and it's all good.

When I created the task in DE, I unchecked everything except "Soft Reset" in drive initialization. I then manually input the number of sectors the drive contains. That got me into DE with an accessible drive.

When I tried to tree the directory so that I could scan the MFT's, it once again errored out and was inaccessible. Instead of shutting it down I navigated back over to the Hitachi utility and once again reloaded the PSHT and RDMT. That made the drive accessible again.

It's scanning now...slow...but scanning. About 2% into it, so I definitely don't think it was a head issue. Both heads seem to read equally well. I'm going to leave this running and see what we get.

Hopefully this info helps others in the future if they need it.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 23rd, 2017, 14:52 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 8118
Location: Portugal
gtd4242 wrote:
(...)
When I created the task in DE, I unchecked everything except "Soft Reset" in drive initialization. I then manually input the number of sectors the drive contains. That got me into DE with an accessible drive.


Next time try to uncheck "Soft Reset" as well....

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 24th, 2017, 10:54 
Offline

Joined: April 10th, 2007, 9:53
Posts: 315
Spildit wrote:

Next time try to uncheck "Soft Reset" as well....


I had already done that. Didn't make any difference at all.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 24th, 2017, 11:18 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 8118
Location: Portugal
gtd4242 wrote:
Spildit wrote:

Next time try to uncheck "Soft Reset" as well....


I had already done that. Didn't make any difference at all.


ok ...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 24th, 2017, 11:25 
Offline

Joined: April 10th, 2007, 9:53
Posts: 315
I found the best solution was just to disable all initialization actions, and ultimately forced the drive to use hardware read retries with no other error handling settings. It's the only way I was able to get the full partition detected and get any type of image created. It clicks every now and then and sounds ugly, but it's still moving along surprisingly enough. Any other settings and it hits a bad sector and just errors out.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 24th, 2017, 12:12 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 8118
Location: Portugal
gtd4242 wrote:
I found the best solution was just to disable all initialization actions, and ultimately forced the drive to use hardware read retries with no other error handling settings. It's the only way I was able to get the full partition detected and get any type of image created. It clicks every now and then and sounds ugly, but it's still moving along surprisingly enough. Any other settings and it hits a bad sector and just errors out.


Thanks for sharing !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: Hitachi HTS725050A7E630 Not Accessible
PostPosted: May 25th, 2017, 13:12 
Offline
User avatar

Joined: August 15th, 2006, 3:01
Posts: 2296
Location: CDRLabs @ Chandigarh [ India ]
Hello,
I would like to share my experience with this kinda scenario .According to my experience this is due to the fact that Plist or glist from copy 0 is not ok .Its good to view plist and glist from copy 0 and 1 and then try and use the copy you feel is ok .Sometimes you can try and reconstruct the list from both partially read copies in Winhex or try composite read mode of PC3K . Sometimes if Glist is totally %@$%#$%# up you can still recover using plist .I have done many drives using this technique

_________________
Regards
Amarbir S Dhillon
CDRLabs Data Recovery - [ Chandigarh ,India ]
My Data Recovery Experiments - > https://www.facebook.com/chandigarhdatarecovery


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

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Exabot [Bot], fess34, Yahoo [Bot] and 21 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