Welcome, Guest. Please login or register.
Did you miss your activation email?
May 20, 2013, 12:52:45 AM
Home Help Search Login Register
News: Using Internet Explorer 8? Use compatibility mode when posting!

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  Diskpatch in loop and not fixing
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Diskpatch in loop and not fixing  (Read 1019 times)
mellowd
member

Posts: 4


« on: November 09, 2009, 04:23:08 AM »

Hi there.

I recently bought diskpatch to recover a lost 2TB partition. If I do a quick scan it shows that it has found a 2TB array. It then allows me to fix it. However when I do this and then list partitions again it shows the partition as 50MB which is incorrect.

I've tried running a full scan, but when it gets to 100% it starts a 0% and starts again. I thought it was doing extra checks so left it to hit 100% a second time and it then looped back to 0% once more.

As this is a 2TB array it takes around 12 hours each time to go from 0 - 100%  - any ideas what I can do here?
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1152


WWW
« Reply #1 on: November 09, 2009, 09:12:04 AM »

Hello,

Quote
any ideas what I can do here?

No not really, without the logfile.
Logged

--
Kind regards,
Joep
mellowd
member

Posts: 4


« Reply #2 on: November 09, 2009, 12:27:10 PM »

Hi,

This is the log in C:\Program files(x86)\DIY DataRecovery iRecover

But we ran this latest scan from the boot CD - does it still write logs here? Thanks!

