Chainloading failed / boot looping
-
I checked the VM was set to E1000 and EFI booting. When I enter the URL I get the following:
#!ipxe
set fog-ip 192.168.1.53
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
iseq ${platform} efi && set key 0x1b || set key 0x1b
iseq ${platform} efi && set keyName ESC || set keyName Escape
prompt --key ${key} --timeout 3000 Booting… (Press ${keyName} to access the menu) && goto menuAccess || chain -ar ${boot-url}/service/ipxe/grub.exe --config-file=“rootnoverify (hd0);chainloader +1”
:menuAccess
login
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param username ${username}
param password ${password}
param menuaccess 1
param debug 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar http://192.168.1.53/fog/service/ipxe/boot.php##paramsThank you all for helping out. Sorry I couldn’t get back to reply earlier than this!
-
Another thought I had was that we also use MDT for creating images that can be put on a boot flash. I have no problem with booting the 7010 UEFI using the MDT boot files. I was able to deploy a .wim file yesterday with no issues. I’m inexperienced with the process and the files but I’m wondering if there isn’t a boot file that we can pull from the MDT process and add it to the FOG repository?
-
@gwhitfield It’s missing kernel parameters.
-
@Wayne-Workman said:
@gwhitfield It’s missing kernel parameters.
Sorry to appear dense, but I don’t know what the output SHOULD look like, nor what to do to get it that way. I’m handicapped by a lack of in-depth knowledge on how it works. I apologize if I have missed a how-to I suppose?
-
@gwhitfield Heres what mine looks like.
Keep in mind, this iPXE script is generated dynamically based on the parameters passed to it (the mac addresses of the computer). I didn’t pass any parameters to the page, which is why the script says
item --gap Host is NOT registered!What version of FOG are you using now? Did you upgrade to trunk as suggested?
#!ipxe set fog-ip 10.2.1.11 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.2.1.11/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.quickimage Quick Image item fog.multijoin Join Multicast Session item fog.sysinfo Client System Information (Compatibility) choose --default fog.local --timeout 5000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :fog.memtest kernel memdisk iso raw initrd memtest.bin boot || goto MENU :fog.reginput kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.2.1.11/fog/ conosoleblank=0 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=127000 keymap= web=10.2.1.11/fog/ conosoleblank=0 loglevel=4 mode=autoreg imgfetch init_32.xz boot || goto MENU :fog.quickimage login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :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 :fog.sysinfo kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.2.1.11/fog/ conosoleblank=0 loglevel=4 mode=sysinfo imgfetch init_32.xz boot || goto MENU :bootme chain -ar http://10.2.1.11/fog/service/ipxe/boot.php##params || goto MENU autoboot -
What version of FOG are you using now? Did you upgrade to trunk as suggested?
Ubuntu 14.04.4, FOG 1.2.0, rev 6365. I didn’t update yet but plan to as soon as I can today. I neglected to mention that I did have a positive UEFI boot and was able to upload from and re-deploy a test image to a Dell E5550 a few days ago using snponly.efi so I thought maybe I’ve just changed something accidentally since then that would be simple to identify.
-
@gwhitfield Have you watched all the movies in the “Tremors” franchise?
-
The root if the issue here is (the Dell 7010). The 7010 will not completely boot the iPXE kernel. This is needed for FOG to function correctly. Its not an issue with FOG, but a compatibility issue between a component that FOG uses (iPXE) and the Dell 7010 EFI firmware. When you MDT boot you can use either cdrom or usb flash drive. This process doesn’t use iPXE so I would expect this to work. I can also boot the 7010 into the FOG Live debugger using a usb (similar to the way MDT boots). But again this doesn’t use iPXE to boot.
What needs to happen.
- Dell fixes their silly firmware
- The iPXE guys can work out a method to patch iPXE to work around this issue.
- You switch back to BIOS booting for this hardware platform.
-
@Wayne-Workman -only saw the first one, enjoyed it immensely for no good reason.
-
@gwhitfield said:
I neglected to mention that I did have a positive UEFI boot and was able to upload from and re-deploy a test image to a Dell E5550 a few days ago using snponly.efi
-
When you MDT boot you can use either cdrom or usb flash drive. This process doesn’t use iPXE so I would expect this to work.
I’m fairly certain I PXE booted the 7010 UEFI using WDS to deploy the MDT image. Only reason I’m uncertain at all is simply how many different imaging related projects I have going on… I will be able to test/confirm later today or tomorrow.
-
@gwhitfield said:
I’m fairly certain I PXE booted the 7010 UEFI using WDS to deploy the MDT image.
WDS doesn’t use iPXE.
-
@Wayne-Workman - Ahhh…they appeared similar enough in the netboot phase that I got the impression it was the same technology. I been duped.
-
@Wayne-Workman said:
Oh sht that’s funny!!!
#1- I gotta see that movie again. It feels like 20 years since…
#2 - I apologize. I know just enough to be dangerous and under the circumstances sometimes it’s hard to know what’s relevant to the discussion much less what’s important. -
@gwhitfield There are 5 of them now. They are all worth watching, in order, with the wife/gf.
-
@Wayne-Workman said:
@gwhitfield It’s missing kernel parameters.
I upgraded to trunk and no change. I was hoping the kernel parameters issue would be resolved automagically since I never intentionally made any changes to anything except putting different efi boot file names in DHCP. I looked and can tell there’s tons of info on kernel parameters and editing the boot menu but isn’t there a default setup that should be in place with a re-install? Do I need to edit something now?
-
@gwhitfield What boot file are you using at the moment? What mode (uefi/bios) is the target computer in right now? Is this a Optiplex 7010 or … something else?
We need to know all your testing details.
-
@Wayne-Workman - I’ll give up on the 7010, they’re just an experiment anyway. I’m currently testing on the ESXi 5.5 VM set to UEFI and E1000 nic, also testing with a Dell E5550 set to UEFI boot first from IPV4 nic and then Boot Manager. They both appear to be doing the same thing when being served the same boot file.
Scope options in DHCP are:
66 - IP of FOG server
67 - whatever file name I’m testing out.Boot file ipxe.efi - they ask “Please enter tftp server:”
Boot file snponly.efi - they ask “Please enter tftp server:”
Boot file snp.efi - they ask “Please enter tftp server:”
Boot file intel.efi - they ask “Please enter tftp server:”
Boot file realtek.efi - They say “DHCP failed, hit ‘s’ for shell, reboot in 10 seconds”
Boot file undionly.kpxe - E5550 flashes quickly and boots to OS, VM looks like below (I don’t have an UEFI disk in the system, just wanted to see the network boot okay.)
-
@gwhitfield If I’m not mistaken, the “Please enter tftp server” has to do with either another DHCP server conflicting or some IP helper thingy.
-
@gwhitfield As you said. Let’s try to focus on one issue! We won’t get the Dell 7010 to netboot with iPXE in UEFI mode any time soon I reckon. As George said he is able to netboot ESXi 5.5 VMs with iPXE on e1000 NIC setting just fine. So it can be done. Please stick to snponly.efi as George reported this works for him.
From your first picture we see that getting an IP via DHCP (and the next-server information) within iPXE has worked. What changed? I kind of doubt that upgrading to the latest FOG version broke this. But we’ll work this out. What happens if you enter the TFTP (FOG server) IP? Does it get you to the menu or fails as well?
I am still wondering about the output you got from accessing boot.php in your browser. Have you possibly changed your iPXE menu to be hidden? Check the settings in the web interface: FOG Configuration -> iPXE Boot Menu -> “Hide Menu” is checked???
@Quazz The message means that although iPXE was able to get an IP via DHCP it did not receive next-server (option 67) from the DHCP. Sounds kind of weird because we know that on the first try (PXE ROM getting IP and boot information) it got the information as it would not have been able to load the iPXE binary otherwise. Would be great to see a packet dump of a client/VM booting to that message. Wireshark on the DHCP server (display filter:
bootp || tftp) would be great!
