esxconsole.vmdk is detecting as snapshot - how to avoid this?

[jithinraj]

Hello All,

We are trying to migrate ESX4.1 boot LUNs from one storage box to another. We moved the LUN but ESX fails to boot and this is due to esxconsole.vmdk is detecting as snapshot.  We followed the KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101214.... This KB helped us to fix the issue. But is any one know how to migrate ESX boot LUNs  without hitting this issue? We are using NetApp Storage.

Please help

Regards

Jithin

[jithinraj]

All, any luck on this?

[Sreec]

Hi,

    The KB which you are referring is correct.Since the issue got resolved after following the KB.Boot from SAN should work as long as we are following all best practices and HCL is fine.I have few questions

1.Was there any change in your environment? Any firmware update? Storage/HBA/Switch changes etc.

2.Is it ISCSI/FCOE/FC-Boot lun?

3.Do we have other host doing a SAN-BOOT where in luns are from same storage array?

Note:This article assumes that the disk, LUN, and storage controller are functioning properly.If you are having issues with local storage such as boot LUN presentation issues or a failed storage RAID, these issues must be identified before implementing the resolution provided in this article

If everything is supported(HCL-http://www.vmware.com/resources/compatibility/search.php?deviceCategory=san) and if there are no changes happened(Very Rare chance) and you should contact Vmware Support for next level of analysis.

Note:There is no preventive measure for this scenario(Because the workaround you did is for resignaturing the lun since it got detected as snapshot LUN),if you dont want to encounter same issue you should not make use of boot from san or do keep an eye on snapshot lun from storage side

[Sreec]

Hi,

    Rather than lun migration,i would recommend a fresh installation of ESX/ESXI on a new lun

[jithinraj]

Thanks Sreec for the reply...answers are below

1.Was there any change in your environment? Any firmware update? Storage/HBA/Switch changes etc.

Yes, New Storage setup. We want move Boot Luns to new storage

2.Is it ISCSI/FCOE/FC-Boot lun?

FC-Boot lUN

3.Do we have other host doing a SAN-BOOT where in luns are from same storage array?

Yes. We moved couple of ESX servers, first one we had hit the issue and second one worked properly.

Is there any way to avoid this? As we want to migrate many ESX servers. Please help

[jithinraj]

Is there any best Practice to move Boot LUns. As you suggested we have to think about fresh installation if nothing works