Init done - logging
Init start - misc
Init done - misc
Init start - types
Init done - types
Init start - caches
Init done - caches
Thread startup: copier, TID 000007AC
Optimizing for 0 CPU(s)
Init start - files
Init done - files
Init start - ident processing
Performance: Ident data query (3 of 3) 0s
Performance: Ident data query (9 of 9) 0s
Performance: Ident data query (2 of 9) 0s
Init done - ident processing
Init start - physical devices
Init done - physical devices
File management init done with a status of 88
NT 5.2.3790 Service Pack 2; 4095 MB RAM
Open physical drive 00000100 success, 69973 MB : HP LOGICAL VOLUME - Port 2, Bus 0, Target 4, LUN 0; maxLBA=143305920
Open physical drive 00000101 success, 205 GB : HP LOGICAL VOLUME - Port 2, Bus 0, Target 5, LUN 0; maxLBA=429925920
Open physical drive 00000102 success, 2047 GB : HP LOGICAL VOLUME - Port 4, Bus 1, Target 0, LUN 0; maxLBA=4294967295
Open physical drive 00000103 success, 2047 GB : HP LOGICAL VOLUME - Port 4, Bus 1, Target 1, LUN 0; maxLBA=4294967295
Open physical drive 00000104 success, 95 GB : HP LOGICAL VOLUME - Port 4, Bus 1, Target 2, LUN 0; maxLBA=200425920
Open physical drive 00000105 success, 2047 GB : HP LOGICAL VOLUME - Port 4, Bus 1, Target 3, LUN 0; maxLBA=4294967295
Open physical drive 00000106 success, 2047 GB : HP LOGICAL VOLUME - Port 4, Bus 1, Target 4, LUN 0; maxLBA=4294967295
Open physical drive 00000107 success, 2047 GB : HP LOGICAL VOLUME - Port 5, Bus 1, Target 0, LUN 0; maxLBA=4294967295
Open physical drive 00000108 success, 2047 GB : HP LOGICAL VOLUME - Port 5, Bus 1, Target 1, LUN 0; maxLBA=4294967295
Open physical drive 00000109 success, 2047 GB : HP LOGICAL VOLUME - Port 5, Bus 1, Target 2, LUN 0; maxLBA=4294967295
Open physical drive 0000010A success, 2047 GB : HP LOGICAL VOLUME - Port 5, Bus 1, Target 3, LUN 0; maxLBA=4294967295
Open physical drive 0000010B success, 2047 GB : HP LOGICAL VOLUME - Port 6, Bus 1, Target 0, LUN 0; maxLBA=4294967295
Open physical drive 0000010C success, 2047 GB : HP LOGICAL VOLUME - Port 6, Bus 1, Target 1, LUN 0; maxLBA=4294967295
Open physical drive 0000010D success, 2047 GB : HP LOGICAL VOLUME - Port 6, Bus 1, Target 2, LUN 0; maxLBA=4294967295
Open physical drive 0000010E success, 2047 GB : HP LOGICAL VOLUME - Port 6, Bus 1, Target 3, LUN 0; maxLBA=4294967295
Open physical drive 0000010F success, 95 GB : HP LOGICAL VOLUME - Port 6, Bus 1, Target 4, LUN 0; maxLBA=200425920
Open physical drive 00000110 success, 931 GB : Maxtor Basics Desktop; maxLBA=1953525168
Starting RAID5 parity check
Parity detected in 1% of 200 tests
One drive will be rebuit for RAID5 tests
Raw scanner starting on disk 0102 from LBA 0 to LBA 4294967295
Raw scanner starting on disk 0103 from LBA 0 to LBA 4294967295
ALERT!: MFT entry with alloc size 24 was encountered during identification; Base record ID 98128304
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 98142F04
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 981937C4
ALERT!: MFT entry with alloc size 3538994 was encountered during identification; Base record ID 981B43C4
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 981DA1C4
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 981ECB04
ALERT!: MFT entry with alloc size 30039544 was encountered during identification; Base record ID 982015C4
ALERT!: MFT entry with alloc size 3145776 was encountered during identification; Base record ID 9821CBC4
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 9725A3C4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97262F44
ALERT!: MFT entry with alloc size 6 was encountered during identification; Base record ID 97263284
ALERT!: MFT entry with alloc size 48 was encountered during identification; Base record ID 972661C4
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 97289F44
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 9728A284
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 972A5344
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 972A9BC4
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 972ACB04
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 972ADEC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 973149C4
ALERT!: MFT entry with alloc size 2359304 was encountered during identification; Base record ID 97356DC4
ALERT!: MFT entry with alloc size 4784164 was encountered during identification; Base record ID 973595C4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 973667C4
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 97375BC4
ALERT!: MFT entry with alloc size 1249378304 was encountered during identification; Base record ID 97387104
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 9738BDC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 973907C4
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 973A33C4
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 973A7DC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 973B41C4
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 973B5DC4
ALERT!: MFT entry with alloc size 4096 was encountered during identification; Base record ID 973C19C4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 973E7FC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 973EA7C4
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 973F5FC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 973F95C4
ALERT!: MFT entry with alloc size 3342409 was encountered during identification; Base record ID 973FBDC4
ALERT!: MFT entry with alloc size 4096 was encountered during identification; Base record ID 9740BDC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97463344
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97463684
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 9746F1C4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 974783C4
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 974897C4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 9752A544
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 9752A884
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 9752C744
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 9752CA84
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 9752E944
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 9752EC84
ALERT!: MFT entry with alloc size 184 was encountered during identification; Base record ID 97530B44
ALERT!: MFT entry with alloc size 1 was encountered during identification; Base record ID 97530E84
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97545144
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 97545484
ALERT!: MFT entry with alloc size 24 was encountered during identification; Base record ID 97547344
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97547684
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97549544
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 97549884
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 9754B744
ALERT!: MFT entry with alloc size 2712701808 was encountered during identification; Base record ID 9754BA84
ALERT!: MFT entry with alloc size 6 was encountered during identification; Base record ID 97555944
ALERT!: MFT entry with alloc size 262 was encountered during identification; Base record ID 97555C84
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 97557B44
ALERT!: MFT entry with alloc size 393256 was encountered during identification; Base record ID 97557E84
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97559D44
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 9755A084
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 9756E344
ALERT!: MFT entry with alloc size 4096 was encountered during identification; Base record ID 9756E684
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97574144
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 97574484
ALERT!: MFT entry with alloc size 24 was encountered during identification; Base record ID 97577D44
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 9757E144
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 9757E484
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 975881C4
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 9758C5C4
ALERT!: MFT entry with alloc size 4096 was encountered during identification; Base record ID 975ED5C4
ALERT!: MFT entry with alloc size 65720 was encountered during identification; Base record ID 976497C4
ALERT!: MFT entry with alloc size 32571392 was encountered during identification; Base record ID 97752744
ALERT!: MFT entry with alloc size 32833536 was encountered during identification; Base record ID 97752A84
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 97756FC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 97768D44
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 977881C4
ALERT!: MFT entry with alloc size 4259926 was encountered during identification; Base record ID 9778E7C4
ALERT!: MFT entry with alloc size 65680 was encountered during identification; Base record ID 9778F5C4
ALERT!: MFT entry with alloc size 4259891 was encountered during identification; Base record ID 97798DC4
ALERT!: MFT entry with alloc size 65560 was encountered during identification; Base record ID 9779FCC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 977B8F44
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 977B9284
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 977BED44
ALERT!: MFT entry with alloc size 131072 was encountered during identification; Base record ID 977BF084
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 977D6B44
ALERT!: MFT entry with alloc size 7077934 was encountered during identification; Base record ID 977D77C4
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 977DC884
ALERT!: MFT entry with alloc size 4096 was encountered during identification; Base record ID 977E99C4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 978061C4
ALERT!: MFT entry with alloc size 40 was encountered during identification; Base record ID 97809304
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 978239C4
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 9783D144
ALERT!: MFT entry with alloc size 14 was encountered during identification; Base record ID 9783D484
ALERT!: MFT entry with alloc size 24 was encountered during identification; Base record ID 97845784
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 978BABC4
ALERT!: MFT entry with alloc size 65536 was encountered during identification; Base record ID 66123384
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 661A5F44
ALERT!: MFT entry with alloc size 4456502 was encountered during identification; Base record ID 661BFFC4
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 661FF344
ALERT!: MFT entry with alloc size 104 was encountered during identification; Base record ID 661FF684
ALERT!: MFT entry with alloc size 3735601 was encountered during identification; Base record ID 66235DC4
ALERT!: MFT entry with alloc size 3211314 was encountered during identification; Base record ID 662C35C4
ALERT!: MFT entry with alloc size 4259926 was encountered during identification; Base record ID 662E0884
ALERT!: MFT entry with alloc size 3211314 was encountered during identification; Base record ID 662E57C4
ALERT!: MFT entry with alloc size 30039543 was encountered during identification; Base record ID 662E93C4
ALERT!: MFT entry with alloc size 65536 was encountered during identification; Base record ID 662EC5C4
ALERT!: MFT entry with alloc size 18 was encountered during identification; Base record ID 6630D944
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 66331744
ALERT!: MFT entry with alloc size 4096 was encountered during identification; Base record ID 66358284
ALERT!: MFT entry with alloc size 18 was encountered during identification; Base record ID 6638C284
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 6639ED84
ALERT!: MFT entry with alloc size 3145776 was encountered during identification; Base record ID 663B1D44
ALERT!: MFT entry with alloc size 3342387 was encountered during identification; Base record ID 663B2084
ALERT!: MFT entry with alloc size 30039544 was encountered during identification; Base record ID 6640CDC4
ALERT!: MFT entry with alloc size 104 was encountered during identification; Base record ID 6643AF44
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 6643F5C4
ALERT!: MFT entry with alloc size 24 was encountered during identification; Base record ID 66463544
ALERT!: MFT entry with alloc size 18 was encountered during identification; Base record ID 66488684
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 6648F984
ALERT!: MFT entry with alloc size 4259926 was encountered during identification; Base record ID 664943C4
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 664A3904
ALERT!: MFT entry with alloc size 65536 was encountered during identification; Base record ID 664A4084
ALERT!: MFT entry with alloc size 3604530 was encountered during identification; Base record ID 664A5944
ALERT!: MFT entry with alloc size 65560 was encountered during identification; Base record ID 664A5C84
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 664A9184
ALERT!: MFT entry with alloc size 18 was encountered during identification; Base record ID 664B2084
ALERT!: MFT entry with alloc size 0 was encountered during identification; Base record ID 66504744
ALERT!: MFT entry with alloc size 4294965888 was encountered during identification; Base record ID 66504A84
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1152


WWW
« Reply #3 on: November 09, 2009, 12:41:32 PM »

Hello,

Since you were asking about DiskPatch, I was actually hoping for a Diskpatch logfile:
http://www.diydatarecovery.nl/dp_manual/guide_supportanalysis.htm

And what happened to the disk you are trying to repair in the first place?
Logged

--
Kind regards,
Joep
mellowd
member

Posts: 4


« Reply #4 on: November 09, 2009, 12:54:02 PM »

Ah, okay, I think we just tried running diskpatch without the create a support analysis log selected - do you know how long this process will take? I'll get on it now.

Thanks
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1152


WWW
« Reply #5 on: November 09, 2009, 01:00:12 PM »

Hello,

It takes about the same time as running a full scan. You will need something to write the logfile to, a CD/DVD does not qualify as we can not write to that from DOS.
Logged

--
Kind regards,
Joep
mellowd
member

Posts: 4


« Reply #6 on: November 09, 2009, 01:29:52 PM »

Hi,

The screen just says InitDisk and has been like this for 30 mins - is this to be expected?

Thanks,
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1152


WWW
« Reply #7 on: November 09, 2009, 01:34:08 PM »

No. You ran it before didn't you?
Logged

--
Kind regards,
Joep
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.17 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!