Ipxe Error: Exec format error
-
Hello!
Long time FOG veteran and just newly upgraded to the newest version 1.0.1.
My FOG setup consists of three connections:
10.10.240.10 that enables me to contact the web server from my computer.
192.168.2.1 Is the bread and butter interface that holds the DHCP server (192.168.2.5) that was builtin with fog
172.16.2.1 Is the separate connection I have that’s attached to a NAS drive for storing images (this works just fine)The laptop I’m using to test with does manage to grab an IP address from the DHCP server, but once it goes to a couple of other steps, I’m given the iPXE error “Exec format error” and I haven’t a clue what that means.
Any ideas anyone?
-
Anyone at all?
-
This is stating that the command that is trying to perform is not recognized. To better help us understand, troubleshooting and finding the common cause would be preferable.
You can also try other undionly.kpxe and ipxe.kpxe files that Tom is working on to resolve some of the other issues.
Note the features in your current undionly file, when you pxe boot a client you should see something similar
[code]
iPXE 1.0.0+ – Open Source Network Boot Firmware – http://ipxe.org
Features: HTTP iSCSI DNS TFTP AoE VLAN bzImage COMBOOT ELF MBOOT PXE PXEXT[/code]Please let me know what features are available and then compare it to the undionly.kpxe files that Tom is currently working with. We need to find the missing piece or the command that is making it fail.
Undi files can be found here: [url]https://mastacontrola.com/ipxe[/url]
-
[quote=“Jaymes Driver, post: 28639, member: 3582”]This is stating that the command that is trying to perform is not recognized. To better help us understand, troubleshooting and finding the common cause would be preferable.
You can also try other undionly.kpxe and ipxe.kpxe files that Tom is working on to resolve some of the other issues.
Note the features in your current undionly file, when you pxe boot a client you should see something similar
[code]
iPXE 1.0.0+ – Open Source Network Boot Firmware – http://ipxe.org
Features: HTTP iSCSI DNS TFTP AoE VLAN bzImage COMBOOT ELF MBOOT PXE PXEXT[/code]Please let me know what features are available and then compare it to the undionly.kpxe files that Tom is currently working with. We need to find the missing piece or the command that is making it fail.
Undi files can be found here: [url]https://mastacontrola.com/ipxe[/url][/quote]
Thanks very much for the reply! And forgive me, I’m a complete PxE noob. How can I “try” the other undionly.kpxe and ipxe.kpxe? Is this done through the fog interface?
-
No, you would do it on the linux installation. What flavor of linux did you use to install FOG on? I will get you some commands to help you on your journey.
-
[quote=“Jaymes Driver, post: 28658, member: 3582”]No, you would do it on the linux installation. What flavor of linux did you use to install FOG on? I will get you some commands to help you on your journey.[/quote]
I’m currently using Ubuntu 10.04 -
[quote=“variable205, post: 28663, member: 359”]I’m currently using Ubuntu 10.04[/quote]
Good solid operating system!
First I want you to pxe boot a machine and tell me what the features are listed.
After you log that information and paste it here, I want you to open up a terminal and issue the following commands:
[code]
cd /tftpboot
sudo mv undionly.kpxe undionly.kpxe.old
sudo wget -O /tftpboot/undionly.kpxe --no-check-certificate https://mastacontrola.com/ipxe/71ed-GOOD/ipxe.kpxe[/code]If you use dnsmasq you will want to restart the service and then try to pxe boot the client.
Also note, that in my environment, I use the file from here sudo wget -O /tftpboot/undionly.kpxe --no-check-certificate [url]https://mastacontrola.com/ipxe/f3d24-QUOTA_20-GOOD/undionly.kkpxe[/url]
Tom has made a number of ipxe files available, you just need to pick and test which work in your environment.
-
Sorry for the late reply, got crazy busy on Friday. Anyway, I think it may be a problem when I try to pxe boot the machine, that’s when the error comes up and not much more information is provided :(.