Moderators

@eliphas said in Fog storage node selection by latency instead of load:

I am using FOG as a base-image-deployer library for VMs, seldom registering a machine on FOG

Ok so you are using fog in a system builder mode. Where you just pxe boot and then select deploy image from the FOG iPXE menu (i.e. load and go). In this case the location plugin will not help you.

Are the master node and storage node at the same location or different geographic locations? If they are different locations and you are using the load and go method, you may be better served by installing a full fog server at each location, then on the HQ location add the two remote FOG servers as storage nodes. This way the images will replicate from the master HQ fog server to the remote FOG servers. The only thing you will need to do is export the image definition from the master node and then import it into the remote fog servers.

@zaccx32 When you delete images from the imaging management page you MUST go into the image definition and delete them from there (in the image definition). If you delete them only from the image list then only the database entry is removed from the database and the raw image files are not touched. This is by design to keep people from accidentally removing the image record and raw files. If you have deleted the image definitions while in the list view you will need to manually go into the FOG server linux console and change to the /images directory and then remove the old image directories with this very powerful command sudo rm -rf /images/<image_name> The -rf command switch is very powerful in that it will remove things without asking if you make the file path carelessly.

Another place to look is in the /images/dev directory. If there are any directories in there what look like mac addresses those can be removed as long as you don’t currently have a capture task underway. These files left over from the capture are botched image captures that can be delete.

@eliphas Install the location plugin into the master node. Then associate the storage node with a location and then when you register the target computer define a location for them. Then your clients will reach out to the defined storage node. Without the location plugin the target computes will pick at random all storage nodes in the master nodes storage group. There is no real intelligence when selecting storage nodes in the storage group.

@krishna said in PXE Windows Client registration:

10.20.0.9 has no relation to my environment.

Well this information has to be coming from somewhere.

For the subnet where your clients are running, look at your dhcp server. Confirm what is at dhcp option 66 on your dhcp server. If its set correctly then we will need you to get a pcap of the booting process. To that point is the fog server and the target computers on the same IP subnet?

@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.

@fry_p said in Dell Vostro 470 - UEFI net boot fails:

I am wondering what else I could try if this is a fixable issue.

1. Attempt to image the computer in bios mode. As long as you boot it in uefi mode for the OS, it is acceptable to image the machine in bios mode. Just use the F12 boot manager to one time pxe boot in bios mode.
2. Bypass iPXE by booting FOS Linux from a usb flash drive.

@sebastian-roth thanks for the advice. I tried ipxe.efi and also tried compiling my own. Unfortunately both times I received the same error. I am wondering what else I could try if this is a fixable issue.

Hi all,
FOG 1.5.9, boot file snponly.efi, kernel 5.10.34 TomElliott.

Get a strange error when trying to UEFI netboot an old Dell Vostro 470. It has the latest released firmware (A14 from 2018) and throws an error about edk2 (see below). It will not progress past this. I am wondering if this is due to the age of the pc model.

Let me know if you need any more details as I’m sure I left out an important detail or two by accident.

Thanks!