Here is our Top 20 vSAN articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.
- Certification of Dell PERC H730 and FD332-PERC Controllers with VSAN 6.x
- Best practices for Virtual SAN implementations using Dell PERC H730 or FD332-PERC storage controllers
- VMware Virtual SAN 6.0 Requirements
- Following maintenance, hosts in a Virtual SAN cluster may erroneously report the error: Host cannot communicate with all other nodes in virtual SAN enabled cluster
- Avoiding a known drive failure issue when Dell PERC H730 controller is used with VMware Virtual SAN 5.5 or 6.0
- Required VSAN and ESXi configuration for controllers based on the LSI 3108 chipset
- vSphere 5.5 Virtual SAN requirements
- VMware Virtual SAN 6.2 on disk upgrade fails at 10%
- Powering on virtual machines in VMware Virtual SAN 5.5 fails with error: Failed to create swap file
- VMware Virtual SAN 6.1 or 5.5 Update 3 Disk Groups show as Unmounted in the vSphere Web Client (DDH)
- Upgrading from ESXi 5.5 to ESXi 6.x in a Virtual SAN cluster can cause permanent loss of data
- VMware Virtual SAN 6.2 on disk upgrade fails due to CBT enabled virtual disks
- Requirements and considerations for the deployment of VMware Virtual SAN (VSAN)
- Creating new objects on a VMware Virtual SAN Datastore fails and reports the error: Failed to create directory VCENTER (Cannot Create File)
- Support statement for 512e and 4K Native drives for VMware vSphere and VSAN
- ESXi 5.5 host in a VMware Virtual SAN cluster reports a warning alarm: Host vendor provider registration
- Virtual SAN Health Service – Cluster Health – VSAN Health service installation
- Upgrading from VMware vSphere 5.5 EP06 or 5.5 P04 to vSphere 6.0 GA can cause VMware Virtual SAN Data Unavailability
- Upgrading the VMware Virtual SAN (VSAN) on-disk format version from 1 to 2
- Virtual SAN Health Service – Performance Service – Stats DB object check
