DispPatch abends at start

[HaraldE]

Morning,

I am trying DP for the first time, like the product but not the result ... yet

The disk with the problem is 320G. It is usually hosted in a laptop but right now it is an external USB drive, hooked to my desktop. The desktop is a rather old IBM ThinCenter with Pentium 4 CPU, 3.20 Ghz and 1 Gb of RAM. OS is XP with SP2

I used DP to create a floppy and booted from it. Start is fine and main meu arrivess ... then thie following happens:

> choose "Start DP"
> DP seems to start
> screen flickers and for about 2 secs I see a message starting:
"DP Has Encountered an unrecorable error ...
> This is all I have time to read ... before I am back at the main menu
> Tried it again with same result
> did some experiments ... wanted to see more of that error screen ... and got it
> Used "Quit" to get out to DOS
> Started DP manualy from a comand line saying "DP"
> Error screen appeared and read:
 + DP has encountered an unrecorable error ...
 + Adress: 78601
 + ErrorC: 11
 + Error Speciifics: Unforseen runtime error

When I looked at the floppy I found DFILES > DP.LOG
And it looks like the following
>>>>>>>>>>>>> LOG STARTS

.../000:03/LOG> ### LOG START ###
.../000:03/LOG> DISKPATCH 3.5.200
.../000:03/LOG> (C) 2000-2008 DIY DataRecovery
.../000:03/LOG> Contact info: http://HTTP://www.DIYDataRecovery.nl
.../000:03/LOG> MemFree: 72Kb
.../000:03/LOG> CommandLineParms:
.../000:03/LOG> LogDate: 06-04-2009
.../000:03/CFG> FilePath="1/.\DPFILES\"
.../000:03/CFG> LogFilename="DP.LOG"
.../000:03/CFG> ReadRetries="32"
.../000:03/CFG> WriteRetries="32"
.../000:03/CFG> MaxReadErrors="32"
.../000:03/CFG> MaxWriteErrors="1"
.../000:03/CFG> LogEachReadError="1"
.../000:03/CFG> ReadDelay="0"
.../000:03/CFG> VfyFixedBadSect="1"
.../000:03/CFG> CleanAfterDOD="1"
.../000:03/CFG> DiskReset="1"
.../000:03/CFG> SectorSkip="1024"
.../000:03/CFG> AutoSaveState="1"
.../000:03/CFG> DumpFoundSectors="0"
.../000:03/CFG> FixFats="1"
.../000:03/CFG> MaxFatScan="51200"
.../000:03/CFG> MaxDataColEntries="256"
.../000:03/CFG> IgnoreF8FF="0"
.../000:03/CFG> DownSizeExt="1"
.../000:03/CFG> ScanSignature="55AA"
.../000:03/CFG> Rebuild="00"
.../000:03/13H> Ext13H installed test requested
.../000:03/13H> Disk found at 128
.../000:03/13H> Ext13H version: EDD-3.0
.../000:03/13H> Ext13H Support: Extended disk access functions
.../000:03/13H> Ext13H Support: Enhanced disk drive functions
.../000:03/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:03/13H> Drive Interface Info:
.../000:03/13H> Disk 128 X13H data : 16383/16/63 307757197/512
.../000:03/13H> Disk found at 129
.../000:03/13H> Ext13H version: EDD-3.0
.../000:03/13H> Ext13H Support: Extended disk access functions
.../000:03/13H> Ext13H Support: Removable drive controller functions
.../000:03/13H> Ext13H Support: Enhanced disk drive functions
.../000:03/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:03/13H> Drive Interface Info:
.../000:03/13H> Disk 129 X13H data : 0/0/0 625142448/512
.../000:03/13H> Ext13H tested ok
.../000:03/FDL> DiskList requested
.../000:03/FDL> Disk found at 128
.../000:03/FDL> Disk found at 129

>>>>>>>>>>>>> LOG ENDS


Can you tell me what and where the issue is?
Is this a problem with my desktop or with DP?
Could you based on above suggest a way forward?

Regards,  Harald

[Joep]

Hello,

What is the original problem? So, why are you running DiskPatch in the first place?

Try hooking up the disk to the motherboard connecter directly, but I fear it may be a problem with the disk mis-reporting some geometry information: right now is reports zeros for cylinder/head/sector values and DiskPatch tries to do some math with zeros. This resulting in a devision by zero error.

[HaraldE]

Morning,

Daughter dropped her laptop to the floor and this made the disk not bootable. It has (I believe) 3 partions, roughly:
10 G hidden
90 G Windows + all her photos
200 G with a lot of data

I can get to the disk using Windows Explorer and have two drive letters, I assume for the 90 and 200 partitions. The 200 is ok and I can see the data. But the other (which I assume is the 90 Gb) can not be reached . I get a "Drive not formatted . Do you want to format it" message

I downloaded iRecover and had a go with it in test mode. It could read the 90 Gb part but it took many hours. Finally I saw the tree structure and it was filled with recovered directories. Almost all directories which Irecover had named ... just a few names I could recognise

I then successfully recover the one directory that is alowed in the test version ... just wanted to see if this worked. And it did. But to do all of these directories I felt would be very time consuming. And recovered images would then not be located in original directory

This is when I started to look at DiskPatch. I bought a copy and had a go on it, I know I should clone the disk but I just don't have a free disk of that size. I actually did clone it but to a smaller disk ... a 50 G ... wanted to see how it worked out. That cloned disk is still with me but I am not sure if it is of value. When I give it to DP (as an USB drive) it tells me I have overlapping partitions.

And now I started to be concerned that I couldn't get a log-file since I was starting DP from a CD. So the next obvious step was to create a bootable diskette. And so I did ... cretaed 2 actually. And both of them gives me same abend as was reported in the original report above.

