iPXE discussion forum

I have other hardware booting with the exact same setup. We are using MDT and chaining directly to MDTs litetouchpe image. Specifically on these HP DL380 gen10 servers we get an error:

BlInitializeLibrary failed 0xc0000001

Whats interesting is that the output between this server and a working server are nearly the same minus the memory addresses. I tried injecting HPs drivers into the PE image and that did not work, tried different BCD files that also did not work, also tried using copype and using the files it created and that did not work. Out of ideas at this point and that error is pretty not helpful :/

Thanks!

[Image: Uv9zjkd.png]

EDIT:

Using latest wimboot and latest ipxe

EDIT 2:
BCD looks like this:

Code:

PS D:\DeploymentShare\Boot\x64\Boot> bcdedit /store BCD /enum all

Windows Boot Manager

--------------------

identifier              {bootmgr}

description             Windows Boot Manager

locale                  en-US

inherit                 {globalsettings}

default                 {default}

displayorder            {default}

toolsdisplayorder       {memdiag}

timeout                 30

Windows Boot Loader

-------------------

identifier              {default}

device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}

path                    \windows\system32\boot\winload.exe

description             Windows Setup

locale                  en-US

inherit                 {bootloadersettings}

osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}

systemroot              \windows

custom:250000c2         1

detecthal               Yes

winpe                   Yes

ems                     No

Windows Memory Tester

---------------------

identifier              {memdiag}

device                  boot

path                    \boot\memtest.exe

description             Windows Memory Diagnostic

locale                  en-US

inherit                 {globalsettings}

EMS Settings

------------

identifier              {emssettings}

bootems                 No

Debugger Settings

-----------------

identifier              {dbgsettings}

debugtype               Serial

debugport               1

baudrate                115200

Global Settings

---------------

identifier              {globalsettings}

inherit                 {dbgsettings}

                        {emssettings}

Boot Loader Settings

--------------------

identifier              {bootloadersettings}

inherit                 {globalsettings}

                        {hypervisorsettings}

Hypervisor Settings

-------------------

identifier              {hypervisorsettings}

description             Hypervisor Settings

hypervisordebugtype     Serial

hypervisordebugport     1

hypervisorbaudrate      115200

Device options

--------------

identifier              {7619dcc8-fafe-11d9-b411-000476eba25f}

ramdisksdidevice        boot

ramdisksdipath          \boot\boot.sdi

PS D:\DeploymentShare\Boot\x64\Boot>

ipxe script:

Code:

#!ipxe

kernel http://<url>/DeploymentShare/Boot/x64/Boot/wimboot

initrd http://<url>/DeploymentShare/Boot/x64/Boot/BCD BCD

initrd http://<url>/DeploymentShare/Boot/x64/Boot/boot.sdi boot.sdi

initrd -n boot.wim http://<url>/DeploymentShare/Boot/LiteTouchPE_x64.wim boot.wim

imgstat

boot

A quick google on that error yields: https://support.microsoft.com/en-us/help...rt-an-oper

Try to upgrade firmware on the machine, if that dosn't help you should contact HP about this issue.
compiling ipxe with memmap debug enabled might help you see what is going on, but not sure what can be done to have that solved, other than fixing firmware.

HP Gen9 and Gen10 share the same firmware bugs. They are fixed in the latest releases.

(2019-06-01 16:07)MultimediaMan Wrote: [ -> ]HP Gen9 and Gen10 share the same firmware bugs. They are fixed in the latest releases.

Would you happen to know what version fixes it specifically? Smile

Flashed latest from HP: U32 v2.04 (04/18/2019)

Still fails Sad

, getting this fixed from HP will be a giant PITA.

HP are actually quite good at dealing with these issues, have you contacted them?
I can guarantee you that it is harder for them to fix the issue, if they don't get your report. Wink

building iPXE with DEBUG=memmap, might give you some idea of what is going on, and playing around with order of loading the files might help.
Also try to double check BIOS settings, maybe do a factory reset and try again and see if that changes anything.

(2019-06-03 22:18)NiKiZe Wrote: [ -> ]HP are actually quite good at dealing with these issues, have you contacted them?
I can guarantee you that it is harder for them to fix the issue, if they don't get your report.

building iPXE with DEBUG=memmap, might give you some idea of what is going on, and playing around with order of loading the files might help.
Also try to double check BIOS settings, maybe do a factory reset and try again and see if that changes anything.

Its not that they wont be helpful its just going to be a giant pain.

So I have been working with HP at this point and they are looking for those memmap dumps from iPXE. I tried compiling iPXE like this:

Code:

make bin-x86_64-efi/ipxe.efi EMBED=boot.ipxe DEBUG=memmap

That did not seem to change anything in the console output. Any ideas? Thanks again.

From your earlier post it seem you go through a lot of steps before booting iPXE. These all fragment the memory.
You should try cutting out some steps, like grub. A braver option would be to burn iPXE directly on the card.

dzeleski

NiKiZe

MultimediaMan

dzeleski

dzeleski

NiKiZe

dzeleski

mhabets