Welcome, Guest. Please login or register.
Did you miss your activation email?
September 24, 2017, 09:44:40 AM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  clone takes 6 days?
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] 2 Go Down Print
Author Topic: clone takes 6 days?  (Read 7523 times)
mrbb
member

Posts: 9


« on: June 08, 2016, 08:52:08 AM »

Hello,

I have a 930 gb disk over USB and it takes more than six days to clone it.
I m afraid to damage the processor or something else to let it run wihout pause so long

Can I abort and restart at the same point or is any other way to clone it faster?

thanks for answer and help

regards   Rainer
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #1 on: June 08, 2016, 10:11:27 AM »

The best way to clone is to have all disks involved connected directly: no USB at all. USB in real mode is very very very slow and very very very unreliable.
You can abort the clone, make sure to remember where the clone stopped (the LBA address, as displayed on the status screen). Then simply re-start the clone from that location. You should also ask yourself why it takes so long: what's the status of the source disk? If that disk is in a bad state the clone could take very long, and the use of a direct connection would be even more important.
Logged

mrbb
member

Posts: 9


« Reply #2 on: June 08, 2016, 10:23:53 AM »

Thanks for answer Tom,

I tried to connect the Disk via sate but get the message invalid disk and restart strg+ alt+ del
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1457


WWW
« Reply #3 on: June 08, 2016, 11:03:24 AM »

Sounds as if the computer is trying to boot from it then? If the disk is attached to SATA and DiskPatch is on a USB key, make sure the boot order is set to try booting from USB first.
Logged

--
Kind regards,
Joep
mrbb
member

Posts: 9


« Reply #4 on: June 09, 2016, 10:50:17 AM »

Thanks for help, it was wrong boot device in bios

so now I connected the disks via sata and time remaining says 56 houres  = 2,3 days  for 930 GB.

Is that normal or is any other problem with the disk?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #5 on: June 09, 2016, 11:39:57 AM »

Depending on the state of the disk this isn't entirely abnormal, we've seen this before.
Quote
Is that normal or is any other problem with the disk?
That seems likely. You haven't said why you want to clone or what the disk's situation is so we can't say much more for now.
Logged

mrbb
member

Posts: 9


« Reply #6 on: June 09, 2016, 01:13:59 PM »

the state of the disk is, that wondows can not access and want to format the disk and diskdrill shows two patitions a 930 gb and two more with ca 300 MB
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1457


WWW
« Reply #7 on: June 09, 2016, 09:35:04 PM »

what does windows say when you try to access it? what are the actual symptoms?
Logged

--
Kind regards,
Joep
mrbb
member

Posts: 9


« Reply #8 on: June 10, 2016, 12:46:35 PM »

the cloning is running one more day, then I will write the exactly error from windows
I remember error in the data structure and can not red
Logged
mrbb
member

Posts: 9


« Reply #9 on: June 12, 2016, 10:26:16 AM »

now the clone is done and windows says :
E:\ is not accessible
The disk structure is corupted and unreadable

I m doing analysis log and post it here?
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #10 on: June 12, 2016, 02:57:37 PM »

Could you do this for the original disk:
http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm

Yes, you could run an analysis and post the result.

Normally when a disk is in trouble and you have to clone it, it's sort of expected that the clone isn't going to be normally accessible. After all, something's wrong with the original disk. So in most cases people clone a disk to make sure they salvage what they can and THEN start to work on the clone with iRecover, to recover as much data as possible.
Logged

mrbb
member

Posts: 9


« Reply #11 on: June 12, 2016, 08:42:15 PM »

This is the SMART Report:


Detected Controllers

  Disk Controller 1
    Device Vendor . . . . . . . . . . . . . : 8086
    Device ID . . . . . . . . . . . . . . . : 1E03
    Device  . . . . . . . . . . . . . . . . : Intel
    Device Location . . . . . . . . . . . . : Bus 0, Device 31, Function 2
    Device Ports  . . . . . . . . . . . . . : 5088-508F, 5094-5097, 5080-5087, 5090-5093, 5060-507F

