Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
wimboot Exec Format error (2e008081) uEFI
2017-08-04, 18:46
Post: #1
wimboot Exec Format error (2e008081) uEFI
Forgive me if this was already addressed, but my searching did not find the answer. (Yes I spend considerable time reading search results) I am trying to boot Winpe over http.

I have created a directory on my Webserver, extracted the winpe.iso file.
Extracted the latest wimboot to that directory
Create a script file in that directory
#!ipxe
kernel wimboot
initrd -n Boot/BCD BCD
initrd -n Boot/boot.sdi boot.sdi
initrd -n sources/boot.wim boot.wim
boot

For trouble shooting I have used make bin-x86_64-efi/ipxe.efi EMBED=embed.ipxe

The contents of ipxe.efi
#!ipxe
dhcp
shell

My PXE EFI grub command to boot this
chainloader /ipxe.efi

All good booting the ipxe.efi to a shell.

When I try to boot / chain.. to the boot.ipxe (Saved as utf8) file on the webserver
ie:
boot http://xx.xx.xx.xx/www/aape/boot.ipxe
I get an ok, then:
I get the error "Could not Select: Exec format error (http://ipxe.org/2E008081)

I just started this project, so all the stuff is the latest release.

Maybe this is something stupid, but I am stuck at this point.

Thanks for any help.
Find all posts by this user
Quote this message in a reply
2017-08-04, 20:17
Post: #2
RE: wimboot Exec Format error (2e008081) uEFI
try imgfetch http://xx.xx.xx.xx/www/aape/boot.ipxe

followed by imgstat

it should show [SCRIPT]

If not make sure the script is saved without any BOM chars the magic #!ipxe must be the first 5 bytes of the file

Read the FAQ before posting.
Did you include relevant ipxe.org error urls?
Visit this user's website Find all posts by this user
Quote this message in a reply
2017-08-04, 20:54
Post: #3
RE: wimboot Exec Format error (2e008081) uEFI
(2017-08-04 20:17)NiKiZe Wrote:  try imgfetch http://xx.xx.xx.xx/www/aape/boot.ipxe

followed by imgstat

it should show [SCRIPT]

If not make sure the script is saved without any BOM chars the magic #!ipxe must be the first 5 bytes of the file

I don't get the [Script] from imgstat. Here is a cut and paste. Looking at it with Notepad++ show all characters, only LF's are in the file. I created the file in linux using vi.
imgstat shows SIVAC\ :4453 byes "ENGINEERING\ WEBSITE/aape/boot.ipxe.

Unfortunately the person who setup the Webserver used White spaces so I am refering to it using \ escape characters.
http://10.xx.xx.xx/SIVAC\ ENGINEERING\ WEBSITE/aape/boot.ipxe
don't know if that could be an issue.. as I am using Linux notation.

File is attached.
#!ipxe
kernel wimboot
initrd -n Boot/BCD BCD
initrd -n Boot/boot.sdi boot.sdi
initrd -n sources/boot.wim boot.wim
boot
Find all posts by this user
Quote this message in a reply
2017-08-04, 22:24
Post: #4
RE: wimboot Exec Format error (2e008081) uEFI
(2017-08-04 20:54)rweisman Wrote:  imgstat shows SIVAC\ :4453 byes "ENGINEERING\ WEBSITE/aape/boot.ipxe.

Unfortunately the person who setup the Webserver used White spaces so I am refering to it using \ escape characters.
http://10.xx.xx.xx/SIVAC\ ENGINEERING\ WEBSITE/aape/boot.ipxe

As you can see it downloads a file called "SIVAC\" with size 4453 ande with "ENGINEERING\ WEBSITE/aape/boot.ipxe. as "argument"

Space in urls are converted to %20

Check your http server logs, that the correct file was fetch and check the filesize ... normally the server should respond with 404 in a case like this, and then iPXE would give you an error on the fetch instead.

Read the FAQ before posting.
Did you include relevant ipxe.org error urls?
Visit this user's website Find all posts by this user
Quote this message in a reply
2017-08-07, 20:49
Post: #5
RE: wimboot Exec Format error (2e008081) uEFI
Thanks for the help.. It led me down the path to my issue. My IIS server would not allow serving files without an extension.
I found a link to fix that, and now I can get my Winpe Wim to boot.
Here it is for others: https://stackoverflow.com/questions/1995...-extension
Find all posts by this user
Quote this message in a reply
Post Reply 




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