After VMware ESX 3.5 Upgrade from SP1 to Sp3 Some SAN LUNs Disappear
Posted on 2009-04-01
What is/was the resolution process?
Rescan vmhbas with below results:
[root@fmsuesxdev02 root]# esxcfg-rescan vmhba2
On scsi2, removing: 0:20 0:21 0:100 0:101 0:102 0:103 1:0 1:1.
On scsi2, adding: 0:20 0:21 0:100 0:101 0:102 0:103 1:0 1:1.
[root@fmsuesxdev02 root]# esxcfg-rescan vmhba3
On scsi3, removing:.
On scsi3, adding:.
Recheck vmfs volumes (still not present)
[root@fmsuesxdev02 root]# cd /vmfs/volumes
[root@fmsuesxdev02 volumes]# ls
Remove blade WWPNs from McData Zones and rescan to remove from ESX
Re-add blade WWPNs to McData Zones and rescan. No change.
In VI Client Main Console LUNs are seen in Configuration > Storage Adapters
But Not in Configuration > Storage
Log on to individual blade in VI Client and have Same results as in Main Console.
When I select Add Storage & the LUNs are seen but re-adding in this manner would reformat and delete all existing data.
Several times prior to the upgrade the blades have "lost" the LUNs and this was able to be rectified by "rescanning" the vmhbas.