Areca RAID adapter saves the raid configuration in each disk of each raidset to support raid roaming. The firmware will check each disk's configuration data to determine which disk in which raidset. The configuration data conatins time stamp, hdd model name, serial number ... etc. In some rare case, a raidset may be splitted to multiple raidset (due to different time stamp, model name, serial number ...etc, this condition may occur during updating of raidset configuration data and exception occurs,.e.g. power loss, improper user action, firmware hang(due to bug)). We need methods to reconstruct the raid configuration data to recover data in raid set.

 (A) RESCUE: Assume only different time stamp (by ignoring the time stamp during re-constructing raid config)

(B) LeVeL2ReScUe: Assume most config data is inconsistent. User must make sure only one raidset in the raid controller. This method only checks the sequence number during reconstructing raid config.
(C) No Init: Assume all hdd's configuration data is lost, this method will only write config data and do not write user data area (no RAID1/3/5/6 initialization will be invoked). Try and error may be needed to recover user data because we assume original raid level, stripe size, volume size, number of disks may be unknown.