Migration validation failure "Disk size is not a multiple of 1024. RAV/Bulk migration is not supported"
Article ID: 321628
Updated On:
Products
Issue/Introduction
When attempting HCX migration, validation fails with the error "Disk size is not a multiple of 1024, RAV/Bulk migration is not supported" preventing migration workflow from proceeding. This occurs when VM disk sizes do not align with the required block size multiples for the specific disk size range.
The validation error may display in the HCX UI with similar messages:
"Disk size is not a multiple of 8192, RAV/Bulk migration is not supported""Disk size is not a multiple of 16384, RAV/Bulk migration is not supported"
Environment
VMware HCX
Cause
VM disk sizes are not exact multiples of the required block size for their size range. HCX validates disk sizes against specific block size requirements based on the disk size range.
Resolution
The changes to the VM's vmdk configuration must be performed through vCenter before the HCX migration workflow.
Workaround:
IMPORTANT: In HCX version prior to 4.3 or earlier, The verification was done to verify if disk size is in multiple of 1024 bytes only.
From HCX version 4.4 or later, additional checks on disk sizes has been done, as shown below:
- If the disk size is 2TB or less, the new size must be an exact multiple of 8KB
- If the disk size is between 2-8TB, the new size must be an exact multiple of 16KB
- If the disk size is between 8-32TB, the new size must be an exact multiple of 32KB
- If the disk size is between 32-64TB, the new size must be an exact multiple of 64KB
Calculation Reference:
- 1 kilobyte = 1024 bytes
- 1 terabyte = 1,099,511,627,776 bytes
Please refer to the chart below for further clarity:
| Disk Size Range | Block Size Required (B) |
|---|---|
| ≤ 2 TB | 8 KB (8 × 1024 = 8,192 bytes) |
| > 2 TB and ≤ 8 TB | 16 KB (16 × 1024 = 16,384 bytes) |
| > 8 TB and ≤ 32 TB | 32 KB (32 × 1024 = 32,768 bytes) |
| > 32 TB and ≤ 64 TB | 64 KB (64 × 1024 = 65,536 bytes) |
Acceptable Decimal Values for TB Sizing: When specifying disk sizes in TB, only these decimal values are allowed:
- X.125 TB
- X.25 TB
- X.375 TB
- X.5 TB
- X.625 TB
- X.75 TB
- X.875 TB
Examples: 4.25 TB is acceptable (a multiple of 1 MB). 4.252TB is not acceptable.
Note: GB disk sizes must have no decimal values.
Manual workaround steps:
Prerequisite: Ensure no backups are running on the source VM, and disable all backup operations temporarily.
1. Access the vCenter with the source affected VM name (object) --> Select "Actions" --> Select "Edit Settings.."
2. In the disk hardware configuration section for the disks, ensure that the disk values are in multiples of 8KB (8192 bytes) if the disk size is less than 2 TB. Use the modulus operator (%) to check if the remainder of division is zero:
- If
disk_size(in bytes) % 8192 == 0, if remainder is 0, then it's a multiple of 8192. - Otherwise, if the disk size is not a multiple of 8192, then we need to adjust the size of the disk, so that it becomes the multiple of 8192, you need to increase the disk size to a value which would be N, (N = 8192 - remainder) and now if you add the disk_size(in bytes) with N, you will get a New_disk_size which would be a multiple of 8192.
See below example:
Note: the seen UI is cut-off and actually has an appended at the end, integers '558794' at the end being " 1.8100000000558794 TB" these disks 7 and 8 would need to be identified as 8192 bytes.
3. Select the dropdown and change the disk sizing category from TB --> GB (sizing type) to add an appropriate integer value (without any trailing decimal point values). In the above example, a value of 1855 GB was used to resolve the issue
4. Click the "OK" button to save the VM settings
5. Retry HCX migration validation, and it should pass (log-out and log-in may assist with any unexpected web-browsing caching)
For RDMS:
Change the Disk size from the Storage end.
Additional Information
Feedback
