Can't boot to Hirens ISO from IPXE Menu
-
@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.
-
So i got it to load through. just moved wimboot to the root and back and it worked on restart. . . But now it just loads the imgfetch then flashes the following screen, and proceeds to windows.
-
-
@mstephens so that’s different from what I understood. This is working as it should.
Does the boot.wim file get transferred? Or does it stop?
-
It finishes, then returns to booting windows (virtual drive has windows on it)
-
@mstephens Well I set this up in the test bench and I get the same results. Its possible that everything loaded in memory is larger than 2GB and that is causing things to abort.
Its not a timing issue because I switched loading boot.wim over to http instead of tftp and the load happens in about 8 seconds now.
It appears the booting of wimboot is crashing which returns us back to the iPXE menu then onto refind.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
