1. Component metadata health check fails with invalid state error
  2. Cannot view or add vSAN Storage Providers in the vSphere Web Client
  3. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  4. A virtual machine on a vSAN datastore might be renamed when vSAN becomes inaccessible
  5. Dying Disk Handling (DDH) in vSAN 6.6
  6. VMware vSAN upgrade best practices
  7. Powering on virtual machines in VMware vSAN 5.5 fails with error: Failed to create swap file
  8. vSAN PCIE/NVMe SSDs Receive Warning for HCL Health Check
  9. VMware vSAN Network Health Check for MTU check fails in a Stretched Cluster
  10. Initializing vSAN during boot takes a longer time
  11. vSAN hosts may encounter a purple screen during object cleanup operations
  12. Shutting down and powering on a vSAN 6.x Cluster when vCenter Server is running on top of vSAN
  13. Potential ESXi host failures when hot unplugging SSD disks backed by LSI controllers
  14. Cannot export/download .vmem files from a vSAN datastore for memory dump analysis
  15. “Cannot complete file operation” error during vSAN VM creation
  16. Using small magnetic disks for vSAN might result in VM failures
  17. “out of resources” error when entering maintenance mode onvSAN hosts with large vSAN objects
  18. VM provisioning operations may take a longer time to complete when using Intel SSD DC P3xxx NVMe as caching tier on vSAN 6.6 and vSAN 6.2 (vSphere 6.0 Update 3)
  19. VMware vSAN witness appliance may be using evaluation license key instead of embedded key
  20. vSAN Health Service – Cluster Health – Advanced vSAN configuration in sync