IPXE errors
-
@Junkhacker multiple device from multiple manufacturers
-
@AdrianW If you could, please post the contents of the output in text format. Particularly the one from the MAC address.
I’m wondering if you have hostnames using
-in the name? I’m not sure if this could pose a problem, but there’s always the possibility. -
@Tom-Elliott
Hi Tom, most of our hostnames have a - in them as FOG is automatically naming them PC-** when they are first registered if we need to take an image from a new type of terminal. This issue happens when trying to deploy to terminals not registered on FOG. As stated in my original post we have been using it without any issue for 2 years to apply OEM images before dispatch -
@Tom-Elliott from the ip ending 85 earliwer
#!ipxe
set fog-ip 10.0.0.1
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://10.0.0.1/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap – -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.sysinfo Client System Information (Compatibility)
item fog.multijoin Join Multicast Session
choose --default fog.deployimage --timeout 10000 target && goto ${target}
:fog.local
exit || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.0.0.1/fog/ consoleblank=0 rootfstype=ext4 shutdown=1 storage=10.0.0.1:/images/ storageip=10.0.0.1 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.0.0.1/fog/ consoleblank=0 rootfstype=ext4 shutdown=1 storage=10.0.0.1:/images/ storageip=10.0.0.1 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username fog
param password password
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
param sysuuid ${uuid}
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.0.0.1/fog/ consoleblank=0 rootfstype=ext4 shutdown=1 storage=10.0.0.1:/images/ storageip=10.0.0.1 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
param sysuuid ${uuid}
:bootme
chain -ar http://10.0.0.1/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot -
@AdrianW There isn’t a -M option in the ipxe menu you posted.
To add a little clarity
- What were you doing when it threw this -M error? Just booting into the ipxe menu to register or where you trying to image?
- Do you get the same results when just booting into register or only when imaging?
- Can you get A computer to fail with the -M error message and then run Tom’s query again but with the mac address of the computer that threw the error like this
http://10.0.0.1/fog/service/ipxe/boot.php?mac=00:00:00:00:00where00:00:00:00:00== the mac address of the computer that generate the error.
I have seen sometimes users naming the image name with something like “Win10 -May2020” Might confuse the iPXE boot loader.
-
@george1421 Thanks George -
After selecting deploy Image and entering username and password is when error occurs
can register devices no problemwill try last one first thing monday as I am being kicked out of the office - it’s weekend
-
@george1421 thank you George - just read the last bit of your post.
We use ‘-’ all the time in our image names but having thought about it - the last thing I did was create a custom image which started with ‘M-’, looks like I may have made a massive typo and put ‘-M’ instead. Will log on remotely over the weekend and check. If that is the case how easy is it to change the image name ? I assume that apart from the image folder name there are also references in the DB. -
@AdrianW changing the image definition and the directory structure in the /images directory should do it. Just note the “-M” it self should not cause the issue but a “<space>-M” would or any “<space>-<character>” would be interpreted by iPXE as a command line switch.
But your right the last thing you did, should be the first place you look.
-
@george1421 Thanks once again for your help, and the others who took the time to offer their help.
I’ll let you know how I get on on Monday -
@george1421 Morning George
the issue is resolved - it was the ‘-M’. There was no <space> at the beginning so iPXE clearly doesn’t like ‘-’ at the beginning. Thanks again