So you could say my main issue now id that I can't start CP in a way to create a log file.

Sorry for the long and winding story ... now you have it all (almost) ... can you see a way out?

Regards,  Harald

[Tom]

DiskPatch does not successfully conclude it's startup because disk detection is funky, most likely a result of gravity.
It seems to me that, since the iRecover runs went okay, that's a good way to go: if the disk is not accessible in it's current state for DiskPatch, DiskPatch won't be able to do much. It should be said that accessing a disk through a USB enclosure is not the most reliable way to do this, but i guess you have your reasons for doing it that way. It would be best though to access the disk directly (connect it to a motherboard controller, or use it in it's original pc).

But to do all of these directories I felt would be very time consuming.

If you buy a license you can do all directories in one go.

And recovered images would then not be located in original directory

Seems a small price to pay for actually getting the pictures back.

So you could say my main issue now id that I can't start CP in a way to create a log file.

Well, i'd say your main issue is getting the pictures back. From your description i understand that the rest is okay, it's about that 90Gb volume and the pictures on it. I suppose we'd be happy to see a DiskPatch log file, but if iRecover can help you get the stuff back, why not go that way? If you still wish to post a log file for us to analyze you will need to connect the disk directly, to hopefully circumvent the disk detection problems.

If you're worried about getting yet another license, we can work out a deal if you wish to purchase an iRecover license.

[HaraldE]

Morning,

Thanks for a quick reply. Maybe I did't make my self clear. I can get DP to work if I boot from the CD but then I can't store the log file. So DP does see and can work on the disk. This I know for sure.

I have also had the disk inside a laptop and connected directly(not USB) and DP from CD could get to it. This is quicker than an USB connection but no difference regarding if and how I get to the disk. So this is not the issue. But my laptop do not have a floppy drive so I had to move over to the desktop

I can't believe it is the drive itself. If I boot DP from CD on desktop I can get to the drive but when I boot DP from floppy on same desktop DP abends. This abend could not be disk related (I think). Maybe it is the floppy or the floppy drive that is defect?

I see some alternatives:
1/ You advice me of a way to boot DP (floppy, USB stick, CD, ....) so I can create log-files
2/ I move over to iRecover and walk down that path
3/ I get a new 320 drive and clone and then use DP on clone for a repair ... with no log.file
4/ I take the risk and use DP directly on the damaged disk ... with no log-file

I have listed them above in the order I want to see them happen. Is there no way I can start DP from CD and store log-files on a floppy?

You say ... "If you still wish to post a log file for us to analyze you will need to connect the disk directly, to hopefully circumvent the disk detection problems." ... I very much want to post a log file but how shall I create one My old desktop is the only machine with a floppy and I can't get the disk inside. This is a new version of Catch-22 (;=))

And yes .. please send me an offer for the iRecover licens, that would be nice. I feel like walking down both the DP and the iR path ... would like both to work.

Thanks for help,   Harald

[Tom]

Okay, so you want to get DP going to work on the disk. I'll take that as the starting point then. Try this:

Use the HP USB key formatter to format a USB key with a FAT partition. Have that key connected when you start the DP boot CD, DP should see that it can't save to the cd and offer to save to the USB key. That should work.
Find the HP formatter here : http://www.diydatarecovery.nl/downloads/HPdrivekeyFormatter.exe

Post a log first, we'll see what the situation is and take it from there. Please also include a SMART log (check the DP manual for details).

[HaraldE]

Thanks Tom ... your help is appreciated

It may take some days to find the time ... so don't hold your breath ... but I will be back
I will also look around for a disk and maybe do a clone ... it would feel safer that way

Regards, Harald

[HaraldE]

Morning,

Bought a 400 Gb Western Digital external drive since I wanted to do a clone. Now I have both the bad 320 Gb and this new 400Gb attached using USB. When I start the laptop using Windows XP I can see both dives. They both gets drive letters and I can format the new drive.

DP starts ok but will only see the bad 320 drive (as well  as the internal hard disk).

Am I doing something wrong?
How do I make DP see the new drive?

> CHANGE:
> Downloaded the new DP version and the above issue is gone.
> Have also formatted a USB stick ... will now try to create a Support Log
> Looks like this will take many hours ...

Regards,  Harald

[HaraldE]

Yup ... Support Log created and shown below.

Erlier today I tried to clone the bad disk and this started ok. But after 30 minutes estimated remaining time was around 6000 minutes (many days). I decided to ESC out. This is my own machine and to be without it for many days would be a real problem ... not an impossibility but very inconvenient.

Instead I asked for a Suprt Log and got one ... shown below. in there you see the three partitions of the bad disk ...
128/000:22/VEC>  UNKNOWN (P)        WinRE        2048    18432000       (9 Gb)
128/000:22/VEC>     NTFS (P)       SYSTEM    18434048   204967936      (98 Gb)
128/000:22/VEC>     NTFS (P)         DATA   223401984   401738416     (192 Gb)

The only partition that I am interested in is the second one (SYSTEM of 98 Gb). The large partition (DATA of 192 Gb) is already available using standard Windows as a drive letter so this one we can skip. The first one I am not sure what it is and suspect it may be a hidden OS partition. So we skip this one as well.

My main questions right now are:
> How good / Bad is the SYSTEM partion ... can it be repaired?
> Is there a way to CLONE just the SYSTEM part and not the whole disk?
   My main interest is to get back JPG files from SYSTEM ..
> Should I skip DP and move over to iRecover? Which path do you recommend?

Regards,  Harald


