During the process of a storage scan, R-Explorer may spot an error related to disk partition issues. This is, namely, disk partition, incorrect size or even overlapping. The causes for this error can be absolutely different leading to the same result: recovery scan may be incorrect.




Disk partition overlapping may occur for one of the following reasons:

Disk is part of a RAID or a spanned storage



In case of RAID, the logical volume you are trying to scan does not consist of the only disk. It relies on several logical storages, which are gathered into one system and don’t function independently. Therefore, you should take all such system components and gather them into this system again. Luckily, R-Explorer in its RAID Recovery and Professional editions ensures the related tool – RAID Builder. The latter will let you define the required configuration and general RAID parameters resulting into virtual RAID storage reconstruction and its preparation for further scan process. RAID assembly is mandatory! If the RAID storage is not assembled before recovery, the storage will only contain a part of the data, and the recovery result can be incorrect with a high rate of possibility.



Incorrect storage size


Data storage connection matters! Hard drives attached via a SATA/USB adapter can raise some questions especially for disks of over 2 TB. A bridge chip of the adaptor may be incapable of transferring data located at large addresses because of its data transmission ability. For this reason, disk sizes displayed in the program can differ from the real ones. The same problem may also arise for internal drives in case of a poor bandwidth of an old motherboard.

Incorrect sector size


Usually, a disk manufacturer defines physical sector size on a hard drive as 512 bytes or 4KB. At the same time, logically it can be divided into 512 bytes, even if the size of a physical sector is 4KB. If, for some reason, a driver error or misconfiguration in defining the correct sector size happens, the partition size in the program can be defined as a shorter one or as the one with an overlap. In such case, you can try attaching the disk via a new hardware or just ignore disks partitions and run the full storage scan.

Partition metadata corruption


Misreading of the partition metadata area may appear for a number of reasons including power cutoffs or any logical failures. As a result, the metadata area becomes overwritten with a new information and can be not recognized or show incorrect information about the partitions. The only recommended scan option here is to make the software carry out a full-disk scan.

The software will inform you about the overlapping error in different ways. First, it may highlight the partition red at the very start giving a corresponding warning at the information panel. Second, it will present the same issue at the scan step.




R-explorer will try fixing the trouble adjusting its size to the disk size. Yet, it is important that you pay attention to the problem and try removing it where possible for the purposes of a more correct data recovery scan.