VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
IsSSD?: 0
IsPDL?: 0
DiskResult[10]:
Name: mpx.vmhba32:C0:T0:L0
VSANUUID:
State: Ineligible for use by VSAN
Reason: Has partitions
IsSSD?: 0
IsPDL?: 0
DiskResult[12]:
Name: eui.a15eb52c6f4043b5002471c7886acfaa
VSANUUID: 52c62b40-77a5-7a06-21ec-decd04e21fef
State: In-use for VSAN
Reason: None
IsSSD?: 1
IsPDL?: 0
In this truncated output, there is one disk “Ineligible for use by VSAN”
because it “Has partitions”. In fact, this is the boot device for this ESXi host,
which is why it shows up like this. But this is also a good way to see if there is an
existing partition tables on other disks what you feel Virtual SAN should in fact
claim for itself.
vdq - IsCapacityFlash
There are some notable enhancements to this command in Virtual SAN 6.0. It now
includes information about checksum support, and if this device is an SSD, is it being
used for flash capacity rather than caching.
~ # vdq -qH
DiskResults:
DiskResult[14]:
Name: naa.50015178f36363ca
VSANUUID: 52c97eb4-125e-7b56-d358-7cf3e6c8c6a1
State: In-use for VSAN
ChecksumSupport: 0
Reason: None
IsSSD?: 1
IsCapacityFlash?: 1
IsPDL?: 0
Here, the second device is an SSD/flash device, but it is being used as a capacity
device in an all-flash configuration.
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 1 3 9