.../000:07/LOG> ### LOG START ###
.../000:07/LOG> DISKPATCH 3.5.300
.../000:07/LOG> (C) 2000-2009 DIY DataRecovery
.../000:07/LOG> Contact info: http://HTTP://www.DIYDataRecovery.nl
.../000:07/LOG> MemFree: 70Kb
.../000:07/LOG> CommandLineParms:
.../000:07/LOG> LogDate: 06-07-2009
.../000:07/CFG> FilePath="C:DPFILES\"
.../000:07/CFG> ReadRetries="32"
.../000:07/CFG> WriteRetries="32"
.../000:07/CFG> MaxReadErrors="32"
.../000:07/CFG> MaxWriteErrors="1"
.../000:07/CFG> LogEachReadError="1"
.../000:07/CFG> ReadDelay="0"
.../000:07/CFG> VfyFixedBadSect="1"
.../000:07/CFG> CleanAfterDOD="1"
.../000:07/CFG> DiskReset="1"
.../000:07/CFG> SectorSkip="1024"
.../000:07/CFG> AutoSaveState="1"
.../000:07/CFG> DumpFoundSectors="0"
.../000:07/CFG> FixFats="1"
.../000:07/CFG> MaxFatScan="51200"
.../000:07/CFG> MaxDataColEntries="256"
.../000:07/CFG> IgnoreF8FF="0"
.../000:07/CFG> DownSizeExt="1"
.../000:07/CFG> ScanSignature="55AA"
.../000:07/CFG> Rebuild="00"
.../000:07/13H> Ext13H installed test requested
.../000:07/13H> Disk found at 128
.../000:07/13H> Ext13H version: EDD-3.0
.../000:07/13H> Ext13H Support: Extended disk access functions
.../000:07/13H> Ext13H Support: Enhanced disk drive functions
.../000:07/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:07/13H> Drive Interface Info:
.../000:07/13H> Disk 128 X13H data : 16383/16/63 625142448/512
.../000:07/13H> Disk found at 129
.../000:07/13H> Ext13H version: EDD-3.0
.../000:07/13H> Ext13H Support: Extended disk access functions
.../000:07/13H> Ext13H Support: Removable drive controller functions
.../000:07/13H> Ext13H Support: Enhanced disk drive functions
.../000:07/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:07/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:07/13H> Drive Interface Info:
.../000:07/13H> Disk 129 X13H data : 1024/4/32 7843839/512
.../000:07/13H> Disk found at 130
.../000:07/13H> Ext13H version: EDD-3.0
.../000:07/13H> Ext13H Support: Extended disk access functions
.../000:07/13H> Ext13H Support: Removable drive controller functions
.../000:07/13H> Ext13H Support: Enhanced disk drive functions
.../000:07/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:07/13H> Drive Interface Info:
.../000:07/13H> Disk 130 X13H data : 0/0/0 781422768/512
.../000:07/13H> Ext13H tested ok
.../000:07/FDL> DiskList requested
.../000:07/FDL> Disk found at 128
.../000:07/FDL> Disk found at 129
.../000:07/FDL> Disk found at 130
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB_|__GEO
128 | .625142448 | 240 | 63 | 298 | BIOS
129 | ...7843839 | .64 | 32 | ..3 | FIXD
130 | .781422768 | 255 | 63 | 372 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
.../000:07/IAS> AdmiSector found on disk 0 (128)
.../000:07/IAS> AdmiSector found on disk 1 (129)
.../000:07/IAS> AdmiSector found on disk 2 (130)
.../000:07/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:08/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:08/EXE> Read/Write pattern test for disk 2 (130) successful
.../000:08/WAS> AdmiSectors in use : 0+ 1+ 2+
.../000:08/KEY> 19O2O9O162/4
.../000:08/PFC> PQstuff signature not detected on disk 0 (128)
.../000:08/PFC> PQstuff signature not detected on disk 1 (129)
.../000:08/PFC> PQstuff signature not detected on disk 2 (130)
.../000:08/PFC> UDMA driver not loaded
.../000:09/PFC> Disk health 1-50
.../000:10/PFC> Partition State backup not found on disk 0 (128)
.../000:10/PFC> Partition State backup not found on disk 1 (129)
.../000:10/PFC> Partition State backup not found on disk 2 (130)
.../000:10/PFC> No Repair date found on disk 0 (128)
.../000:10/PFC> No Repair date found on disk 1 (129)
.../000:10/PFC> No Repair date found on disk 2 (130)
.../000:17/MNU> - Main, Select Disk
.../000:22/CSD> Start CheckDisk for disk 0 (128)
.../000:22/CSD> CheckDisk complete, ReadErrors 0
.../000:22/USD> Disk 0 (128) selected
.../000:22/GSC> No geo change detected for disk 0 (128)
.../000:22/WAS> AdmiSectors in use : 0+ 1+ 2+
128/000:22/USD> MBR for disk 0 (128)
128/000:22/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C 8E C0 8E D8 BE 00 7C BF 00  |  3???.|?.|?.
016   06 B9 00 02 FC F3 A4 50 68 1C 06 CB FB B9 04 00  |  .?..???Ph....
032   BD BE 07 80 7E 00 00 7C 0B 0F 85 10 01 83 C5 10  |  ??.?~..|..?..??.
048   E2 F1 CD 18 88 56 00 55 C6 46 11 05 C6 46 10 00  |  .?V.U?F..?F..
064   B4 41 BB AA 55 CD 13 5D 72 0F 81 FB 55 AA 75 09  |  ?A??U?.]r.??U?u.
080   F7 C1 01 00 74 03 FE 46 10 66 60 80 7E 10 00 74  |  ??..t.?F.f`?~..t
096   26 66 68 00 00 00 00 66 FF 76 08 68 00 00 68 00  |  &fh....f.v.h..h.
112   7C 68 01 00 68 10 00 B4 42 8A 56 00 8B F4 CD 13  |  |h..h..?B?V..
128   9F 83 C4 10 9E EB 14 B8 01 02 BB 00 7C 8A 56 00  |  .??.?..?.|?V.
144   8A 76 01 8A 4E 02 8A 6E 03 CD 13 66 61 73 1E FE  |  ?v.?N.?n.?.fas.?
160   4E 11 0F 85 0C 00 80 7E 00 80 0F 84 8A 00 B2 80  |  N..?..?~.?.??.??
176   EB 82 55 32 E4 8A 56 00 CD 13 5D EB 9C 81 3E FE  |  ??U2??V.?.]?>?
192   7D 55 AA 75 6E FF 76 00 E8 8A 00 0F 85 15 00 B0  |  }U?un.v.??..?..?
208   D1 E6 64 E8 7F 00 B0 DF E6 60 E8 78 00 B0 FF E6  |  ??d?.`?x.?.?
224   64 E8 71 00 B8 00 BB CD 1A 66 23 C0 75 3B 66 81  |  d?q.?.??.f#?u;f?
240   FB 54 43 50 41 75 32 81 F9 02 01 72 2C 66 68 07  |  ?TCPAu2??..r,fh.
256   BB 00 00 66 68 00 02 00 00 66 68 08 00 00 00 66  |  ?..fh....fh....f
272   53 66 53 66 55 66 68 00 00 00 00 66 68 00 7C 00  |  SfSfUfh....fh.|.
288   00 66 61 68 00 00 07 CD 1A 5A 32 F6 EA 00 7C 00  |  .fah...?.Z2??.|.
304   00 CD 18 A0 B7 07 EB 08 A0 B6 07 EB 03 A0 B5 07  |  .?. ?.?. ?.?. ?.
320   32 E4 05 00 07 8B F0 AC 3C 00 74 FC BB 07 00 B4  |  2?...<.t??..?
336   0E CD 10 EB F2 2B C9 E4 64 EB 00 24 02 E0 F8 24  |  .?.??+??d?.$.??$
352   02 C3 49 6E 76 61 6C 69 64 20 70 61 72 74 69 74  |  .?Invalid partit
368   69 6F 6E 20 74 61 62 6C 65 00 45 72 72 6F 72 20  |  ion table.Error
384   6C 6F 61 64 69 6E 67 20 6F 70 65 72 61 74 69 6E  |  loading operatin
400   67 20 73 79 73 74 65 6D 00 4D 69 73 73 69 6E 67  |  g system.Missing
416   20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74 65  |   operating syste
432   6D 00 00 00 00 62 7A 99 0A F0 0C 8C 00 00 00 20  |  m....bz?.?.?...
448   21 00 27 FE FF FF 00 08 00 00 00 40 19 01 80 FE  |  !.'?.......@..??
464   FF FF 07 FE FF FF 00 48 19 01 00 90 37 0C 00 00  |  ...?...H...?7...
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE  |  ...............?
496   FF FF 07 FE FF FF 00 D8 50 0D B0 0A F2 17 55 AA  |  ...?...?P.?.?.U?
###
128/000:22/VEC> Start Verify EPBR Chain for disk 0 (128)
128/000:22/VEC> Listing current partitions on disk:
128/000:22/VEC>  UNKNOWN (P)        WinRE        2048    18432000       (9 Gb)
128/000:22/VEC>     NTFS (P)       SYSTEM    18434048   204967936      (98 Gb)
128/000:22/VEC>     NTFS (P)         DATA   223401984   401738416     (192 Gb)
128/000:22/VEC> Partition Table info for sector 0 (0 0 1)
128/000:22/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..27 | ....0..32..33 | .1023.254..63 | ......2048 | ..18432000
..2 .128 | ..07 | .1023.254..63 | .1023.254..63 | ..18434048 | .204967936
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..07 | .1023.254..63 | .1023.254..63 | .223401984 | .401738416
128/000:22/VEC> 55AA sig Ok
128/000:22/LOG> Boot sector dump requested at 2048 (0 32 33)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 2048
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 18431999
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 1151999
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): D6348B9D348B7EED
........Volume Label (txt): WinRE
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/000:22/VEC> BS and BBS equal
128/000:22/LOG> Boot sector dump requested at 18434048 (1219 43 60)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 18434048
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 204967935
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 12554495
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 7E548E15548DD077
........Volume Label (txt): SYSTEM
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/000:22/VEC> BS and BBS equal
128/000:22/LOG> Boot sector dump requested at 223401984 (14775 63 16)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 223401984
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 401738415
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 2559999
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 5CA49111A490EF30
........Volume Label (txt): DATA
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/000:22/VEC> BS and BBS equal
128/000:22/VEC> Verify EPBR Chain completed
128/000:23/USD> Select disk completed
128/000:26/MNU> - Main, Disk Ops
128/000:28/MNU> - Disk Ops, Clone Disk
128/000:35/CLN> Source <= Target disk, Clone will fit
128/000:35/CLN> Previous clone setup: 128 -> 130
128/000:35/WAS> AdmiSectors in use : 0+ 1+ 2+
128/001:04/CLN> Start Clone Disk, from 0 (128) to 2 (130)
128/001:04/CLN> Clone range is 0 to 625142447
128/001:04/CLN> CloneType 1, SkipSize 1024
128/001:04/CLN> Read/Write Errors reset; Read/Write Errors until now : 0/0
128/001:04/CLN> MaxWriteErrors set to 1 for Cloning
128/003:24/CLN> Clone Disk (pass 1) aborted at sector 210944 (13 228 21)
128/003:48/CLN> Start Clone Disk, from 0 (128) to 2 (130)
128/003:48/CLN> Clone range is 0 to 625142447
128/003:48/CLN> CloneType 4, SkipSize 1024
128/003:48/VFC> Start Cloned Area Verify for disks 0 (128) & 2 (130)
128/003:48/VFC> Area to Verify is 0 - 625142447
128/003:48/VFC> ReadErrors reset; ReadErrors until now : 0
128/004:11/VFC> Verify Clone aborted at sector 62464 (4 31 32)
128/004:21/MNU> - Main, Select Disk
128/005:41/CSD> Start CheckDisk for disk 0 (128)
128/005:41/CSD> CheckDisk complete, ReadErrors 0
128/005:41/USD> Disk 0 (128) selected
128/005:41/GSC> No geo change detected for disk 0 (128)
128/005:41/WAS> AdmiSectors in use : 0+ 1+ 2+
128/005:41/USD> MBR for disk 0 (128)
128/005:41/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C 8E C0 8E D8 BE 00 7C BF 00  |  3???.|?.|?.
016   06 B9 00 02 FC F3 A4 50 68 1C 06 CB FB B9 04 00  |  .?..???Ph....
032   BD BE 07 80 7E 00 00 7C 0B 0F 85 10 01 83 C5 10  |  ??.?~..|..?..??.
048   E2 F1 CD 18 88 56 00 55 C6 46 11 05 C6 46 10 00  |  .?V.U?F..?F..
064   B4 41 BB AA 55 CD 13 5D 72 0F 81 FB 55 AA 75 09  |  ?A??U?.]r.??U?u.
080   F7 C1 01 00 74 03 FE 46 10 66 60 80 7E 10 00 74  |  ??..t.?F.f`?~..t
096   26 66 68 00 00 00 00 66 FF 76 08 68 00 00 68 00  |  &fh....f.v.h..h.
112   7C 68 01 00 68 10 00 B4 42 8A 56 00 8B F4 CD 13  |  |h..h..?B?V..
128   9F 83 C4 10 9E EB 14 B8 01 02 BB 00 7C 8A 56 00  |  .??.?..?.|?V.
144   8A 76 01 8A 4E 02 8A 6E 03 CD 13 66 61 73 1E FE  |  ?v.?N.?n.?.fas.?
160   4E 11 0F 85 0C 00 80 7E 00 80 0F 84 8A 00 B2 80  |  N..?..?~.?.??.??
176   EB 82 55 32 E4 8A 56 00 CD 13 5D EB 9C 81 3E FE  |  ??U2??V.?.]?>?
192   7D 55 AA 75 6E FF 76 00 E8 8A 00 0F 85 15 00 B0  |  }U?un.v.??..?..?
208   D1 E6 64 E8 7F 00 B0 DF E6 60 E8 78 00 B0 FF E6  |  ??d?.`?x.?.?
224   64 E8 71 00 B8 00 BB CD 1A 66 23 C0 75 3B 66 81  |  d?q.?.??.f#?u;f?
240   FB 54 43 50 41 75 32 81 F9 02 01 72 2C 66 68 07  |  ?TCPAu2??..r,fh.
256   BB 00 00 66 68 00 02 00 00 66 68 08 00 00 00 66  |  ?..fh....fh....f
272   53 66 53 66 55 66 68 00 00 00 00 66 68 00 7C 00  |  SfSfUfh....fh.|.
288   00 66 61 68 00 00 07 CD 1A 5A 32 F6 EA 00 7C 00  |  .fah...?.Z2??.|.
304   00 CD 18 A0 B7 07 EB 08 A0 B6 07 EB 03 A0 B5 07  |  .?. ?.?. ?.?. ?.
320   32 E4 05 00 07 8B F0 AC 3C 00 74 FC BB 07 00 B4  |  2?...<.t??..?
336   0E CD 10 EB F2 2B C9 E4 64 EB 00 24 02 E0 F8 24  |  .?.??+??d?.$.??$
352   02 C3 49 6E 76 61 6C 69 64 20 70 61 72 74 69 74  |  .?Invalid partit
368   69 6F 6E 20 74 61 62 6C 65 00 45 72 72 6F 72 20  |  ion table.Error
384   6C 6F 61 64 69 6E 67 20 6F 70 65 72 61 74 69 6E  |  loading operatin
400   67 20 73 79 73 74 65 6D 00 4D 69 73 73 69 6E 67  |  g system.Missing
416   20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74 65  |   operating syste
432   6D 00 00 00 00 62 7A 99 0A F0 0C 8C 00 00 00 20  |  m....bz?.?.?...
448   21 00 27 FE FF FF 00 08 00 00 00 40 19 01 80 FE  |  !.'?.......@..??
464   FF FF 07 FE FF FF 00 48 19 01 00 90 37 0C 00 00  |  ...?...H...?7...
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE  |  ...............?
496   FF FF 07 FE FF FF 00 D8 50 0D B0 0A F2 17 55 AA  |  ...?...?P.?.?.U?
###
128/005:41/VEC> Start Verify EPBR Chain for disk 0 (128)
128/005:41/VEC> Listing current partitions on disk:
128/005:41/VEC>  UNKNOWN (P)        WinRE        2048    18432000       (9 Gb)
128/005:41/VEC>     NTFS (P)       SYSTEM    18434048   204967936      (98 Gb)
128/005:41/VEC>     NTFS (P)         DATA   223401984   401738416     (192 Gb)
128/005:41/VEC> Partition Table info for sector 0 (0 0 1)
128/005:41/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..27 | ....0..32..33 | .1023.254..63 | ......2048 | ..18432000
..2 .128 | ..07 | .1023.254..63 | .1023.254..63 | ..18434048 | .204967936
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..07 | .1023.254..63 | .1023.254..63 | .223401984 | .401738416
128/005:41/VEC> 55AA sig Ok
128/005:41/LOG> Boot sector dump requested at 2048 (0 32 33)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 2048
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 18431999
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 1151999
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): D6348B9D348B7EED
........Volume Label (txt): WinRE
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/005:41/VEC> BS and BBS equal
128/005:41/LOG> Boot sector dump requested at 18434048 (1219 43 60)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 18434048
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 204967935
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 12554495
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 7E548E15548DD077
........Volume Label (txt): SYSTEM
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/005:41/VEC> BS and BBS equal
128/005:41/LOG> Boot sector dump requested at 223401984 (14775 63 16)
### BootSectorDump for BStype NTFS
...........Jump Code (hex): EB5290
............OEM Name (txt): NTFS
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 8
....Reserved Sectors (dec): 0
..............Unused (hex): 0000000000
....Media Descriptor (hex): F8
..............Unused (hex): 0000
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 223401984
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 401738415
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 2559999
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 5CA49111A490EF30
........Volume Label (txt): DATA
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/005:41/VEC> BS and BBS equal
128/005:41/VEC> Verify EPBR Chain completed
128/005:42/USD> Select disk completed
128/005:46/MNU> - Main, Disk Ops
128/005:52/MNU> - Main, Utilities
128/005:56/MNU> - Main, Options
128/006:00/MNU> - Support, Analyze Disk (no repair, create log)
128/006:04/SCN> DiskScan requested, ScanType is 3
128/006:04/SCN> from 0 (0 0 1) to 625142447 (41345 95 63), 625142448 sectors
128/006:04/SCN> Starting QuickScan (vista) at 2048 (0 32 33)
128/006:04/SCN> Next QuickScan location at 18434048 (1219 43 60)
128/006:05/SCN> Next QuickScan location at 223401984 (14775 63 16)
128/006:06/SCN> Next QuickScan location at 625140400 (41345 63 32)
128/006:06/RDS> Read past EOD intercept for disk 128 at 625142448 (41345 96 1)
128/006:06/SCN> Next QuickScan location at 0 (0 0 1)
128/006:07/SCN> QuickScan finished
128/006:07/SCN> Starting SmartScan (vista) at 0 (0 0 1)
128/006:07/RDS> Read past EOD intercept for disk 128 at 4294967295 (284058 164 4)
128/006:37/RDS> ReadError for disk 128 at 8527871 (564 3 3), C:1, T:10h
128/011:51/RDS> ReadError for disk 128 at 8642559 (571 143 31), C:2, T:02h
128/017:01/RDS> ReadError for disk 128 at 22145023 (1464 148 20), C:3, T:10h
128/019:46/RDS> ReadSector success (after error) at 22145023 (1464 148 20), tries 18
128/019:59/RDS> ReadError for disk 128 at 23799807 (1574 14 46), C:3, T:02h
128/025:27/RDS> ReadError for disk 128 at 44494854 (2942 187 34), C:4, T:10h
128/031:05/RDS> ReadError for disk 128 at 49997824 (3306 176 17), C:5, T:10h
128/036:25/RDS> ReadError for disk 128 at 50638848 (3349 31 16), C:6, T:10h
128/041:43/RDS> ReadError for disk 128 at 50708486 (3353 176 39), C:7, T:10h
128/047:42/RDS> ReadError for disk 128 at 60930054 (4029 183 46), C:8, T:10h
128/057:43/RDS> ReadError for disk 128 at 112791551 (7459 182 6), C:9, T:10h
128/057:46/RDS> ReadSector success (after error) at 112791551 (7459 182 6), tries 1
128/058:06/RDS> ReadError for disk 128 at 112793599 (7459 214 38), C:9, T:10h
128/058:09/RDS> ReadSector success (after error) at 112793599 (7459 214 38), tries 1
128/062:11/RDS> ReadError for disk 128 at 115130367 (7614 106 10), C:9, T:10h
128/062:12/RDS> ReadSector success (after error) at 115130367 (7614 106 10), tries 1
128/062:41/RDS> ReadError for disk 128 at 115142662 (7615 61 20), C:9, T:10h
128/062:44/RDS> ReadSector success (after error) at 115142662 (7615 61 20), tries 1
128/062:54/RDS> ReadError for disk 128 at 115144703 (7615 93 45), C:9, T:10h
128/062:58/RDS> ReadSector success (after error) at 115144703 (7615 93 45), tries 1
128/070:01/RDS> ReadError for disk 128 at 223283199 (14767 97 49), C:9, T:10h
128/070:06/RDS> ReadSector success (after error) at 223283199 (14767 97 49), tries 1
128/072:13/RDS> ReadError for disk 128 at 224714758 (14862 20 59), C:9, T:10h
128/072:42/RDS> ReadSector success (after error) at 224714758 (14862 20 59), tries 4
128/080:49/RDS> ReadError for disk 128 at 310923270 (20563 170 1), C:9, T:10h
128/080:53/RDS> ReadSector success (after error) at 310923270 (20563 170 1), tries 1
128/111:36/SCN> SmartScan finished
128/111:36/SCN> DiskScan completed
128/111:36/SCN> ReadErrors for disk 0 (128): 8
128/572:10/LOG> DataCollection items found: 14 / 5
### DATACOLLECTION.ARRAY, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 128 | ......2048 | ...NTFS | ..BS | ......2048 | ..18432000 | PRI | .
002 | 128 | ..18434047 | ...NTFS | .BBS | ......2048 | ..18432000 | PRI | .
003 | 128 | ..18434048 | ...NTFS | ..BS | ..18434048 | .204967936 | PRI | .
004 | 128 | .223401983 | ...NTFS | .BBS | ..18434048 | .204967936 | PRI | .
005 | 128 | .223401984 | ...NTFS | ..BS | .223401984 | .401738416 | PRI | .
006 | 128 | .625140399 | ...NTFS | .BBS | .223401984 | .401738416 | PRI | .
007 | 128 | .........0 | ...NTFS | PTE2 | ..18434048 | .204967936 | PRI | .
008 | 128 | .........0 | ...NTFS | PTE4 | .223401984 | .401738416 | PRI | .
009 | 128 | ......2048 | ...NTFS | ..BS | ......2048 | ..18432000 | PRI | I
010 | 128 | ..18434047 | ...NTFS | .BBS | ......2048 | ..18432000 | PRI | I
011 | 128 | ..18434048 | ...NTFS | ..BS | ..18434048 | .204967936 | PRI | I
012 | 128 | .219305983 | ...NTFS | .BBS | ..18434048 | .200871936 | PRI | .
013 | 128 | .223401983 | ...NTFS | .BBS | ..18434048 | .204967936 | PRI | I
014 | 128 | .223401984 | ...NTFS | ..BS | .223401984 | .401738416 | PRI | I
128/572:10/LOG> DataCollection items found: 14 / 5
### DATACOLLECTION.ARRAY, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 128 | ......2048 | ...NTFS | ..BS | ......2048 | ..18432000 | PRI
002 | 128 | ..18434047 | ...NTFS | .BBS | ......2048 | ..18432000 | PRI
003 | 128 | ..18434048 | ...NTFS | ..BS | ..18434048 | .204967936 | PRI
004 | 128 | .223401983 | ...NTFS | .BBS | ..18434048 | .204967936 | PRI
005 | 128 | .223401984 | ...NTFS | ..BS | .223401984 | .401738416 | PRI
006 | 128 | .625140399 | ...NTFS | .BBS | .223401984 | .401738416 | PRI
007 | 128 | .........0 | ...NTFS | PTE2 | ..18434048 | .204967936 | PRI
008 | 128 | .........0 | ...NTFS | PTE4 | .223401984 | .401738416 | PRI
012 | 128 | .219305983 | ...NTFS | .BBS | ..18434048 | .200871936 | PRI
128/572:10/LOG> PartList items created: 4
### PARTLIST.ARRAY ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ... | ..1 | ..2 | ..0 | ..1 | ..1 | ..1 | 2 | ..A
002 | ...NTFS | ..7 | ..3 | ..4 | ..0 | ..7 | ..7 | ..7 | 3 | ..A
003 | ...NTFS | ... | ... | .12 | ..0 | .12 | .12 | .12 | 1 | ..B
004 | ...NTFS | ..8 | ..5 | ..6 | ..0 | ..8 | ..8 | ..8 | 3 | ..A
### PARTLIST.ARRAY.INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | ......2048 | ..18432000 | ..18434047 | PRI | ..A | ..V
002 | ...NTFS | ..18434048 | .204967936 | .223401983 | PRI | ..A | ..V
003 | ...NTFS | ..18434048 | .200871936 | .219305983 | PRI | ..B | ..V
004 | ...NTFS | .223401984 | .401738416 | .625140399 | PRI | ..A | ..V
128/572:10/SST> SaveState requested for disk 0 (128)
128/572:10/WAS> AdmiSectors in use : 0+ 1+ 2+
128/572:11/SST> SaveState completed for disk 0 (128)
128/572:11/EXE> Analysis complete
128/572:29/MNU> - Main, Disk Ops
128/572:34/MNU> - Main, Utilities
128/572:52/MNU> - Main, Disk Ops
128/572:57/MNU> - Main, Utilities
128/573:02/MNU> - Main, Options
128/573:17/MNU> - Main, Quit
128/573:17/LOG> RunTime: 573:17
128/573:17/LOG> ### CLOSE LOG ###

