cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1968
Views
0
Helpful
10
Replies

ESXi 6.0 booting issue on HX240 M5

bezeddin
Level 1
Level 1

Folks,

 

We're deploying HXDP on HX240c All Flash with NVMe

The node comes with no ESXi 6 installed so we need to deploy ESXi first

After ESXi installed we need to change boot order boot to M2 (default is EFI)

when ESXi boot up the will pause at startup.nsh. Need to exit from shell in order to boot normally 

Anyone facing this issue and how to resolve it ?

ESXi version HX-Vmware-ESXi-6.0U3-7967664-Cisco-Custom-6.0.3.1

 

 

 

10 Replies 10

mr.ucs
Level 1
Level 1

Has anyone an idea?

Sounds like the BIOS is not being programmed correctly, likely the boot order.

 

I would attempt to decom/re-ack the server via UCSM in an effort to re-apply the BIOS settings and see if the issue is resolved.

 

 

In ma case It is a c240m5 with on Board m2 and nvme and ssd in Front 

 

we disassociate and associate the bios policy ans It did not work.

We also changed the bios policy and Add uefi Boot paraters to the bootx64.efi

 

when we Exit uefi Shell esx Starts 

Can you post what your boot order looks like? I would like to check the "actual" and "configured" boot order.

 

Also provide the following commands from Shell>

 

map -b

 

devtree

 

bcfg boot dump

 

 

Configured

local lun Order 1 

with uefi Parameters 

KVM CD Drive Order 2

 

uefi and Secure Boot 

 

In the efi Shell when Looking at the Boot Order 

the efi Shell is First 

Second is the local m2ssd with Right path

 

wr changed the Position wir Mv but After a Reboot the Same 

If using M.2 your boot policy should reflect "Embedded Local Disk" with the correct parameters defined.

 

The P-SATA mode in the BIOS policy should reflect SWRAID if using RAID.

 

 

I will test It thanks 

In my case it solve by reorder boot priority 1 to M2 and perform Hypervisor configuration through HX installer

 

We added the policy to one new server with embadded local disk and kvm cd/DVD on second boot

 

We manually added the efi file to boot in the efi shell which comes up.

After that the server will start and it will work.

this work arround is describted in the following article

 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuh13333

 

Is there a possibility that the esx server writs his boot information automaticly in the efi?

 

@mr.ucs which ESXi build number you used ?

Review Cisco Networking products for a $25 gift card