Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Wimboot - Could not boot image: Exec format error
2017-08-16, 18:54
Post: #1
Wimboot - Could not boot image: Exec format error
I am trying to network-boot a system via HTTP from a server that has IIS version 10 by following the steps in http://ipxe.org/appnote/uefihttp. I am using the latest ipxe.efi. To avoid infinite loop due to ipxe.efi being downloaded on every DHCP request, I followed the instructions in http://ipxe.org/howto/msdhcp#pxe_chainloading and created a DHCP policy that has the boot.ipxe script mentioned in http://ipxe.org/wimboot as Option 67 (BootFile Name).

My boot.ipxe file contains:
Code:
#!ipxe
kernel wimboot pause
initrd boot/bcd            BCD
initrd boot/boot.sdi        boot.sdi
initrd sources/boot.wim    boot.wim
imgstat
prompt
boot

But boot fails with the following message:
Quote:Filename: http://x.x.x.x:port/win/boot
http://x.x.x.x:port/win/boot... Ok
boot: 920 bytes
Could not boot image: Exec format error (http://ipxe.org/2e008081)

I have made sure that the tips given in http://ipxe.org/err/2e0080 are followed. Still the same error occurs. It seems the boot client is finding the Exec Format Error with the boot.ipxe file itself, and I'm not sure why. Any suggestions would be greatly appreciated.

The entire logs:
Quote:iPXE initializing devices…ok
iPXE 1.0.0+ (70544) – Open Source Network Boot Firmware – http://ipxe.org
Features: DNS HTTP iSCSI TFTP SRO AoE EFI Menu
net0: ab:cd:ef:gh:ij:kl using NII on NII-0000:3d:00.0 (open)
[Link:down, TX:0 TXE:0 RX:0 RXE:0]
[Link status: Unknon (http://ipxe.org/1a086194)]
Waiting for link-up on net0……………. Unknown (http://ipxe.org/1a086194)
net1: ab:cd:ef:gh:ij:kl using NII on NII-0000:3d:00.1 (open)
[Link:down, TX:0 TXE:0 RX:0 RXE:0]
[Link status: Unknon (http://ipxe.org/1a086194)]
Waiting for link-up on net1……………. Unknown (http://ipxe.org/1a086194)
net2: ab:cd:ef:gh:ij:kl using NII on NII-0000:3d:00.2 (open)
[Link:down, TX:0 TXE:0 RX:0 RXE:0]
[Link status: Unknon (http://ipxe.org/1a086194)]
Waiting for link-up on net2……………. Unknown (http://ipxe.org/1a086194)
net3: ab:cd:ef:gh:ij:kl using NII on NII-0000:3d:00.3 (open)
[Link:down, TX:0 TXE:0 RX:0 RXE:0]
[Link status: Unknon (http://ipxe.org/1a086194)]
Configuring (net3 ab:cd:ef:gh:ij:kl)… ok
net3: x.x.x.y/255.255.255.0
Filename: http://x.x.x.x:port/win/boot
http://x.x.x.x:port/win/boot... Ok
boot: 920 bytes
Could not boot image: Exec format error (http://ipxe.org/2e008081)
No more network devices
Find all posts by this user
Quote this message in a reply
2017-08-16, 20:14 (This post was last modified: 2017-08-30 17:23 by NiKiZe.)
Post: #2
RE: Wimboot - Could not boot image: Exec format error
IIS will not serve files without knowing it's extension (having a MIME type associated)

If you follow the steps on that error page, especially "Check that the image you are trying to boot has not been corrupted in any way." by downloading this file in a browser and just checking filesize you can see that the size differs. This is also seen in the output you posted "boot: 920 bytes"

Quick search on the forum for IIS finds this post with link to possible solution: http://forum.ipxe.org/showthread.php?tid...9#pid16249

Use GitHub Discussions
VRAM bin
Visit this user's website Find all posts by this user
Quote this message in a reply
2017-08-30, 16:24 (This post was last modified: 2017-08-30 16:25 by rweisman.)
Post: #3
RE: Wimboot - Could not boot image: Exec format error
IIS can be configured, just don't do it for all of the Websites unless you are only using IIS for iPXE.

I have it working.

See this post for a step by step.
https://www.serverintellect.com/support/...xtensions/
Find all posts by this user
Quote this message in a reply
2017-08-30, 16:32 (This post was last modified: 2017-08-30 16:38 by Logan.)
Post: #4
RE: Wimboot - Could not boot image: Exec format error
Thank you, NiKiZe and rweisman, for your helpful comments.

I was finally able to figure it out. As per the instructions in http://ipxe.org/wimboot, I had created a file named boot.ipxe containing all the kernel and initrd commands. But the .ipxe extension is actually not recognized. It should have been .php. That solved the issue.

Now, instead of showing the wrong size (920 bytes), it shows the correct size (250 bytes), and then successfully runs the script.
Quote:Filename: http://x.x.x.x:port/win/boot.php
http://x.x.x.x:port/win/boot.php... Ok
boot.php: 250 bytes [script]
http://x.x.x.x:port/win/wimboot... ok
http://x.x.x.x:port/win/boot/bcd... ok
http://x.x.x.x:port/win/boot/boot.sdi... ok
http://x.x.x.x:port/win/boot.wim... ok

Thanks again for your help!
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 2 Guest(s)