[Tom]

> How good / Bad is the SYSTEM partion ... can it be repaired?

Don't know, really. The read errors are in that particular area, so something's wrong. But considering that the whole thing did the Newtonian dance i can't make any predictions about the state of that partition/disk. It's damaged, that's about it.

> Is there a way to CLONE just the SYSTEM part and not the whole disk?

Yes, just note the start and end area for that volume and enter the correct values for the clone operation. Just watch out: the clone wants to know where to start and where to stop, and the volume list lists the volumes with the start location and the length, so you'll have do some math. It's simpler then it sounds, just keep an eye out for what DP asks and give it the correct numbers.
Also, after a selective clone you'll have to run a "rebuild partition table" on the clone disk because the volume won't be visible in windows; the MBR will need to be fixed to show the lonely volume.

   My main interest is to get back JPG files from SYSTEM ..

I've said this before: you already succeeded with iRecover, right? Why all this then? Just because of the minor nuisance of lost filenames?

> Should I skip DP and move over to iRecover? Which path do you recommend?

I recommend the path that seems to work, and from your description the iRecover path worked. But it's up to you, really. Maybe the selective clone works out better, you'll just have to try.

Note: cloning disks through USB will be slow and might be unreliable. Direct connecting is better.

[HaraldE]

Helllo Tom,