(incomplete)

This is the analyse:

.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 4.0.300
.../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: 06-12-2016
.../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: 2.1 / EDD-1.1
.../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 : 1024/16/63 15974400/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> 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 129 X13H data : 16383/16/63 488397168/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> 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 130 X13H data : 16383/16/63 3907029168/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 | ..15974400 | .16 | 63 | ...7 | BIOS | .512
129 | .488397168 | 255 | 63 | .232 | BIOS | .512
130 | 3907029168 | 255 | 63 | 1863 | BIOS | .512
..0 | .........0 | ..0 | .0 | ...0 | BIOS | ...0
.../000:01/EXE> !- EFI BIOS / GUID partition type found on disk 1 (129)
.../000:01/EXE> !- EFI BIOS / GUID partition type found on disk 2 (130)
.../000:03/IAS> AdmiSector found on disk 0 (128)
.../000:03/IAS> AdmiSector on disk 1 (129) not free for DP use, dump follows;
.../000:03/LOG> SectorDump requested at 34 (0 0 35)
###
000   FA 47 C7 FF E4 73 96 63 33 BC 92 E8 EC FC EB F0  |  G.sc3
016   2F 2C 4F 93 65 CE 6F 01 CD 27 52 89 40 9B 29 D0  |  /,Oeo.'R@)
032   57 CD 60 95 A1 2C 02 D3 18 7D 0D 6B DE 53 47 92  |  W`,..}.kSG
048   C3 2B AC AB BB C9 7C 4F 56 77 BC B9 EF 73 1C E9  |  +|OVws.
064   4A A2 35 F2 01 67 19 D9 AC D6 FF 08 FF C7 22 76  |  J5.g.٬..."v
080   BE 3C 70 DC 9F 12 3E 17 74 E5 45 E0 16 88 A0 46  |  <pܟ.>.tE. F
096   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
112   66 AB 25 7B 62 64 A1 55 0E B3 D8 30 A0 34 CB B7  |  f%{bdU.0 4˷
128   CD 73 DC 74 AF 50 E7 09 15 D1 FD 17 9E C4 BA 61  |  stP...ĺa
144   29 4C 5F A7 B0 DC 79 82 D9 1B D7 8C 07 95 75 FC  |  )L_y.׌.u
160   5F C6 3B E6 3A BE 31 3E BA 72 03 C9 03 13 95 D8  |  _;:1>r...
176   D2 C8 89 FC 82 3E 7C C0 90 82 1B 28 1F 76 EC 77  |  ȉ>|.(.vw
192   E0 A7 ED 09 F2 6F D5 D1 53 75 D3 6B D9 B8 E1 4B  |  .oSukٸK
208   DF BB 2F B0 7B 9F 1F 02 2E 62 BD 22 D4 C2 EF 3C  |  ߻/{...b"<
224   B8 80 DB 65 DD DE 51 F2 58 86 74 52 0E 7F 19 5F  |  eQXtR.._
240   71 DE 4B 9A 16 94 53 39 96 FE FF E6 90 A7 70 F5  |  qK.S9.搧p
256   39 CE 19 45 02 3D 26 2F BD C0 E0 AE 89 93 17 FE  |  9.E.=&/உ.
272   10 E0 DE 7C A2 E4 FA D0 C3 F2 3E AB 7A 8D 99 23  |  .|>z#
288   FA DF 3F 94 55 BA 1F E4 C4 1A 7B EE B0 E4 10 44  |  ?U..{.D
304   CD 75 F0 64 BF 25 78 52 3C 46 41 89 DF E9 C9 26  |  ud%xR<FA&
320   0E 96 74 A0 BB 65 D1 2A 42 A9 FA C0 3F 97 CD CE  |  .t e*B?
336   86 8F 45 E9 D8 C4 B7 EB 02 03 67 2C 3D 2A 26 21  |  Eķ..g,=*&!
352   9C 9D DD 45 17 31 AE 03 0E 58 50 22 C5 BA 6D A8  |  E.1..XP"źm
368   C8 4C C5 E7 41 D4 58 79 FD EF F5 33 7B CF 1D 52  |  LAXy3{.R
384   26 36 36 53 07 70 AF AB 93 AD 1C 53 F1 D5 BB AB  |  &66S.p.Sջ
400   2E 72 8C 70 41 40 F3 D9 FE F1 57 E0 05 72 14 16  |  .rpA@W.r..
416   44 11 2E EB 92 1F 7B 16 78 BF 6A B0 DC 09 2E A4  |  D...{.xj..
432   F1 55 9F 94 F9 A2 CC 9A CE A1 55 4C 94 4C 39 EE  |  U̚ΡULL9
448   33 FA E1 B8 AF 5E E7 E2 9C E3 42 1B 40 7E 4B 7F  |  3ḯ^B.@~K
464   6E 65 57 57 1B F5 CB AC 17 F9 4A B1 42 E6 CC EF  |  neWW.ˬ.JB
480   A2 68 14 DD D9 42 AE FF AD 58 34 CC 3D 76 FE BD  |  h.B.X4=v
496   2F 08 18 CE 54 A5 E8 13 AF 78 0F 9C E6 C4 A7 D7  |  /..T.x.ħ
###
.../000:03/IAS> AdmiSector found on disk 2 (130)
.../000:03/KEY> DEMO/1
.../000:03/PFC> PQstuff signature not detected on disk 0 (128)
.../000:03/PFC> PQstuff signature not detected on disk 1 (129)
.../000:03/PFC> PQstuff signature not detected on disk 2 (130)
.../000:03/PFC> Disk health not checked
.../000:04/PFC> Partition State backup not found on disk 0 (128)
.../000:04/PFC> Partition State backup not found on disk 1 (129)
.../000:04/PFC> Partition State backup not found on disk 2 (130)
.../000:04/PFC> No Repair date found on disk 0 (128)
.../000:04/PFC> No Repair date found on disk 1 (129)
.../000:04/PFC> Last Repair (U) for disk 2 (130) performed on 06082016/121027
.../000:36/CSD> Start CheckDisk for disk 2 (130)
.../000:36/CSD> 0 (0 0 1)
.../000:36/CSD> 16064 (0 254 63)
.../000:36/CSD> 3907024065 (243201 0 1)
.../000:36/CSD> 3907029167 (243201 80 63)
.../000:36/CSD> CheckDisk complete, ReadErrors 0
.../000:36/USD> Disk 2 (130) selected
.../000:36/GSC> Geo for disk 2 (130) changed since last DP run
.../000:36/GSC> Geo info on disk 2 (130) (old)   : 1953525168255063
.../000:36/GSC> Current geo info for disk 2 (130): 3907029168255063
.../001:16/GSC> Selected geo for disk 2 (130) is 255/63
.../001:16/WAS> AdmiSectors in use : 0+ 1- 2+
130/001:16/USD> MBR for disk 2 (130)
130/001:16/LOG> SectorDump requested at 0 (0 0 1)
###
000   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
016   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
032   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
048   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
064   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
080   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
096   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
112   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
128   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
144   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
160   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
176   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
192   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
208   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
224   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
240   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
256   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
272   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
288   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
304   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
320   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
336   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
352   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
368   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
384   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
400   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
416   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
432   00 00 00 00 00 00 00 00 23 35 AF F9 BF FA 00 00  |  ........#5..
448   02 00 EE FF FF FF 01 00 00 00 FF FF FF FF 00 00  |  ...............
464   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
480   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
496   00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA  |  ..............U
###
130/001:16/VEC> Start Verify EPBR Chain for disk 2 (130)
130/001:16/VEC> Listing current partitions on disk:
130/001:16/VEC>  UNKNOWN (P)        (Err)           1  4294967295    (2048 Gb)
130/001:16/VEC> Partition Table info for sector 0 (0 0 1)
130/001:16/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..EE | ....0...0...2 | .1023.255..63 | .........1 | 4294967295
..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
130/001:16/VEC> 55AA sig Ok
130/001:16/LOG> Boot sector dump requested at 1 (0 0 2)
### BootSectorDump for BStype FAT16
...........Jump Code (hex): 454649
............OEM Name (txt): PART...
....Bytes per Sector (dec): 23552
.Sectors per Cluster (dec): 0
....Reserved Sectors (dec): 0
...........FAT count (dec): 196
....Root Entry Count (dec): 3635
..Total Sectors (16) (dec): 237
....Media Descriptor (hex): 00
.......FAT Size (16) (dec): 0
...Sectors per Track (dec): 1
.....Heads per Track (dec): 0
......Hidden Sectors (dec): 0
..Total Sectors (32) (dec): 3907029167
........Drive Number (hex): 00
............Reserved (hex): 00
......Boot Signature (hex): 00
...........Volume ID (hex): 00002200
........Volume Label (txt):
..Filesystem Type ID (txt):   
N)
....Sector Signature (hex): 0000
1st FAT not found at      : 1 (0 0 2)
2nd FAT not found at      : 1 (0 0 2)
130/001:16/CF8> FAT sectors are equal
130/001:16/LOG> SectorDump requested at 1 (0 0 2)
###
     EFI PART... ....".. nC... ...........
     ........... ........... ........... ...........
     ........... ........... ........... ...........
     ........... ........... ........... ...........
###
130/001:16/VEC> Verify EPBR Chain completed
130/001:16/USD> Select disk completed
130/001:22/SCN> DiskScan requested, ScanType is 3
130/001:22/SCN> from 0 (0 0 1) to 3907029167 (243201 80 63), 3907029168 sectors
130/001:22/SCN> Starting QuickScan (vista) at 2048 (0 32 33)
130/001:22/SCN> Next QuickScan location at 821248 (51 30 44)
130/001:23/SCN> Next QuickScan location at 1435648 (89 93 5)
130/001:23/SCN> Next QuickScan location at 0 (0 0 1)
130/001:24/SCN> QuickScan finished
130/001:24/SCN> Starting SmartScan (vista) at 0 (0 0 1)
130/001:24/RDS> Read past EOD intercept for disk 130 at 4294967295 (267349 89 4)
130/276:03/SCN> SmartScan finished
130/276:03/SCN> DiskScan completed
130/276:03/SCN> ReadErrors for disk 2 (130): 0
130/278:47/LOG> DataCollection items found: 11 / 4
### DATACOLLECTION, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 130 | ......2048 | ...NTFS | ..BS | ......2048 | ....819200 | PRI | .
002 | 130 | ....821247 | ...NTFS | .BBS | ......2048 | ....819200 | PRI | .
003 | 130 | ....821254 | ..FAT32 | .BBS | ....821248 | ....614400 | PRI | .
004 | 130 | ....821248 | ..FAT32 | ..BS | ....821248 | ....614400 | PRI | .
005 | 130 | ......2048 | ...NTFS | ..BS | ......2048 | ....819200 | PRI | I
006 | 130 | ....821247 | ...NTFS | .BBS | ......2048 | ....819200 | PRI | I
007 | 130 | ....821248 | ..FAT32 | ..BS | ....821248 | ....614400 | PRI | I
008 | 130 | ....821254 | ..FAT32 | .BBS | ....821248 | ....614400 | PRI | I
009 | 130 | ...1697792 | ...NTFS | ..BS | ...1697792 | 1950905743 | PRI | .
010 | 130 | 1952604160 | ...NTFS | ..BS | 1952604160 | ....919552 | PRI | .
011 | 130 | 1953523711 | ...NTFS | .BBS | 1952604160 | ....919552 | PRI | .
130/278:47/LOG> DataCollection items found: 11 / 4
### DATACOLLECTION, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 130 | ......2048 | ...NTFS | ..BS | ......2048 | ....819200 | PRI
002 | 130 | ....821247 | ...NTFS | .BBS | ......2048 | ....819200 | PRI
003 | 130 | ....821254 | ..FAT32 | .BBS | ....821248 | ....614400 | PRI
004 | 130 | ....821248 | ..FAT32 | ..BS | ....821248 | ....614400 | PRI
009 | 130 | ...1697792 | ...NTFS | ..BS | ...1697792 | 1950905743 | PRI
010 | 130 | 1952604160 | ...NTFS | ..BS | 1952604160 | ....919552 | PRI
011 | 130 | 1953523711 | ...NTFS | .BBS | 1952604160 | ....919552 | PRI
130/278:47/LOG> PartList items created: 4
### PARTLIST ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ... | ..1 | ..2 | ..0 | ..1 | ..1 | ..1 | 2 | ..A
002 | ..FAT32 | ... | ..4 | ..3 | ... | ..4 | ..4 | ..4 | 2 | ..B
003 | ...NTFS | ... | ..9 | ... | ..0 | ..9 | ..9 | ..9 | 1 | ..B
004 | ...NTFS | ... | .10 | .11 | ..0 | .10 | .10 | .10 | 2 | ..A
### PARTLIST, INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | ......2048 | ....819200 | ....821247 | PRI | ..A | ..V
002 | ..FAT32 | ....821248 | ....614400 | ...1435647 | PRI | ..B | ..V
003 | ...NTFS | ...1697792 | 1950905743 | 1952603534 | PRI | ..B | ..V
004 | ...NTFS | 1952604160 | ....919552 | 1953523711 | PRI | ..A | ..V
130/278:47/SST> SaveState requested for disk 2 (130)
130/278:47/WAS> AdmiSectors in use : 0+ 1- 2+
130/278:47/SST> SaveState completed for disk 2 (130)
130/278:47/EXE> Analysis complete
130/278:58/LOG> RunTime: 278:58
130/278:58/LOG> ### CLOSE LOG ###
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #12 on: June 12, 2016, 10:01:04 PM »

Questions:
- You mention a 930 Gb disk, none of the disks here is 930. How does that work?
- Did you clone TO the 2TB disk, if so, did that disk have stuff on it before you cloned?
- The log shows DiskPatch to be in demo mode, how did you clone a disk?

I see a 930 Gb disk in the geo check section, did you perhaps disconnect the 930 disk?

The fact that the disk health log is incomplete is a bad sign; at least one disk is in bad shape, or some other piece of disk related hardware is not working well.
Logged

mrbb
member

Posts: 9


« Reply #13 on: June 13, 2016, 08:46:23 AM »

The disk is a Toshiba MQ01ABD100 1000GB interne Festplatte

the 2 GB disk I cloned to had stuff on it, I think I formatted it with Windows 8 before

I have diskpatch on a USB stick and bought a key and gived it in and it is just runnig

during analyse I did not disconnected the disk

The disk was for about 2 jears in a new notebook, then I replaces it by a ssd disk and connected it as second disk e:
the problems started theat all data where shown in the explorer but windos could not open any file. I have the idea that a windows update danaged something in the strukture
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1472


WWW
« Reply #14 on: June 13, 2016, 10:39:47 AM »

Sorry but this gets more confusing over time. I can't get a good picture of what is going on here so I'll offer some generic advice:

As stated before, when cloning a bad disk it is unlikely that the resulting clone is working perfectly. This means you will have to work on the cloned disk with a tool like iRecover; this will allow you to access the data when normal access (because of corruption or because areas of the disk were skipped) is not possible.

It is best when a target disk is completely empty before starting a clone. If there is data on the target disk (before you clone to it) it will interfere with the recovery when running iRecover (all this is in the manual's cloning section and in the guides, look there for more details).

Your cloning took a long time so I'm assuming the source disk is in bad shape. All you have now is the clone. Run an iRecover analysis on the clone and see if data can be recovered. If so proceed with iRecover.
Logged

Pages: [1] 2 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!