@Tom-Elliott

1. Does registration fail every time, or did it fail once?

• With a disk attached registration works fine.
• With no disk attached it fails every time

2. In the BIOS, what is the SATA mode: AHCI, RAID, or ATA/IDE?

• SATA mode is AHCI

3. Please run a debug task on that host: Hosts > (the host) > Basic Tasks > Advanced > Debug. At the shell, run lsblk, then dmesg | grep -iE ‘ata|sd’. Post a photo of both.

• So I don’t have an image for legacy boot. I only brought home a drive with the UEFI image.
• I can either change the BIOS to UEFI and do a one time boot or I can install Ubuntu 26.04.1 on a different disk as Legacy boot.
• Which would you prefer; I am trying to minimize variables on the theory of only change one thing at a time…

For sake of documentation here is the info @Tom-Elliott asked for:

1. The make and model of the target machine, and its BIOS version.

• Dell Model: XPS 8400 BIOS: A14

2. A photo of the whole screen, from the first line. We need the line that starts with “iPXE” and shows its version.
   
3. Is any other DHCP server active on that network, such as your router? If yes, what boot file (option 67) does it give out?

• No the server and hosts are connected to a 5 port unmanaged Gigabit switch with DHCP handled by FOG server.

• Server IPv4 interface is hard coded with address 192.168.3.1 255.255.255.0 (in Settings/Network/Wired Connection 1 IPv4) tab gateway 192.168.3.1

• Other home network is 192.168.2.0 /24 and is only used, via wifi, on periodic basis to download updates.

3. Does the target boot to the FOG menu in Legacy/CSM mode, with UEFI off?

• Yes it boots in successfully but errors out as in reply above.
• Manually adding host on the FOG server, the host boots fine and I successfully captured an image.

@Tom-Elliott

Switching to Legacy worked but I went from white screen to black screen for non registered hosts very quickly.

How do I keep the white screen around longer?

Registration fails but I can’t attach video. Photo below:

Peter

Hi;

Objective: Build a “standalone” FOG server environment i.e. one machine as the FOG server and three others as hosts of FOG tasks such as full wipes/capture/deploy I am trying to get the while screen so I can do a registration of a “target” machine. However I am getting the following error(s) instead which I cannot get past.

**iPXE initialising devices…•

autoexec.ipxe… Not found (https://ipxe.org/2d12618e)
/autoexec. ipxe… Not found (https://ipxe.org/2d12618e)
ASSERT c:tedk2\udk2010.sr1.x2\MdeModulePkg\Library\UefiHiilib\Hiilib.c(257): Hii
Handle != ((void ж) 0)

ASSERT_EFI_ERROR (Status = Not Found)
ASSERT c:ledk2\udk2010.sr1.x2\MdeModulePkg\Library\Uef1H11L1b\H11Lib.c(259): IEF
I_ERROR (Status)
ASSERT c:sedk2\udk2010.sr1.x2\MdePkg\Library \BaseL ib\LinkedList.c(60): List 1= ( .(void ) o)*

Reproduction Steps:

Build FOG Server

• Perform a clean Ubuntu Desktop 26.04.1 installation (then reboot machine)
• Open UBUNTU App Centre and perform an Update All to ensure all applications are up to date (reboot machine)
• Run Firmware Updater to bring firmware up to date (reboot machine)
• Open terminal:
  execute sudo apt update && sudo apt upgrade -y
  execute sudo apt autoremove -y

Reboot machine

2)Install FOG
Based on current installation instructions for FOG 1.5:
Install git
clone fog project from github
run the ./installfog.sh bash script

3. Try to register “target” machine
   Check BIOS for
   latest version
   UEFI boot enabled
   PXE boot enabled
   Set boot order so IPv4 and IPv6 are first in boot order

Restart machine and hope for white screen to Register a Host. Get above error. Please note I have tried more flavours of the reproduction steps than Baskin Robbins has ice cream flavours e.g. with/without SecureBoot, DHCP, DNS, router even Ubuntu 24.04.5 and Ubuntu 26.04.1 all with the same errors on my host machine. I even broke down and did an RTFM of fog docs, wiki, and forums.

Fog install log files:
fog_error_1.5.10.2518.log
foginstall.log

The instructions for FOG Server installation include the following:

Database setup

While most of the installation runs without intervention, there is one step you need to do manually. The installer will prepare the database for you and then ask you to open your web browser and visit the FOG web UI to build the initial database schema or promote an existing database with new schema updates. Make sure you follow this step and only proceed with the installer (hit ENTER) after the schema update/setup has finished, or the installer will fail.

In build 1.5.10.2518 this has become a question in the interactive install. If you try from the web UI a user will receive a Denied message.

The instructions need an update.

@george1421 post can be marked as solved.

Do I do that or is this done by a Moderator?

@george1421 thanks George! I guess I am going to have to get a more powerful target. Maybe 12th gen rather than 3rd Gen?
Not 13th or 14th gen as they have stability issues.

Hi All;

Forgive me if this question is redundant.

I volunteer with a not for profit and we receive donated desktops and laptops. For all machines we do a Full wipe of each drive and then deploy a standard image.

We have a small isolated FOG environment with one FOG server (1.5.9) and a couple of desktops plugged into a switch. Everything is working fine except with the growth in SATA drive size e.g. 2TB the Full wipe can take hours; if not days.

How can I make the Full Wipe faster?

• list item Would a faster switch and faster NICs in the machines help?

• list item Would using SATA3 motherboards on the server and targets help?

Any suggestions would be appreciated.