- 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
- “The ramdisk “vsantraces” is full” error reports in vSAN logging
- Replacing SSD disk on a vSAN cluster
- vSAN CLOMD daemon may fail when trying to repair objects with 0 byte components
- Diskgroups fail to mount due to heap exhaustion
- On vSAN 6.6 and 6.6.1 cluster, Testing health check fails randomly
- VMware vSAN 6.2 on disk upgrade fails due to CBT enabled virtual disks
- 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
- vSAN performance diagnostics reports: “vSAN is experiencing congestion in one or more disk group(s)”
- Certification of Dell PERC H730 and FD332-PERC Controllers with vSAN 6.x
- Virtual Machine with more than 64GB memory fails to Storage vMotion to vSAN cluster
- Initializing vSAN during boot takes a longer time
- Deployment guidelines for running VMware vSAN and VMware vSphere VMFS datastores on a Dell H730 controller with the lsi_mr3 driver
- Cannot view or add vSAN Storage Providers in the vSphere Web Client
- “Virtual SAN objects available for provisioning” task fails
- “Host cannot communicate with all other nodes in vSAN enabled cluster” error
- “Virtual SAN Disk Balance” warning alarm during vSAN health check
| Tweet |
