Raid reconstructor software faq – runtime software products how do u get trichomoniasis

A. There are two ways. The first is to right click on the white space to the right of the drive number, you will have a drop down list to choose from. The second way is to click the three periods at the end of the white place and the same drop down list will appear.

A. There are two reasons why this can happen. If you are running Windows Vista or above, you need to close RAID Reconstructor and reopen it by right clicking on the RAID Reconstructor icon and choosing Run As Administrator. The second reason is that the drives are still attached to the RAID controller which hides the physical drives from Windows. Attach the drives to a non-raid controller and you shoudl then see them in the list.

A. Yes. If you have 4 drives, tell RAID Reconstructor that you have 4 drive and enter the three good drive while leaving one of the drive numbers empty.

The software will rebuild the missing drive from the XOR data of the other three drives. This is the same regardless of how many drives you have.

A. The analyze phase with 11 drives can take a few days due to the number of combinations where the block size, rotation, and start sector are concerned. 12 drives would take almost 7 years to analyze due to the exponential increase in the number of drives. If you know the exact parameters for the array, you can enter them into the main screen and skip to step 3. If you do not know the exact parameters, we can determine the parameters in less than 24 hours with our RaidProbe Service.

A. The differential Entropy test will try to determine the best starting sector, and block size of the array. Once it determines them, it shows a preview of the settings to you, to allow you to make any changes, before it analyzes the data. This is the best solution if you are unaware of the parameters of your array.

A. This allows you to manually pick your starting sector, block size, sectors to probe, and rotation. This is useful if you have an idea of what the block size, rotation or what the start sector is and will speed up the analysis by excluding the ones you know are incorrect.

A. This means the software did not find the proper parameters for your array. There are many reasons this could happen. If you have excessive file system damage, if your array is using a proprietary order or rotation, if the start sectors on the drives are different, and many more. In a case like this, we recommend using our RaidProbe Service and let us determine all the parameters for your array.

A. Look at the message and it will tell you what drive the error occurred on. If it is a RAID 5, remove that drive from the drive listing in step 1 and run the analysis again. If you get more sector read errors, make images of the drives as soon as possible and then proceed using the images. If it is a RAID 0, make images of the drive and use the images instead of the physical drives.

A. No. RAID Reconstructor does not look at the array on a file level, so there is not a way to do this. The scope of the software is to determine the parameters of the array only. By getting a recommendation in step 2, you know that you are getting the correct parameters of the array and provided there is no major file system damage, you should be able to recover the data from the reconstructed array.

A. A virtual image is an XML document that tells our other software (DiskExplorer, GetDataBack, and Captain Nemo) how the array is put together and pulls the data directly from the physical media. This prevents you from having to output an image that is the full size of the array or writing the data to a new drive before recovering the data.

A. It outputs a small file (less than 3kb in most cases) that will allow you to recover the data using our other software (DiskExplorer, GetDataBack, and Captain Nemo) without the need for a full image or the data being written to a new drive first.

A. This outputs a raw image file that is the same size of the array. For example, if the array is 600GB, this will output a 600GB file, regardless of how much data is on the array. This is useful if you have a different recovery software you wish to use.

A. This allows you to write the data back to a new drive directly. This is useful if you only have a controller failure, you can write the data to a new drive, reboot and have full access to the data. You may even be able to put the drive back in the machine the array was on and boot from it. This will destroy any data on the drive, so be careful when using this feature.

A. Once the Virtual Image/Image is made, these links open the image in the application link you choose. For example, if you have a virtual image and you click the Captain Nemo link and you have Captain Nemo installed, Captain Nemo will launch and the image will mount itself up and present the data to you (provided there is not any file system damage preventing Captain Nemo from mounting the image). If the application you choose is not installed, you will be presented with a link to download the software first.

A. Any single file RAW image will work, unless it is created by our software, then a multi-file image can be used. You can not use an encase image, however you can output that encase image to a single file DD image and use that in RAID Reconstructor.

A. You can create an image in either GetDataBack, Captain Nemo, or DiskExplorer. Each has its own way to create an image so check the help file in each of them. They all produce the same type of image file. Do not use DriveImage XML as that is not a compatible image for data recovery.

A. A RAID 10 (1+0) is two RAID 0’s put together. You need to determine which drives belong to each side of the RAID 0 and then use RAID Reconstructor to analyze the RAID 0. If you can not determine the correct drives on each side, you should use our RaidProbe Service and let us take care of it for you.

A. You need to move the drives into a working machine as slave drives or you can use a bootable CD with our software on it to get access to the drives. The drives need to be attached to a non-raid controller for this to work. You can find all the details about creating a bootable CD here.

A. USB does not support error checking, therefore the data that RAID Reconstructor is using could be unusable and corrupt your recovery. Do not use USB drives for data recovery purposes. Remove the drive from the external case and install it internally.

A. A NAS usually is a Linux software RAID. You need to find the start of the RAID partition, usually the last and biggest partition. Run the analysis from there. A more convenient way is our new software NAS Data Recovery that does all the work for you.