- Component metadata health check fails with invalid state error
- Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
- vSAN Build Recommendation Engine Health fails
- Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
- How to manually remove and recreate a vSAN disk group using esxcli
- vSAN CLOMD daemon may fail when trying to repair objects with 0 byte components
- Replacing SSD disk on a vSAN cluster
- 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
- Virtual Machine with more than 64GB memory fails to Storage vMotion to vSAN cluster
- vSAN performance diagnostics reports: “vSAN is experiencing congestion in one or more disk group(s)”
- On vSAN 6.6 and 6.6.1 cluster, Testing health check fails randomly
- Diskgroups fail to mount due to heap exhaustion
- Cannot view or add vSAN Storage Providers in the vSphere Web Client
- “The ramdisk “vsantraces” is full” error reports in vSAN logging
- Initializing vSAN during boot takes a longer time
- “Unexpected status code: 503” error in vSAN health check plug-in
- “Virtual SAN objects available for provisioning” task fails
- vSAN host may encounter a purple diagnostic screen during performance statistics updates
- “Host cannot communicate with all other nodes in vSAN enabled cluster” error
- “Virtual SAN Disk Balance” warning alarm during vSAN health check
Related Articles
