@krishna Using a random screenshot and not explain it costed you two days by pointing to the wrong direction. The clearer your information is the more we are able to help you.

OK, so this is a normal single master FOG node setup and we can rule out routing because FOG server and PXE booting clients are all in the same subnet?

So you have the firewall disabled in the FOG server?

Where clients ever able to PXE boot to the menu? If yes, when did it work last and what changed since then?

About the access.log - I just figured that Ubuntu moved to a different name at some point. Please run tail -f /var/log/apache2/*.log while you PXE boot one client to see if it shows up in the log.

@sebastian-roth try this https://drive.google.com/file/d/1I_LFCwT0INMzg8vHbbi60KSqvYHtNDKN/view?usp=sharing

@aloniada Interesting. I have not tried it myself as I don’t use live OS booting. Just trying to help with what I find on the web. I would imagine the parameter can go pretty much anywhere in the imgargs line.

When you moved it to different positions, did you always get the exact same error message. I can’t think of why iPXE would grab that out of the imgargs line…

@adamhyla89 said in 11th Gen Intel Kernel:

it states cannot open ` /var/www/fog/service/bzImage’ (no such file or directory)

Better copy & paste the commands to not miss anything. So again: file /var/www/html/fog/service/ipxe/bzImage* /var/www/fog/service/ipxe/bzImage*

The install on the VM is only command line, no GUI for Ubuntu.

There is no GUI (for Ubuntu) needed as you can access the FOG web UI from another computer. I guess you have used it already because how would you manage FOG or even get past the schema update when you don’t access the FOG web UI.

@rodluz you can try this, https://forums.fogproject.org/topic/6463/expose-fog-host-and-image-properties-to-post-install-scripts?_=1620751811503 and make a review of host, image and hostinventory items…

@sebastian-roth unfortunately I do not get shell after pressing enter. This is what I get instead

@sebastian-roth we may have found a workaround since we have a uefi/bios co-existence setup, we are trying to legacy boot to capture/deploy the uefi image. It appears to have worked. I am not sure I want to pursue this issue further since it is a very old model and a one off case.

I appreciate your help on the matter regardless, thank you.

@sebastian-roth yes, right… and just FYI, I got it working once I followed the instructions on the link you’ve sent me, thanks man!

@ngriffith29 With FOG you usually register hosts (at least you need to if you want FOG to rename them) and there you define the hostname it will use after deployment. So it’s just up to you to name the hosts accordingly.

@vtl.victor I am not saying it’s impossible to do. It just needs work and we don’t seem to find the time to work on this. Your quickest way to achieve what you want is capture/deploy an image at your FOG network site. Don’t let the deployed host boot into the OS (add kernel parameter shutdown=1 to that host). Then boot that same host up with Clonezilla (for example) and for taking a backup that can be deployed at an offline site on USB - no FOG server needed there - just the Clonezilla boot media and image on portable drive. (cross references: 1, 2, 3)

If that’s not what you want you need to dive into the details. Just quoting Junkhacker’s postfrom another topic here:

FOG image capture and deploy are multi-step processes. each are several commands that rely on scripts and programs in the FOG OS (FOS) and change based on what options you have selected. FOG images are not designed to be used stand alone. Using FOG images without a FOG server will require steps that were expected to be automated and there really isn’t a quick way around it.

So if you or anyone else is keen, you want to start looking at the commands to do this here:

Clear old partition table: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2012 Apply new partition table: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2041 Loop to do the restore: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2376 Finally call partclone deploy the image files one by one: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L760 Restore UUID information: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/partition-funcs.sh#L25 Possibly more things I have missed…

And that’s just the simple case without resizing partitions!

It’s all open source, it’s all yours!

@greg-plamondon I’m looking at the iso image and I think we should be able to pxe boot it.

In the tftp root directory create a dir to hold your files.

mkdir -p /tftpboot/os/port

Copy from the iso image /boot/vmlinuz and /boot/initrd.xz to /tftpboot/os/port on the fog server.

Then you will want to create a new FOG iPXE menu similar to this

Menu Item: os.Porteus.Kiosk
Description: Porteus Kiosk 5.2.0
Parameters:
kernel tftp://${fog-ip}/os/port/vmlinuz
initrd tftp://${fog-ip}/os/port/initrd.xz
imgargs vmlinuz initrd=initrd.xz quiet first_run
boot || goto MENU
Menu Show with: All Hosts

Lets see what that does for you. We may have to tweak the image args because I see a parameter of http_server= in the syslinux config but its not in the grub config.

@fernando-gietz thanks

@john3892 Assuming you installed FOG via git, please run:

cd /path/to/fogproject #change this to where it is actually located git checkout dev-branch git pull cd bin ./installfog.sh -y

This issue should be addressed.

Thank you,

@ice4192 Like this?
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@SomeWeirdRandomDude Please post the full fog.log from that client here.

By the way, which version of FOG and the fog-client do you use?

@dashwell Which version of FOG do you use?

Although it boots into the menu on other devices I would still check for a spanning tree issue first. Connect a dumb mini switch (8 port unmanaged, even no-name product) between your new laptop and the official switch/cord it was connected to. See if it can get an address and boot to the menu this way.

If that does not help then you might switch to a different iPXE binary. The default for UEFI mode machines is ipxe.efi. Change you DHCP PXE options to use snponly.efi and give it a try with your new laptop.

Then again, if it does not work, you might look into compiling iPXE from the latest source code. We’ll explain how to do this when all other methods don’t help.

@colej Which version of FOG do you use?