VMware ESX/ESXi 3.5 Update 3 released
November 7th, 2008 | 
Author: | I’ve already mentioned the new ESX 3.5 Update 3 release in my post about the VMDK Recovery Tool, but here’s a copy of the official email announcement I received from VMware tonight. | ||||||
|
|
Jeez, I was just getting used to Update 2!
Posted in 
Tags: 
Don’t know if this has been brought up before.. but I learned this weekend that Virtual Center must always have higher or equal update version running as any ESX host in the environment. Or else the next time you go to restart the virtual center service it will crash. So I guess my point is before you update ESX to U3 makes sure VC is up to date as well.
Since this page has been for me the window to vm world with the nicest view, I thought of contributing my experience with this update.
Although 2 out of my 5 ESXi servers updated smoothly through the VI Update program, the other 3 refused to get my datastores up and running after the update. Apparently something went wrong with the signing of my volumes … 3 times over!
So here is a tip if you come across this one… Go to VI and select the server you got problems with and try the following:
DO NOT use the “add storage” option!!! This will reformat your datastores and you will loose all your VMs!!
Set both Entries Configuration -> Advanced Settings -> LVM -> DisallowSnapshotLUN and Configuration -> Advanced Settings -> LVM -> EnableResignature to 0.
Rescan in the storage tab and you should have your datastores back.
If you decide to Resign your stores set EnableResignature = 1.
!!NOTICE!! You will have to import all your VMs to the console again.
ipman and nettraptor,
Thanks for the contributing tips and for reading vm /etc!
Just to comment on #1, the installation procedure specifies to update the database and VC client before updating any hosts. RTM people.