I am actually very thankfull for both your products and the assist I get ...
but must admit I don't understand why you sometimes have a bit of a negative tone?

I've said this before: you already succeeded with iRecover, right? Why all this then? Just because of the minor nuisance of lost filenames?

All this is new to me ... I have just bought a new product called DiskPatch ... and I find it very interesting. As a new person in the game I may very well repeat myself ... say the wrong things ... but do believe me ... I am learning. And most of what I learn is from what you write. For example I just "learnt" how to make a "quote" inside a text.

Bottom line is that I very much appreciate your help and am pretty sure I will need more of it ... so keep the good advice comin! Tonight I will use your advice and try a limited clone.

Regards,  Harald

[Tom]

but must admit I don't understand why you sometimes have a bit of a negative tone?

Yes, i get that a lot in the real world, actually. I'm not though, i really want to know the answer to the question i asked, because it tells me something. And you still haven't answered me. Which is okay, really, but you have to understand: we have one mission, and that is to get you your data back. For that to work out well we need to know as much as possible, which is tricky enough with the internet inbetween us and the customer. So it may look like i get a little shortfused when people don't give me the answer i want after asking several times, but that's just my way of hopefully provoking an answer. Didn't work here though... :-)
Anyways, don't read the negative in it, think of it as my drive to get as much info as possible. And obviously, i'm happy to see we have a positive impact on your situation in general, with the learning and such. After all, we do have a reputation to uphold.

