vSAN Health Service - Physical Disk Health - Disk licensed capacity consistency

Products

• VMware vSAN
• VMware Cloud Foundation

Issue/Introduction

This article introduces the new vSAN Health check 'Disk licensed capacity consistency' in vSAN and provides details on why it might report the error and how to fix the error.

Environment

VMware vSAN 9.1

Resolution

Q: What does the 'Disk licensed capacity consistency' health check do?

• It verifies consistency between vSAN in-use disks and the disk information stored in the license system.
• It checks for any PDL (Permanent Device Loss) disks and disks not correctly registered in the license system.
• These kinds of disks will either cause higher capacity reporting than actual usage or restricted operations.

Q: What does it mean when it is in an error state?

• If this health check shows alerts, it indicates an inconsistency between the vSAN disks in use and the disk information recorded in the license system.
• This issue may lead to restricted I/O operations, data access failures, or potential risks to data integrity.
• Witness hosts and OSA cache disks are excluded from this check. 

Q: How does one troubleshoot and fix the error state?

Please follow the guidelines  below to fix each disk licensed capacity inconsistency issue:

Issue	Health State	Troubleshooting Steps
The vSAN in-use disk is out of vSAN license control	UNHEALTHY	SSH to the ESXi host and claim the disk via ESXCLI command: Connect to the ESXi host using SSH. Claim the disk via ESXCLI command with the disk UUID or name. For ESA cluster:  esxcli vsan storagepool mount --disk <disk name> esxcli vsan storagepool mount --uuid <disk uuid> For OSA cluster: esxcli vsan storage diskgroup mount --disk <disk disk> esxcli vsan storage diskgroup mount --uuid <disk uuid>
The vSAN in-use disk has a smaller capacity than the capacity kept in the license system	INFO	Remove the disk and reclaim it using vSphere Client UI. In vSphere Client UI, select the cluster and navigate to "Disk Management" Select the host and click "VIEW DISKS". Remove the disk: For ESA cluster: Select the disk name and click "REMOVE DISK", remove the disk with "Ensure accessibility" or "Full data migration" option. For OSA cluster: Under the Disk group, select the disk name and click "REMOVE DISK", remove the disk with "Ensure accessibility" or "Full data migration" option.      4. Reclaim the disk: For ESA cluster: Click "ADD DISKS", select the disk name and click "ADD". For OSA cluster: Expand the three-dot menu from the Disk group, click "Add Disks", select the disk name and click "ADD".
The vSAN in-use disk has a larger capacity than the capacity kept in the license system	UNHEALTHY	Remove the disk and reclaim it using vSphere Client UI. In vSphere Client UI, select the cluster and navigate to "Disk Management" Select the host and click "VIEW DISKS". Remove the disk: For ESA cluster: Select the disk name and click "REMOVE DISK", remove the disk with "Ensure accessibility" or "Full data migration" option. For OSA cluster: Under the Disk group, select the disk name and click "REMOVE DISK", remove the disk with "Ensure accessibility" or "Full data migration" option.      4. Reclaim the disk: For ESA cluster: Click "ADD DISKS", select the disk name and click "ADD". For OSA cluster: Expand the three-dot menu from the Disk group, click "Add Disks", select the disk name and click "ADD".
The disk kept in the license system is not recognized and used by vSAN	INFO	SSH to the ESXi host and remove the disk via ESXCLI command. Attempt to connect to the ESXi host using SSH. Remove the disk via ESXCLI command: For ESA cluster:  esxcli vsan storagepool remove --disk <disk name> esxcli vsan storagepool remove --uuid <disk uuid> If the disk removal operation failed repeatedly, use -f|--force to forcefully remove the disk, such as: esxcli vsan storagepool remove --disk <disk name> -f For OSA cluster: esxcli vsan storage remove --uuid <disk uuid>