Home \ Manual \ Configuring RAID recovery

Configuring RAID recovery

ZAR has been discontinued
After about twenty years, I felt ZAR can no longer be updated to match the modern requirements, and I decided to retire it.

ZAR is replaced by Klennet Recovery, my new general-purpose DIY data recovery software.

If you are looking specifically for recovery of image files (like JPEG, CR2, and NEF), take a look at Klennet Carver, a separate video and photo recovery software.
General considerations

RAID recovery mode of ZAR X is used to recover data when the array configuration (such as stripe size, or the order of the array member disks) is lost. If you determine the situation involves RAID reconstruction, select the "RAID Recovery" mode in Introduction panel.

The drives should be accessible as separate devices. This means you should either connect them to the regular (non-RAIDed) ports, or reconfigure the RAID controller as required to provide access to the drives independently.

Select RAID member disks

Select disks which are members of the array. If the array is RAID5 with one disk missing, select all available array members - the missing disk will be reconstructed based on the RAID5 parity data.

Clicking by the disk on the left, you get the detailed information about the disk on the right panel. You can use disk image files as array member disks. To load image files use More Functions button.

Specify RAID layout

There are two layout types available, namely "RAID0, RAID10, or RAID01" and "RAID5".

Stripe sizes are measured in sectors, rather than in kilobytes. Calculation is simple: 1KB = 2 sectors. Maximum stripe size limit is 2048 sectors (1MB). Generally, stripe size detection is pretty reliable, so it is recommended that you leave this setting as is. Factory default is minimum 1, maximum 2048 sectors.

Input restrictions and recommendations

If one disk is missing from a RAID5 array, mark all the available members of the array. The missing disk will be reconstructed automatically.

Avoid ordering to search the drive that was not a member of the array. This is especially important in case of a RAID5, because an additional drive will cause parity recalculation, resulting in even more disks to search, and the algorithm might get lost in all the possibilities.

Copyright © 2001 - 2023 Alexey V. Gubin.