[HaraldE]

Morning Tom,

All ok ... understand and you may be right about answering question ... so here we go:

Why all this then?

All is about getting data back. But there is also a bit of a learning in this since I have never had a disk crash before. So I read document+forums a lot about this topic.

Just because of the minor nuisance of lost filenames?

If DP can give me back the disk structure with names of files and folders then that would be a major bonus. So in a way ... yes.

if iRecover can help you get the stuff back, why not go that way?

One reason is that I have a license for DP so it makes sense to start here. But I now have feeling I am down the wrong path. See more later on

What is the original problem?

Daughter has a laptop and dropped it on to the floor. Since then it won't start and the C drive can not be reached using Windows. The extra D drive is accessible though.

So, why are you running DiskPatch in the first place?

It isn't really the "first" place. DP is third tool try. And I try DP after seen some positive remarks. In general the product is doing well but I am starting to feel it is not the best for my situation.

If I missed any of your questions ... try again.

Now that was history now over to present. I started a CLONE yesterday and had to use USB. I am aware it is slower but I just don't have a machine where I can add the two drives on the inside. I can get one in but not two. A question ... if I would restart the clone and put one of the two disks inside ... which should be inside and which USB? Do you think this could improve the situation significantly?

The cloning is limited to the C drive and when I started DP it said it would take around two day. This is a very long time ... maybe not for the cloning itself but for me to be without my main machine. I decided to give it a try. Now after one  night and around 10 hours I am a bit disappointed. The status tells me DP has cloned from 18xxxxxx to 21xxxxxx and it is aiming for 204xxxxxx. And estimated remaining time is another 38920 minutes (many weeks). I believe it is standing still ... no values are changing.

