Posts made by londonfog

@george1421 said in 20.04 autoinstall:

https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/2?_=1594759012162

I wonder if it will be different though, maybe not initially, but soon. See below:

http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/ points to a legacy version. And if you click it, you go here: http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/legacy-images/ to which it mentions this will no longer be supported in the future and mentions the new version stating: now supports all Server hardware platforms, unattended autoinstall, offline installation, network-gapped install, PXE and HTTP boot, RAID, LVM, LUKS, among other things.

Has anyone gotten a subset of this: https://askubuntu.com/questions/1235723/automated-20-04-server-installation-using-pxe-and-live-server-image working with FOG yet? I’m currently only trying to tackle making it liveboot. I haven’t tested an autoinstall yet, since that is new to me with 20.04, I’m used to preseeds.

I get as far as an initramfs shell telling me “Unable to find a live file system on the network”

my initial parameters:
kernel tftp:///${fog-ip}/os/ubuntu/20.04/casper/vmlinuz
initrd tftp:///${fog-ip}/os/ubuntu/20.04/casper/initrd
imgargs vmlinuz initrd=initrd ip=dhcp root=/dev/nfs boot=casper netboot=nfs nfsroot=/${fog-ip}:/images/os/ubuntu/20.04/ locale=en_US.UTF-8 quiet splash ip=dhcp rw
boot || goto MENU

any help is greatly appreciated!

Edit:
I updated my paramaters to closely match what was listed in the above link and got it to work to boot to a live disk.

kernel tftp://${fog-ip}/os/ubuntu/20.04/casper/vmlinuz
initrd tftp://${fog-ip}/os/ubuntu/20.04/casper/initrd
imgargs vmlinuz initrd=initrd ip=dhcp url=http://${fog-ip}/os/20.04/ubuntu-20.04-live-server-amd64.iso locale=en_US.UTF-8 quiet splash ip=dhcp rw
boot || goto MENU

This ended up being the case. Apparently there was a bug in the version of ipxe.efi and cloning the version in the github repo below resolved the issue. I was so caught up in other things I forgot to actually try this until I was reading over this thread again today.

Thank you for your help!

@george1421 said in UEFI Boot:

@londonfog Hmm, ok that isn’t it then. I thought it was possible that something happened with the 1.5.8 update and ipxe.efi was damaged some how.

In each of the boot loaders (undionly.kpxe and ipxe.efi) there is a script that calls default.ipxe on the FOG server… But thinking about it now, its getting past that point because it calls default.ipxe which chains to bootp.php. That http call is failing for some reason. So default.ipxe has already been loaded by ipxe.efi.

I don’t have an answer why only uefi has this issue. I can say that 1.5.5 is kind of old, but I don’t remember your issue being an issue in 1.5.5. I guess you could try ipxe.efi from 1.5.8 to see if that changes anything. Here is the link to the github site where you can download ipxe.efi https://github.com/FOGProject/fogproject/tree/master/packages/tftp

@george1421 I have tested with two different UEFI systems. Both Dell however.

I have a pcap now, looking through it I see this line [ETHERNET FRAME CHECK SEQUENCE INCORRECT] and it’s corresponding to the boot.php.

@george1421 I added it to my default.ipxe and no such luck. ::shucks::

@george1421 interesting.

when I type `chain http://fogip/fog/service/ipxe/boot.php’ it times out

it does not time out when I run `chain -ar http://fogip/fog/service/ipxe/boot.php’

@george1421 1.5.5

@george1421

default.ipxe
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch ${buildarch}
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
param sysuuid ${uuid}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://<fogIP>/fog/service/ipxe/boot.php##params

bottom of boot.php
param sysuuid ${uuid}
:bootme
chain -ar http://<fogIP>/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

Now I have hit ‘S’ at the time out error to drop to a ipxe shell and have successfully booted to the fog menu by running
chain -ar http://<fogIP>/fog/service/ipxe/boot.php##params

@george1421 so after the connection times out I decided to hit ‘s’ and drop to the iPXE prompt. And then I manually called the chain command I saw listed near the bottom of my boot.php file which is:
:bootme
chain -ar http://xxx.xx.xx.x/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

I manually typed out the chain line and it boots to my fog menu page… So i’m glad I can atleast make the connection, i’m just stumped why it’s not automatically doing it?

@george1421 I happened to look at /opt/fog/.fogsettings and noticed that bootfilename= is ‘undionly.kpxe’ should this be changed to include ipxe.efi?

@Sebastian-Roth I’m sure there is no typo considering legacy boot still works fine. But when I get into the office I’ll do a dump to see if anything stands out.

@george1421 correct, if I use legacy it boots fine, switch to UEFI, I get the error in original post. I’m quite baffled, which is what lead me to bring this here. I’ll be back in the office tomorrow and can dig more, any suggestions I’ll gladly take! Thanks for all your replies so far!

@george1421 also, I think I mentioned in the original post, but BIOS pxe is still working. If the IP were not correct in default.ipxe would bios pxe also not boot?

@george1421 we’re using infoblox for DHCP. I worked with the network engineer for creating the policies. I’ll verify that he’s pointing the UEFI filter to the correct file in tftboot.

And yes I can go to that url. So does it seem more like a networking thing at the moment?

Hi There,

trying to set up uefi boot, we have it setup correctly on the dhcp side with correct options. When selecting uefi boot I get an address, it finds the server and the following happens:
tftp://fogip/default.ipxe… ok
http://fogip/fog/service/ipxe/boot.php...........Connection Timed out (http://ipxe.org/4c0a6092)
Could not boot: connection timed out (http://ipxe.org/4c0a6092)
Chainloading failed, hit ‘s’ for the iPXE shell; reboot in 10 seconds

Legacy boot still works fine. Are there parameters I need to change in boot.php or maybe in default.ipxe?

Thanks in advance!

@george1421 said in Adding normal wipe to PXE boot menu:

kernel bzImage loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=270000 web=${fog-ip}/fog/ consoleblank=0 rootfstype=ext4 capone=1 mode=wipe wipemode=fast mac=00:00:00:00:00:00
imgfetch init.xz
boot || goto MENU

Would it be possible to add a wild card to see any disk in the host computer and wipe them all?

Scenario is I have a destination machine with 2 NVMe drives, It currently already has a linux install on one of the drives. Sometimes Fog seems to erase the existing in use drive and deploy the image to that drive, and other times it picks drive 2 and images there, thus creating an issue when we boot/reboot that sometimes the wrong drive is picked for booting and its not the right image.

What is the best method for wiping all drives including partition tables/mbr on the destination machine prior to a deploy?

Thanks!