UEFI B200M4 and Windows 2012R2

[sdingman68]

Has anyone had success booting a B200M4 with UEFI and Windows 2012R2?  We are able to install the OS without issue but once the install has completed and the server reboots we get a BSOD stating that the ntoskrnl.exe is missing or corrupt.  I mounted the volume to another server and verified that ntoskrnl.exe was where is should be and was not corrupt.  Informantion on UEFI is scarce and with UCS blade servers even more scarce.  The server is boot from SAN, FC. UEFI sees the 120 GB drive during the boot process.  

TIA

Scott

[Walter Dey]

Hi Scott

Did you configure UEFI

Cisco UCS Manager GUI Configuration Guide, Release 2.2 - Configuring Server Boot [Cisco UCS Manager] - Cisco

UEFI Boot Parameters

UEFI boot mode for servers is dependent on information that is stored on the platform hardware. The boot entry, which contains information about the UEFI OS boot loader, is stored in the BIOS flash of the server. In Cisco UCS Manager releases earlier than Release 2.2(4), when a service profile is migrated from one server to another server, the boot loader information is not available on the destination server. Hence, the BIOS cannot load the boot loader information for the server to boot in UEFI boot mode.

Cisco UCSM Release 2.2(4) introduces UEFI boot parameters to provide the BIOS with information about the location of the UEFI OS boot loader on the destination server from where the BIOS loads it. Now, the server can use the boot loader information and boot in UEFI boot mode.

• Guidelines and Limitations for UEFI Boot Parameters
• Setting UEFI Boot Parameters
• Modifying UEFI Boot Parameters

[sdingman68]

I must be using the wrong boot loader path and efi file then.

Here is what I currently have.

Boot Loader Name = Windows Boot Mgr

Boot Loader Path = \EFI\Microsoft\Boot\bootmgfw.efi

When troubleshooting a different UEFI issue, Cisco support said that these were not needed.  Documentation says mandatory.

[Kranthi Kumar Katkam]

Scott,

Following path should be working:
EFI\Boot\BOOTX64.EFI

Prior to 2.2(4) release, you have to manually point to this from the EFI cli prompt.

[sdingman68]

Added that as the path and restarted server, still getting ntoskrnl.exe is missing or corrupt error.  We are on version 2.2(7).

[Kranthi Kumar Katkam]

Scott,

I would suggest to go through HCL and recommend to run the drivers as per the compatibility guide.

If you are already running the recommended drivers, then check the system event logs and collect memory dump from the OS. https://blogs.technet.microsoft.com/askcore/2012/09/12/windows-8-and-windows-server-2012-automatic-memory-dump/

-Kranthi

[sdingman68]

Here is a screen shot of my current boot policy.  

[joshua.emily]

Old and dated and I am sure you have figured it out by now... However, your boot path should not contain the boot file. For example it should be like this:
Bootname = bootx64.efi
Bootpath = \EFI\BOOT