So I am about to ESC out of this cloning if you don't have a different opinion. And if I do, I will either move over to iRecover or start looking for something else. I am not unsatisfied with DP as a product but I am not satisfied with the end result. So if I had a choice I would like to try iRecover full version. Can you somehow grant me such a license as a replacement for the one I bought for DP?

Regards,  Harald

[Tom]

Allright, understood.

When cloning it is always best to connect directly. If that isn't possible, at least connect the problem disk directly: the target disk is supposed to be a good disk so connecting that one through USB should be okay. Understand that reading a bad disk through USB is simply not the best way, the IDE/SCSI or whatever direct interface you have is usually better equipped to handle weird situations. Plus there's a potential problem with recognizing a disk's geometry when accessing a USB connected disk from DOS (as DP is doing).

From what you've told me cloning doesn't sound as if it is working out for you. That may very well be because of USB, but actually it doesn't matter that much. You can try what i suggested above (connect the problem disk directly and try again), that should work better, but you will have to be prepared to let it take a long time (it's not unusual for these things to take quite a while).

I understand that you bought DP first and want that to do the trick for you, but if you look at what's going on now you might (as i do) start wondering about whether this is the right course to take. Normally it would be; we always say "bad disk? clone first". But if that doesn't work out and other recovery options worked out better, than you have to start thinking about switching tools. Now here's what i would do:
use iRecover to get the files back (worked before, you lose filenames but have the files). Once you have them, continue working on the clone scenario. In that case, if the cloning doesn't go well, you will at least have the files. I know that this means that you would need to buy both programs, but in cloning situations that is usually the case: clone the disk and then use iRecover to retrieve as much as possible from the cloned disk (sometimes a cloned disk is normally accessible and you won't need iRecover, but that would be luck. it's happened though).

