ESXi 6.0 getting stuck up at vmw_vaa ip_hds loaded successfully

[Narayanarao]

Hi Guys,

We are using Cisco B200 M4, we installed ESXi 6.0 U2 using Custom ISO provided by Vmware for Cisco blade.

Issue: ESXi is getting stuckup at boot screen with this message vmw_vaa ip_hds loaded successfully

hint: This issue is observed after provisioning storage to ESXi servers. I am observing this issue on two nodes.

any clue/advices appreciated. 

Thanks

[Evan Mickel]

This particular module is responsible for Storage Array API integration so it would be sensible that it may be effected by provisioning of storage to a host.

Do you have a large number of RDM LUNs provisioned to the host in question?  How many LUNs (RDM or otherwise) are presented to the host in total?  What make/model is the array?

This question would likely be better answered in the support forums for VMware but if you can get those answers back to me we can make some progress towards better understanding the situation.

Thanks!

[Narayanarao]

Hi 

Thanks for response

We have approximately 25 RDM Luns. All are small size luns mapped to single VM.

About Array. Hitachi VSP G400

[Evan Mickel]

This definitely seems to be a limitation of the configuration and storage provisioning that has been put in place.  VMware knows that this is an issue and has generated the following knowledge base article that I would encourage you to read.  I have placed a link below.

https://kb.vmware.com/s/article/1016106

It appears that the specific behavior seen in that KB was fixed in a previous version but this serves as a reasonable jumping-off point that would at least get you closer to an answer.  It looks like you can mark those LUNs as reserved to speed up your boot time.  In multiple instances I saw posts within VMware's forums regarding hosts/VMs with 20+ RDM LUNs with 60 minute boot times.

I hope this helps!