cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
5627
Views
5
Helpful
5
Replies

ESXi 7U3 Boot Failure (Secure Boot with TPM Enabled)-No Mapping Found

IC2317
Level 1
Level 1

Hi All,

 

I am facing issue getting ESXi boot after fresh installation. My environment is boot from SAN (Pure Storage). Strange part is that I have other UCS blades that are booting fine. Only difference is, hosts that are booting fine were installed before enabling secure boot and TPM. I just had to enable secure boot and TPM in polices and there were no issues in booting these hosts.

However, when I am doing new fresh installation of ESXi 7 U3 on hosts (Previously 6.7 was installed) and trying to boot from SAN then it fails.

Installation succeeds by mounting Customized Cisco Image but after reboot it does not boot. Below is the error:

 

ESXbootfailure.png

1 Accepted Solution

Accepted Solutions

Hi Steven,

 

I figured out the problem why this was occurring. In UCS boot policy, SAN boot was configured with vHBA0 and vHBA1 but on storage switches zoning is configured with vHBA2,vHBA3 so after installation when host was rebooting it could not find boot LUN. Earlier, SAN boot was configured from EMC VNX for Boot Luns(Using vHBA0 & vHBA1) and now I am migrating that to Pure storage, so this issue was related to misconfiguration at UCS & Storage Switch. As soon as vHBA2/HBA3 was added in the boot target, ESXi booted successfully.

 

Many thanks for your help so far, much appreciated.

View solution in original post

5 Replies 5

Wes Austin
Cisco Employee
Cisco Employee

Are you using UEFI boot mode? Seems like the installer is not writing a UEFI boot variable to BIOS.

Yes, I am using UEFI Boot Mode and have also configured with below settings:

 

uefi.png

Does the UEFI boot option "UEFI SAN" show up in the list if you press [F6]?

Can you manually add a new entry to the BIOS setup via [F8]? (I think [F8] is the key.)

Does the server boot from the manually created entry?

I have seen where incorrect UEFI options were entered into UCSM which overwrote/broke the OS written options (read: it may be better to remove the UCSM config and let the OS add the boot option).

 

Beyond that I'd start reviewing OS docs like:

  https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-D1BD27AB-C432-454D-9B2B-DC04E7BA9979.html

Hi Steven

 

No, UEFI SAN option does not show up in Boot Menu. Also, I don't see option to add Boot Entry option also in this blade.

 

I checked on other host(ESXi Installed before enabling TPM & Secure Boot) that has same profile(Because created from same service template), it shows "VMware ESXi" in the Boot option and also have option to manual entry. I am not able to understand that why same blade with same firmware version has different options in BIOS than the one on which I am installing fresh ESXi after enabling secure boot.

Hi Steven,

 

I figured out the problem why this was occurring. In UCS boot policy, SAN boot was configured with vHBA0 and vHBA1 but on storage switches zoning is configured with vHBA2,vHBA3 so after installation when host was rebooting it could not find boot LUN. Earlier, SAN boot was configured from EMC VNX for Boot Luns(Using vHBA0 & vHBA1) and now I am migrating that to Pure storage, so this issue was related to misconfiguration at UCS & Storage Switch. As soon as vHBA2/HBA3 was added in the boot target, ESXi booted successfully.

 

Many thanks for your help so far, much appreciated.

Review Cisco Networking for a $25 gift card

Review Cisco Networking for a $25 gift card