My suggestion: buy an iRecover license and get to work on those files. When you've finished the whole thing (iRecover and/or cloning), request a refund for the tool that didn't help you. Or, if you wish, i can offer you an iRecover license for a nice discount (say 45%) but that would mean the refund won't be possible anymore.

Obviously i'm not forcing you here, it's just a suggestion. If you wish you can try a new clone and see if that works out: if so, you won't need to spend any extra money. But there's no guarantee that you won't still need iRecover to get the files from the clone: if important areas on the source disk didn't copy over to the clone because of read errors, normal access to the disk may still not be possible.
Also, remember what i said about the selective clone. It's a good idea, but you'll have to run a Partition Table repair on the cloned disk afterwards.

Don't hesitate to ask any further questions.

[HaraldE]

Tom,

You comments are valid, positive and good. This is what I will do:

> I will stop current cloning
> Plug bad disk inside laptop and try a clone again and let it run for some hours
    (mainly to see what increase in speed I get)
> If that again shows up as "many days" then DP is not best for my situation
> If so I will buy iRecover and have a go with it ... (I think it took less than 2 days to read the disk last try)
> Recover all files I can find and then ask for a refund of DP

Do you have any suggested changes to this plan?
Will second clone start from the beginning or can I benefit from the clone work that has been done till now?
Also ... do you have any fix to my very original issue when DP abends at start? This only happens on my old desktop

Regards,  Harald