Crash in irecover scanning for partition layout

[tyab]

I have a windows 7 x64 system with a 2x1TB raid 0 secondary data drive. The Raid 0 was created using windows disk manager as a dynamic disk, not through a raid controller. I corrupted the partion table of one of the raid 0 drives though incorrect usage of norton ghost. With the one corrupted drive, windows no longer sees the drives as a valid raid, the disk management shows them as two dynamic drives, both in a failed state.

I am trying out your irecover product.

It is able to see the two volumes, and able to complete the two quick scans. When presented with the partition layout, I choose NO and then right click on it and ask it to scan for partition layout.

Everytime I do this - the following crash quickly happens:

  http://tyab.net/image/irecovercrash.jpg


Thanks

[Joep]

Hello,

In this case there are 2 possible scenarios, and scanning for a lost/deleted partition is in neither one of them:

1. iRecover detects the LDM after selecting a disk in simple recovery mode and presents you with the volume(s) defined in the LDM. In which case you then select a volume and let iRecover work out RAID related parameters.

2. If the LDM is lost, overwritten etc., you need to do 'Reconstruct RAID layout' and feed it the physical disks so iRecover can work out array parameters first. If successful but no volumes are presented, select 'define manually' and then select 'there was only one volume ...'.

[tyab]

The point I wanted to make is that the product is crashing when I try that feature. Here is a .zip of the debug log file.

http://tyab.net/files/irecoverlogfile.zip

That said, instead of letting irecover scan for the partitions, I simply told it that I had full disk partition and it was then able to locate a vast majority of the files. Being a trial, I could not copy them, but at least it proved to me that I can recover most of the files. Enough for me to decide to purchase the product and I am currently backing up those recovered files.

And I did also try out one of your competitors products, Disk Internals Raid Recovery (trial version), and overall both products seemed able to recover the same type/number of files but your UI is far superior (in my opinion) and your product was able to do the scan and present me with the list of files in under 2 hours, while Disk Internals Raid Recovery took over 9 hours and seemed to have a hard time reconstructing the root directory where your product found all but handful of the directories in the root.  As  stated above, good enough for me to make a purchase decision and buy irecover pro.

If your programmers need more info on how to recreate the crash, I am willing to help. If I have some free time, I'll try and run irecover under VS2010 and generate a minidump for them.

[Joep]

Hello,

Ok, understood! It was my intention to get you in the right direction as quickly as possible. I took a look at the log file, unfortunately it does not provide any pointers with regards to the error. The partition scan is actually so simple and straight forward that there aren't many things that can go wrong. Errors in this routine are so rare we can count them on one hand since iRecover 1. Errors we did see were related to non responding disks, though we do not have much reason here to assume one of you disks is physically bad in some way.