@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
Posts made by AdrianW
-
RE: IPXE errors
-
RE: IPXE errors
@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 -
RE: IPXE errors
@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. -
RE: IPXE errors
@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
-
RE: IPXE errors
@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 -
RE: IPXE errors
@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 -
RE: IPXE errors
@Tom-Elliott it is any machine we connect - I have tried 3 different manufacturers
-
RE: IPXE errors
@Sebastian-Roth I did using the mac of the server and I get the same output
-
RE: IPXE errors
@Tom-Elliott said in IPXE errors:
/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00
Hi Tom I’ve tried that - just gives same output as I posted before
-
RE: IPXE errors
Hi Tom
thanks for the quick reply - output below#!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 -
RE: Kernel 4.19.xx Realtek network support
Hi Sebastian - interestingly when I switch to the 32bit kernel everything woks fine so as far as were concerned the problem is solved
-
IPXE errors
We’ve had Fog server running for about 2 years. Suddenly this morning when trying to ‘Deploy Image’ we enter user\password and it now flags an error
http://10.0.0.1/fog/service/ipxe/boot.php… ok
Unrecognised option "-M"Any suggestions
-
RE: Kernel 4.19.xx Realtek network support
@Sebastian-Roth unfortunately the 1.2 server has been ‘recommissioned’ but surely the ‘readlink’ command will only tell me the driver of the interface on the server. The issue we have is with the devices we are trying to re-image. They all re-image fine apart fom one make of terminal which uses the RTL8167 chipset
-
Kernel 4.19.xx Realtek network support
We have been using FOG 1.2 for a couple of years now without any problems. We recently upgraded to 1.55. and the latest Kernel 4.19.6 64bit. The issue we are having is that some of our terminals will not reimage now. They receive an IP address and load the default menu but then when we select the image to load it fails to bring the network card up. Works fine with kernel 4.18.11
Network cards are Realtek PCIe GBE Family Controller (RTL8167) - has support for these cards been removed permanently ?