@quazz You’re right. Must have been a bad spot or something. One thing we all know Windows does is to add a minimum of two partitions on a clean install. Mine had 3 (ms system reserved, empty) partition. Did lots of research, found I don’t need three, just setup GPT with single partition, did base install, and now FOG imaging upload works.

Thanks for pointing me in the right direction.

@Sebastian-Roth Gosh darn it, that worked!!! What ultimately was done was what you suggested. Someone else had suggested the primary disk change, that was removed. But there was also some custominit.xz or something like that listed as well, so I changed that to init.xz. Can’t believe it, but that worked! Now going to try and deploy this same image to exact same hardware on different PC. I’ll let you know how the deploy goes. Sebestian (and team) thanks so much for your hard work and diligence on this. -Jim

@Tom-Elliott
Thanks Tom

However I ran this about 15 times. Post install I was never given an option to update the database or schema.

My initial issue before upgrading was that I was trying to deploy image to Lenovo M625Q tiny with 256gb SSD drive as the PRIMARY drive and the standard Seagate 500gb (SATA0) as the SECONDARY drive. I added the /dev/nvme0n1 as the primary disk, yet FoG wrote to the Seagate drive first every time.

I asked ChatGPT for ideas, and it found a known issue with FoG writing to EUFI SSD drive as Primary drive and stated that I needed to update to the latest iPXE file. Everything been broken ever since. I have spent more than a week trying to get FoG working once again.

I’m updating my Ubuntu server to v20.04 now and I will try the re-install one more time, unless you have any other ideas?

-Jim

[BUG] iPXE Boot Loop and Kernel Missing After Upgrade to FOG 1.5.10.1660 — Clients Fail to Boot to Menu

---

Environment:

• FOG Version: 1.5.10.1660
• Server IP: 192.168.9.10
• Clients: Lenovo M625Q Tiny, UEFI BIOS
• Primary Disk: 256GB SSD
• Secondary Disk: 500GB HDD
• PXE Boot Mode: UEFI
• Install Directory: /root/fogproject/
• Apache DocRoot: /var/www/

---

Issue Summary:

After upgrading to the latest FOG version, my PXE boot environment is broken. What used to work flawlessly is now a disaster. PXE clients either hang, enter a loop, or display autoexec.ipxe not found. Sometimes pressing ESC brings up a green DOS-style login prompt, then fails to chainload. Sometimes they hang on “Booting…” indefinitely.

---

Symptoms:

• iPXE boot screen says:
  • Could not boot: autoexec.ipxe not found
  • Chainloading failed
• Green DOS login prompt appears briefly after pressing ESC
• Clients never reach the expected FOG PXE Menu
• Kernel files (bzImage, bzImage32) and init files are missing
• FOG configuration GUI shows blank or missing sections
• No active task, yet PXE fails to display menu
• boot.php loads in browser but returns:
  Warning: A non-numeric value encountered in bootmenu.class.php on line 290

---

What I’ve Verified:

• Tables hosts, hostMAC, and ipxeMenuItems are populated and correct
• MAC address correctly mapped to host
• PXE config references bzImage32, but the file is missing
• Apache serving from /var/www, not /var/www/html
• Manually created /var/www/autoexec.ipxe, permissions confirmed
• Kernel paths match database and boot.php but files are gone
• curl test against boot.php returns valid iPXE script, but boot fails
• No active tasks found in the tasks table

---

What’s Missing or Broken:

• /var/www/fog/service/ipxe/ is missing bzImage, init.xz, etc.
• GUI options like FOG Configuration → iPXE Menu Configuration are missing
• No visible way to manage PXE boot menu via GUI
• Default behavior not working: No task = no PXE menu shown

---

What I’ve Tried:

• Rebuilt PXE menu records in MySQL
• Manually added menuaccess=1 in boot.php call to test
• Disabled display_errors in PHP FPM, CLI, and Apache configs
• Reinstalled Apache/PHP, confirmed docroot
• Cleared and reloaded /tftpboot
• Re-created /var/www/autoexec.ipxe
• Spent over 14 man-hours debugging this
• Absolutely no unauthorized edits to boot.php

---

This Is Critical:

FOG’s original behavior:

• If task is scheduled → auto-execute
• If no task → show PXE boot menu

That logic is now broken post-upgrade. I do not want custom behavior or rewritten logic. Just default.

---

Ask to Community:

• Is this a known issue in 1.5.10.1660?
• Where can I safely re-download the kernel/init files (like bzImage32, init.xz)?
• How do I regenerate the boot.php environment cleanly without destroying host/task data?
• Can anyone else confirm GUI menus missing in this build?

---

Attachments Available:

• Screenshots of:
• PXE Boot failures
• Green login prompt
• Missing menu entries
• SQL output verifying host mapping

---

Thanks in advance — desperate for resolution.

– Jim

Hello All! (Especially Wilsol)

I used the top configuration ideas from Wilsol, and before I could get through the entire list, darned thing started working. (yeah probably secure boot, thanks Tom for pointing us in the right direction)

Thanks to everyone for the assist.

-Jim

Hi Tom and Rodluz. I use FoG often. Our company uses Lenovo’s predominantly and all works great. For legacy devices I use undionly.kkpxe but mainly for EUFI devices I use ipxe.efi

Tom, I went into Bios and yes, Secure Boot and all of its options are enabled.
Rodluz, yes I do get the >>Start PXE over IPv4. screen and then I get the proper IP addresses and message that NBP file downloaded successfull, then the screen goes blank and then the Start PXE over IPv6 screen pops up, then nothing. Times out.

Thanks for the responses, all. What’s my workaround to get this to work?

-Jim

Anyone??

I have a new Dell Optiplex 7020 and I am trying to get it to connect to my FoG server via PXE and it’s not working. Anyone know of a working FXE file I should be using for this connectivity? I want to save an image that uses EUFI Bios and iPXE is not working

Any suggestions?

-Jim

Oops!
I deleted from CLI. But I just did that again and the image did not appear in the list and the storage number increased accordingly.

-Jim

Hello. I have deleted old images in my images folder. However, the available storage space node never changes. How can I update this to show actual drive space available for images?

Hello team. Running into an issue. I have these new Lenovo all-in-one devices and I have opted to use the available SSD rive addon as my base OS drive, and a secondary 500gb for data. However in fog, while I can select multiple partition image, it will not allow me to make either of the drive resizable. That created big problems for me. Is fog going to come up with some work around for this? Has anyone any thoughts on this?

@sebastian-roth said in Image menu not showing recently created images:

@Jim-Holcomb How many images do you have? I am not aware of a limit of images that can be seen in the menu but I can’t tell you for sure.

So would you be able to delete an older one and see if one of the new one pops up in the menu?

Hello Sebastian - I tried that - deleting older images. No joy. You know that the image menu just keeps going to the next number in order. I am currently at 160, but of course I do not have anywhere near that many images. Then menu goes to 158 then ends. Yet if I go to “List all Images” of course the image resides there with all of it’s available information, size, date, etc…

I am stumped here.