- Error reported in vCenter when attempting to apply a vSAN capacity license to a vSAN cluster with 4kn SWE devices.
"The reported vSAN capacity exceeds the quantity of the capacity license."
- Capacity count assigned for TiB is eight times larger than actual capacity of disks.
vSAN 8.0U3+
The disk size for 4kn SWE device is calculated incorrectly when reporting vSAN VCF license usage causing the vSAN TiB license not able to be applied, or count assigned for TiB is eight times larger than actual capacity.
- Verify use of 4k drives before running the attached script.
Logs contain the following:
hostd.log
hostd.log:2025-04-22T15:45:45.554Z In(166) Hostd[2099725]: [Originator@6876 sub=Libs opID=561366f8-92-2721-2722 sid=52842f88 user=vpxuser:VirtualCenter] VsanUtil: Device is 4Kn-SWE with 4k sector size.
hostd.log:2025-04-22T15:45:45.608Z In(166) Hostd[2099725]: [Originator@6876 sub=Libs opID=561366f8-92-2721-2722 sid=52842f88 user=vpxuser:VirtualCenter] VsanDiskLunImpl: Device is 4Kn-SWE with 4k sector size.
vsansystem.log
vsansystem.log:2025-04-22T16:03:32.676Z In(166) vsansystem[2099118]: [vSAN@6876 sub=Libs opId=226be806] VsanDiskLunImpl: Device is 4Kn-SWE with 4k sector size.
vsansystem.log:2025-04-22T16:03:32.678Z In(166) vsansystem[2099129]: [vSAN@6876 sub=Libs opId=5a4df391] VsanUtil: Device is 4Kn-SWE with 4k sector size.
Undertake the following on each host of the vSAN cluster:
1. Upload the attached script "newremediate4KnSweDeviceCapacity.py" to each ESXi host in the cluster, or to a shared datastore
2. Run script: "python newremediate4KnSweDeviceCapacity.py".
3. Attempt to apply license again and/or verify the correct assignment and TiB capacity count from VCenter at Menu > Infrastructure > Cluster > Configure > Licensing > VSAN License.
An example of drive type affected: Toshiba Product Id: AL15SEB18EP