VMware has just released a long awaited (at least by me 🙂 version of vSphere - 6.0 Update 2. This version introduced officially VMware Host Client and solved an annoying bug regarding to failover VMs affected by Permanent Device Loss (PDF).
The VM is left in an invalid state with a warning message stating that Hardware Version 1 is not recognized whenever there is a PDL of any of the storage hosting VM.
Update: still a PDL problem. 🙁
After creating a snapshot of my VCSA, I patched my vCenter using VAMI in my lab. It worked pretty well and needed not so much time (~30min). I didn't face any problem such as stuck at 70% that I faced during patching to U1b.
However, when I checked the ESXi 6.0 Update 2 Release Notes, I found this problem there and following workaround:
The issue occurs due to introduction of a new Virtual SAN VIB which is interdependent with the esx-base VIB and the esxcli software vib update command only updates the VIBs already installed on the system.
Workaround: To resolve this issue, run the "esxcli software profile update" as shown in the following example:
esxcli software profile update -d /vmfs/volumes/nagasaki_local/update-from-esxi6.0-6.0_update02.zip -p ESXi-6.0.0-20160302001-standard
VMware VSAN 6.2 is released as part of vSphere 6.0 U2. This version introduced many cool features such as deduplication, compression or RAID 5 and RAID 6 erasure coding.
To download vCenter and ESXi 6.0 U2 please click below links: