A local SSD becomes unavailable for virtual flash resource or Virtual SAN configuration when it is formatted with VMFS or any other file system.
When you attempt to configure either Virtual SAN or virtual flash resource, a local SSD disk does not appear on the list of disks to be used.
This problem might occur when a local SSD intended for use with either feature has been already formatted with VMFS. Neither Virtual SAN nor virtual flash can share the SSD disk with VMFS or any other file system.
Also, because virtual flash and Virtual SAN are mutually exclusive consumers of SSD disks, both features cannot share the same SSD disk. If the SSD is already claimed by one feature, for example Virtual SAN, you are not be able to use it for another, such as virtual flash, unless you release the disk.
- Avoid formatting the SSD with VMFS during ESXi installation or Auto Deploy. See Preventing SSD Formatting During Auto-Partitioning.
- If the SSD is already formatted with VMFS, remove the VMFS datastore. For information see the vSphere Storage documentation.
- To use the SSD as a virtual flash resource, do not claim this disk for Virtual SAN. If the disk is claimed by Virtual SAN, remove the disk from Virtual SAN. The SSD is released from Virtual SAN and becomes available on the list of disks to use with virtual flash. For information about removing disks from Virtual SAN, see the vSphere Storage documentation.
- If you intend to use the SSD with Virtual SAN, do not use the disk for a virtual flash resource. If SSD is used as the virtual flash resource, remove the virtual flash configuration. The disk becomes available for Virtual SAN. See the vSphere Storage documentation.
An SSD might be unavailable because ESXi cannot recognize it. See Local SSDs Are Undetectable.