VMware vSAN 6.x
VMware vSAN 7.x
VMware vSAN 8.x
This issue might occur if there is an unknown or stale disk present on the host that is not recognized by CMMDS (Cluster Monitoring, Membership, and Directory Services). This discrepancy can trigger the "physical disk health retrieval" alarm, causing the disks to show as unhealthy.
"vdq -iH"DiskMapping[0]: SSD: naa.xxxxxxxxxxxxxxxx MD: naa.xxxxxxxxxxxxxxxx MD: naa.xxxxxxxxxxxxxxxx DiskMapping[2]: SSD: naa.xxxxxxxxxxxxxxxx MD: naa.xxxxxxxxxxxxxxxx MD: naa.xxxxxxxxxxxxxxxx MD: naa.xxxxxxxxxxxxxxxx DiskMapping[4]: SSD: naa.xxxxxxxxxxxxxxxx MD: naa.xxxxxxxxxxxxxxxx MD: naa.xxxxxxxxxxxxxxxx MD: naa.xxxxxxxxxxxxxxxx"esxcli vsan storage list"Unknown: Device: Unknown Display Name: Unknown Is SSD: false VSAN UUID: yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy VSAN Disk Group UUID: VSAN Disk Group Name: Used by this host: false In CMMDS: false On-disk format version: -1 Deduplication: false Compression: false Checksum: Checksum OK: false Is Capacity Tier: false Encryption Metadata Checksum OK: true Encryption: false DiskKeyLoaded: false Is Mounted: false Creation Time: Unknown