-
Title
The partition size is incorrect, please shrink the volume. -
Description
After upgrade to Rapid Recovery, backups for one or more drives fail with "The partition size is incorrect, please shrink the volume".
In the Core UI the following error is displayed:
Transfer of volumes [X:\, Y:\, Z:\] from 'Hostname'.The transfer of one or more volume images from a protected machine to the Core has failed:* Invalid Operation Exception: The partition size is incorrect, please shrink the volume.In the AppRecovery.log file the following error error is logged:
Determining data to send for volume 'X:\' failed. Transfer of that volume will not be performed, but other volumes in this snapshot may still be processed
System.AggregateException depth 0: One or more errors occurred. (0x80131500) ---> (Inner Exception #0 depth 0) System.InvalidOperationException depth 1: The partition size is incorrect, please shrink the volume. (0x80131509)In agentless protection the error displayed is almost exactly the same except it refers to the volumes as \\Hard disk #\Volume #. For example [\\Hard disk 1\Volume 1, \\Hard disk 1\Volume 2 - Linux Swap, \\Hard disk 1\Volume 3]
-
Cause
This error is caused by the partitions on the hard disk being larger in size than the actual hard disk. Hence "the partition size is incorrect". This issue can occur in both Windows and Linux backups using both agent based and agentless backup methods. -
Resolution
Workaround 1: If running Windows 2008, Vista or later version, follow the steps below provided in KB Article 123207.
Gather the necessary information
- Open msinfo32 and go to Components->Storage->Disks
- Make note of the total size of the disk (the exact number of bytes shown in parentheses beside “size”)
- Make note of the partition sizes (again, the exact number of bytes), and the Partition Starting Offsets (in bytes)
Check for misalignment
- If you have multiple partitions on the same disk (e.g., Disk #0, Partition #0; Disk #0, Partition #1), add Partition Size and Starting Offset for Partition 0. Subtract that value from Partition 1′s Starting Offset. You should get either 0 or a positive number.
- For the last partition on the disk, add the Partition Size and Partition Starting Offset. Subtract this value from the disk Size. You should get either 0 or a positive number.
- If you get a negative number for either of these, it means your partition is misaligned by that number of bytes (divide it by 1024 twice to get the value in MB). This means your partition is either overlapping another partition, or it ends beyond the edge of the disk. This means that any data on the portion of the partition that does not have a corresponding part of the disk will become corrupted when it’s flushed to the disk. Similarly, any data on overlapping portions of the partitions will become corrupted.
Shrink the volume
- Open Disk Management. Right-click on the volume corresponding to the misaligned partition and shrink that volume by at least the amount by which it’s misaligned. For example, say the partition is misaligned by 5,471,232 bytes; this equates to approximately 5.2178 MB. You would need to shrink that volume by at least 6 MB.
Workaround 2: If the server is a Virtual Machine.
- Increase the affected virtual disk by 1 - 2 GB.
- To increase the size of a virtual disk in VCenter/ESXi please follow this VMware KB Article.
- To increase the size of a virtual disk in Hyper-V please follow this Microsoft KB Article.
- Attempt the backup again