Home > Blogs > Support Insider


Top 20 vSAN Articles June 2018

  1. Component metadata health check fails with invalid state error
  2. Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  3. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  4. Replacing SSD disk on a vSAN cluster
  5. The ramdisk ‘vsantraces’ is full
  6. “The ramdisk “vsantraces” is full” error reports in vSAN logging
  7. On vSAN 6.6 and 6.6.1 cluster, Testing health check fails randomly
  8. VMware vSAN 6.2 on disk upgrade fails due to CBT enabled virtual disks
  9. vSAN CLOMD daemon may fail when trying to repair objects with 0 byte components
  10. Diskgroups fail to mount due to heap exhaustion
  11. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  12. vSAN Unassociated Object Handling – A Methodology
  13. “Virtual SAN Disk Balance” warning alarm during vSAN health check
  14. Certification of Dell PERC H730 and FD332-PERC Controllers with vSAN 6.x
  15. vCenter Server 6.0 Update 2 displays on non-vSAN enabled ESXi hosts displays the message: Retrieve a ticket to register the vSAN VASA Provider
  16. Initializing vSAN during boot takes a longer time
  17. Virtual Machine with more than 64GB memory fails to Storage vMotion to vSAN cluster
  18. Placing host into maintenance mode with ‘Full data migration’ option fails
  19. vSAN performance diagnostics reports: “vSAN is experiencing congestion in one or more disk group(s)”
  20. Cannot view or add vSAN Storage Providers in the vSphere Web Client