vSAN OSA - Create vSAN Disk Groups failure where there are multiple Cache SSDs
Article ID: 410836
Updated On:
Products
Issue/Introduction
Create vSAN Disk Groups action is failing in SDDC Manager Day N workflows. This appears to occur when the host lacks sufficient disks for disk group formation.
Environment
VCF 9.0
vSAN
Cause
In vSAN OSA, Each disk group must consist of precisely one cache disk and between one and seven capacity disks. The current issue appears because of an additional SSD disk that lacks a corresponding HDD disk, which is essential for the formation of a proper disk group.
The illustration below depicts this situation, highlighting an extra SSD disk that does not have the necessary accompanying HDD disk to constitute a valid disk group.
|----------------------------------|
| DiskName | Type |
|----------------------------------|
| naa.58ce38ee20ca6179 | ssd |
| naa.50000399c80851b1 | hdd |
| naa.5000cca0a502ac8c | ssd |
| naa.50000399c80909c9 | hdd |
| naa.5000cca0a502ac64 | sdd | -- extra ssd disk without accompanying HDD disk
------------------------------------
Resolution
To resolve this issue, mark a single SSD disk as a vSAN Direct Disk and restart the workflow.
1. Get the disk name using vdq -q.
2. Use the command below to mark the disk as a vSAN Direct disk:
esxcli vsan storage tag add -d <disk-name> -t vsanDirect
Feedback
