|VMware ESX Server cannot see existing VMFS3 Volume|
I had a problem in one of my DRS/HA Clusters where one ESX 3.0.2 host was unable to see an existing VMFS volume although the volume was in use by other ESX hosts in the cluster, and we confirmed that the SAN LUN zoning was done correctly.
I did have the option in the VI client to add more storage, and then select the LUN, but that would reformat the LUN and I would loose all my existing VM's on that volume.
The fix to this issue was to reset the LUN with "Resignaturing"...
To reset the LUn so it can be presented to the ESX host:
Ensure that no ESX hosts are using or locking the LUN.
In the VI Client, select the ESX host and select the configuration tab
On the remaining ESX hosts:
Select the ESX host
- Simple VMware vSphere 4 & 5 License Calculator
- Clearing a GUID Partition Table (GPT) in Linux
- Building an iSCSI Openfiler SAN on a USB Stick
- Replace SSL Certificates: Replace vCenter Server SSL Certificates
- Replacing vSphere SSL Certificates
- My experiences with Installing vCenter on Windows Server 2008 R2
- Patching ESX 3.5 Using esxupdate
- Veeam FastSCP on Windows Server 2003 x64
- Restarting vmware-hostd
- A Deeper Look Into VMware vSphere 5 Licensing