Welcome, Guest. Please login or register.
Did you miss your activation email?
June 20, 2019, 07:33:10 AM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  DP log analysis
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: DP log analysis  (Read 4261 times)
CodyM
member

Posts: 1


« on: October 13, 2013, 05:08:34 AM »

I'm trying to recover some data on a former external hard drive. The hard drive is a seagate expansion (3td) drive I bought around 15 months ago. About 12 months ago, it stopped working, seeming to have trouble keeping sufficient power. This appears to have been triggered by it being unplugged from the usb port, and when I plugged it back in (possibly to a different port?) it began acting up. I stored it for most of the last year, but decided to try and recover the files. When I plugged it in (still as an external drive), it had power just fine but windows said it needed to be formatted before it can be used (Actual line was "you need to format drive I: before it can be used" or very similar to that). Naturally being skeptical, I checked disk management and thought it wasn't showing up (it didn't show in the top half, but I now believe it probably was in the bottom half if I had scrolled that section down). In any case, I did some research and discovered that the enclosure of these drives often causes problems, so I removed the external enclosure and connected it to my computer like a regular HDD. Same error message, but when I checked disk management I noticed it in the bottom half of the screen. In disk management it says "Disk 0, Basic, 2794.52GB, Online". To the right of that, there are three boxes, one with a blue header and two with black headers. The blue header box says  "349.31 GB RAW , Healthy (Primary Partition)". The two black boxes say "1698.69 GB, unallocated" and "746.52 GB, unallocated." I recall there being approximately 1.3-1.6TB of data on the drive. If relevant, I am running windows 7 x64 (I believe it is home premium), intel chipset. I ran the diskpatch trial analysis and this is the dump. Thanks in advance.


.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 4.0.200
.../000:01/LOG> (C) 2000-2013 DIY DataRecovery
.../000:01/LOG> Contact info: www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 58Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 10-12-2013
.../000:01/CFG> FilePath="C:DPFILES\"
.../000:01/CFG> ReadRetries="32"
.../000:01/CFG> WriteRetries="32"
.../000:01/CFG> MaxReadErrors="32"
.../000:01/CFG> MaxWriteErrors="1"
.../000:01/CFG> ReadDelay="0"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> WriteAfterReadError="1"
.../000:01/CFG> VfyFixedBadSect="1"
.../000:01/CFG> CleanAfterDOD="1"
.../000:01/CFG> DiskReset="1"
.../000:01/CFG> SectorSkip="1024"
.../000:01/CFG> AutoSaveState="1"
.../000:01/CFG> DumpFoundSectors="0"
.../000:01/CFG> FixFats="1"
.../000:01/CFG> MaxFatScan="51200"
.../000:01/CFG> MaxDataColEntries="256"
.../000:01/CFG> IgnoreF8FF="0"
.../000:01/CFG> DownSizeExt="1"
.../000:01/CFG> ScanSignature="55AA"
.../000:01/CFG> Rebuild="00"
.../000:01/13H> Ext13H installed test requested
.../000:01/13H> Disk found at 128
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 128 X13H data : 15313/16/63 15435776/512
.../000:01/13H> Disk found at 129
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 129 X13H data : 16383/16/63 234441648/512
.../000:01/13H> Disk found at 130
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 130 X13H data : 16383/16/63 1565565872/512
.../000:01/13H> Ext13H tested ok
.../000:01/FDL> DiskList requested
.../000:01/FDL> Disk found at 128
.../000:01/FDL> Disk found at 129
.../000:01/FDL> Disk found at 130
### DISKLIST ###
__D_|________LBA_|___H_|__S_|___GB_|__GEO_|___SS_
128 | ..15435776 | .16 | 63 | ...7 | BIOS | .512
129 | .234441648 | 255 | 63 | .111 | BIOS | .512
130 | 1565565872 | 255 | 63 | 2794 | BIOS | .512
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
.../000:01/IAS> AdmiSector found on disk 0 (128)
.../000:01/IAS> AdmiSector found on disk 1 (129)
.../000:01/IAS> AdmiSector found on disk 2 (130)
.../000:01/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:02/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:02/EXE> Read/Write pattern test for disk 2 (130) successful
.../000:02/WAS> AdmiSectors in use : 0+ 1+ 2+
.../000:02/KEY> DEMO/1
.../000:02/PFC> PQstuff signature not detected on disk 0 (128)
.../000:02/PFC> PQstuff signature not detected on disk 1 (129)
.../000:02/PFC> PQstuff signature not detected on disk 2 (130)
.../000:02/PFC> Disk health not checked
.../000:03/PFC> Partition State backup not found on disk 0 (128)
.../000:03/PFC> Partition State backup not found on disk 1 (129)
.../000:03/PFC> Partition State backup not found on disk 2 (130)
.../000:03/PFC> No Repair date found on disk 0 (128)
.../000:03/PFC> No Repair date found on disk 1 (129)
.../000:03/PFC> No Repair date found on disk 2 (130)
.../000:29/VEC> Start Verify EPBR Chain for disk 2 (130)
.../000:29/VEC> Listing current partitions on disk:
.../000:29/VEC>     NTFS (P)        (Err)          63   732564000     (349 Gb)
.../000:29/VEC> Partition Table info for sector 0 (0 0 1)
.../000:29/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | ....0...1...1 | .1023.254..63 | ........63 | .732564000
..2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
.../000:29/VEC> 55AA sig Ok
.../000:29/LOG> Boot sector dump requested at 63 (0 1 1)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): 000000
............OEM Name (txt): ........
....Bytes per Sector (dec): 0
.Sectors per Cluster (dec): 0
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): 00
..............Unused (hex): 0000
...Sectors per Track (dec): 0
.....Heads per Track (dec): 0
......Hidden Sectors (dec): 0
..............Unused (hex): 00000000
.............Unknown (hex): 00000000
.......Total Sectors (dec): 0
........MFT Location (dec): 0
.MFT Mirror Location (dec): 0
....Clusters per FRS (dec): 0
.Clusters/Indx Block (dec): 0
...........Volume ID (hex): 0000000000000000
........Volume Label (txt): (Err)
............Checksum (hex): 00000000
....Sector Signature (hex): 0000
.../000:29/VEC> BS and BBS not equal, dump follows;
.../000:29/LOG> Boot sector dump requested at 732564062 (45600 0 63)
### BootSectorDump for BStype NTFS (B)
...........Jump Code (hex): 82B7B3
............OEM Name (txt): ^޴ئ.
....Bytes per Sector (dec): 13807
.Sectors per Cluster (dec): 98
....Reserved Sectors (dec): 8768
..............Unused (hex): 539803423B
....Media Descriptor (hex): A8
..............Unused (hex): BFF6
...Sectors per Track (dec): 4294934920
.....Heads per Track (dec): 4294937067
......Hidden Sectors (dec): 2299447196
..............Unused (hex): 8E7ACD21
.............Unknown (hex): 6661BFD1
.......Total Sectors (dec): 2748731287
........MFT Location (dec): 1646407658
.MFT Mirror Location (dec): 589209385
....Clusters per FRS (dec): 1959347464
.Clusters/Indx Block (dec): 1940084057
...........Volume ID (hex): F77F986D4D4B9D55
........Volume Label (txt): (Err)
............Checksum (hex): EDF53F5B
....Sector Signature (hex): C9AB
.../000:37/VEC> Verify EPBR Chain completed
.../000:41/USD> No source / disk selected
.../000:42/USD> Select disk completed
.../000:42/LOG> RunTime: 000:42
.../000:42/LOG> ### CLOSE LOG ###

Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #1 on: October 14, 2013, 08:35:01 AM »

Hello,

There is one *basic* NTFS partition which can't be right. If you used the full 3TB (one volume of 3 TB) before then the disk had to be *dynamic* because with basic partitions you can only have volumes up to 2 TB.

DiskPatch can not recreate dynamic volumes at this point as it only works with standard a MBR (up to 2 TB volumes). To recover the data you'd need iRecover.

A hint when using iRecover, right click in the device/volume selection window > define volumes manually and then opt for 'there was only one volume' to scan the entire disk (assuming you had one volume on the disk).
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
Pages: [1] Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!