Can't boot to Hirens ISO from IPXE Menu
-
Hey everyone, I’m pretty new to this so let me know if you need anymore information. I’m trying to boot Hirens from the IPXE menu for trouble shooting purposes, but I’m getting the following error.
For reference: Running FOG 1.5.9 on Debian 10
I followed a tutorial that had me make the follow changes to the IPXE menu in the UI as well as the exports fold in /etc/exports/
Thanks,
Max
-
@mstephens Yeah you ran into several issues.
- Your iso is larger than 2GB
- You can boot the iso directly, but you can through memdisk
- This memdisk approach only works for bios based computers.
I have a tutorial here that explains how to set it up for a uefi based computer: https://forums.fogproject.org/post/140212
I don’t use it other than seeing if I could get it to pxe boot. For bios based computers you can use the memdisk approach.
-
@george1421 thank you! I’ll let you know how it goes tomorrow!
-
@george1421 Ran into the following error.
Updated Kernel and setup directories/menu item as stated in tutorial.
-
@mstephens is secure boot enabled? The error is saying it can’t start running winboot or it doesn’t know its format.
-
@mstephens I also find its interesting that it didn’t do any of the imgfetch before it tried to boot wimboot
imgfetch --name BCD ${pe-path}/BCD BCD imgfetch --name boot.sdi ${pe-path}/boot.sdi boot.sdi imgfetch --name bootmgr ${pe-path}/bootmgr bootmgr imgfetch --name boot.wim ${pe-path}/boot.wim boot.wim -
@george1421 Secure boot is disabled. Can you send me an example path for the tftp path and imgfetch so I can make sure the syntax is right?
-
@mstephens said in Can't boot to Hirens ISO from IPXE Menu:
example path for the tftp path and imgfetch so I can make sure the syntax is right?
I’m not sure I understand. The real physical path for the tftp root is
/tftpbooton the fog server.From the tutorial the wim files needs to be in
/tftpboot/os/Hiren101remember with linux case is important.
This is where you copied the files to:cp /mnt/loop/bootmgr /tftpboot/os/Hiren101 cp /mnt/loop/boot/BCD /tftpboot/os/Hiren101 cp /mnt/loop/boot/boot.sdi /tftpboot/os/Hiren101 cp /mnt/loop/sources/boot.wim /tftpboot/os/Hiren101Now the wimboot goes in one directory above in
oscp ./wimboot-2.6.0-signed/wimboot /tftpboot/osThen in the parameters I set to variables to these locations.
set tftp-path tftp://${fog-ip}/os set pe-path ${tftp-path}/Hiren101Which takes the FOG supplied variable
${fog-ip}which is set to the FOG server’s IP address. -
@george1421 still not booting. Double checked IP and capitalization. Also still nothing on imgfetch, not sure why
-
@mstephens
ls -la /tftpboot/os -
This post is deleted! -
-
@mstephens Show me the parameters you have setup in the iPXE menu.
-
bcd is lowercase because that’s how it presents in the dir
BOOTMGR is uppercase because that’s how it presents in the dir -
@mstephens I’m hoping the pictures are mixed up on the orders. This is should be what the parameters look like
set tftp-path tftp://${fog-ip}/os set pe-path ${tftp-path}/Hiren101 kernel ${tftp-path}/wimboot gui imgfetch --name BCD ${pe-path}/BCD BCD imgfetch --name boot.sdi ${pe-path}/boot.sdi boot.sdi imgfetch --name bootmgr ${pe-path}/bootmgr bootmgr imgfetch --name boot.wim ${pe-path}/boot.wim boot.wim boot || goto MENUThat boot after loading the wimboot is what is causing the start before imgfetch is executed.
-
@george1421
They are out of order, here is a copy
-
@mstephens Hmm I can’t explain why its not loading wimboot because its in the right spot and missing out on the imgfetch commands. I guess the masked IP address is the address of your FOG server?
From a windows computer, if you install the tftpclient feature and drop the firewall for testing, can you use tftp to get wimboot from the FOG server?
-
Can’t seem to get the file from windows. The machine is on the same subnet so nothing passes the firewall. Error ‘connect request failed’
-
It is the FOG server IP
-
@mstephens said in Can't boot to Hirens ISO from IPXE Menu:
Can’t seem to get the file from windows.
From the fog server can it get the file from itself?
On the windows computer, if you did not drop the firewall or grant the tftp program access that is probably the problem. tftp is much like ftp in that there are two communication channels setup. “Command” from the windows to FOG and “Data” from FOG to windows computer.
