Best posts made by aaoyagi

@braindead In Fog Configuration -> Fog Settings -> TFTP Settings -> FOG_TFTP_PXE_KERNEL_DIR

Just got this working for me. In case anybody wants the steps:

First in your /etc/exports add this line:
/var/www/fog/iso/15.04_64 *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)

Then restart your nfs server. If you’re running Ubuntu it’s sudo service nfs-kernel-server restart

Next, extract the Ubuntu iso to a direcotry named 15.04_64 in your /var/www/fog/iso directory.

In your Advanced menu use this:
:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item ubuntu15.04_64 Boot Ubuntu 15.04
item return return to previous menu
:ubuntu15.04_64
set path /fog/iso/15.04_64
set nfs_path /var/www/fog/ISO/15.04_64
kernel http://${fog-ip}${path}/casper/vmlinuz.efi || read void
initrd http://${fog-ip}${path}/casper/initrd.lz || read void
imgargs vmlinuz.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:${nfs_path} ip=dhcp splash quiet – || read void
boot || read void
goto start

Hopefully it works for you too. You don’t have to set the variables. I just did it that way in case I ever have to change where the iso directory lives.

@sacha_marin Sweet! Glad you got it working. I couldn’t figure out what was going on with mine and then I realized…case sensitivity. #facepalm

@Hunter-Bonner You may have already tried this, but I didn’t see it in the string of replies so I thought I would chime in. Have you tried using the undionly.kkpxe as your ipxe boot instead of the standard undionly.kpxe? Some of the machines in a lab I manage, Lenovo E31 workstations, have become problematic and using the undionly.kkpxe as the boot file is the only way I can get them to work 100% of the time. Most often they wouldn’t get ip addresses from DHCP, which is not your problem, but testing with the kkpxe couldn’t hurt.

@jguest I had mentioned this in another thread, but you might try passing undionly.kkpxe as the boot file rather than undionly.kpxe. I have a lab of Lenovo Thinkstation E31s that had difficulty getting IPs and using the kkpxe was the only way I’ve been able to correct it.

@Jørgen-Falk-Pedersen What happens when you try an older Kernel like the 4.0.4 Kernel? I’ve noticed that downloading the 4.0.5 Kernel through the web gui often results in downloading a “File not found” html file that’s 154 bytes and not the bzimage or bzimage32 like you would expect. If that’s what’s happening you can manually download the 4.0.5 Kernels bzimage and bzimage32 from http://sourceforge.net/projects/freeghost/files/KernelList and copy them to /var/www/fog/service/ipxe/ Then make sure to reset the permissions on each to give fog read and write and www-data read-only. Like this

@sacha_marin
This is what mine looks like now and I’ve been able to boot the Offline NT Password Reset okay.

:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item cd140201 Boot Offline NT Password Reset
item shell ipxe shell
item return return to previous menu
choose --default cd140201 --timeout 5000 target && goto ${target}
:cd140201
sanboot http://${fog-ip}/fog/ISO/cd140201.iso ||
goto MENU
:shell
shell ||
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU
autoboot

Not sure what else you want to boot, but @Wayne-Workman is right about it being dependent in my experience. For instance, I tried using boot-repair-disk to fix a GRUB issue that I had and it didn’t work properly, I suspect because I’m using sanboot to load the iso. I was going to Windows 8.1 and Ubuntu 15.04 once I get my imaging working properly.

@sacha_marin Should be easy enough to test then. If you haven’t already tried:

1. Create a directory in /var/www/fog where your isos will be kept. If you want to avoid having to redo this every time you upgrade fog it would probably be worth defining another available site in Apache to host your iso files, but for the sake of easiness we can use the fog site since it’s already defined in Apache.
2. Drop the Hiren’s.BootCD.15.2.iso into the iso Directory
3. Assuming you put it in a directory called iso in your /var/www/fog/ folder you’d use something like this:
   :MENU
   menu
   item --gap – ---------------- iPXE boot menu ----------------
   item Hiren’s Load Hiren’s BootCD
   item shell ipxe shell
   item return return to previous menu
   choose --default cd140201 --timeout 5000 target && goto ${target}
   :Hiren’s
   sanboot http://${fog-ip}/fog/iso/Hiren’s.BootCD.15.2.iso ||
   goto MENU
   :shell
   shell ||
   :return
   chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
   prompt
   goto MENU
   autoboot

Case sensitivity counts here so check that cause I messed it up a couple of times trying to get it working. Also, the reason I like to keep the ipxe shell there is so if my iso boot fails, I can just boot the ipxe shell and test the sanboot http://whatever/path/to/iso/here.iso command and see if it boots that way so I know how to fix my menu. Good luck!

@sacha_marin @Wayne-Workman is right about those being variables. Let me download a copy of Hiren’s and see if I can get it working. There was another thread where a guy was trying to integrate Hiren’s too and he used this as the entry to boot Hiren’s. You might try it. In his case he renamed the iso to hirensboot.iso I’ll give it a shot too as soon as I get a chance.

initrd http://${fog-ip}/fog/iso/hirensboot.iso ||
chain memdisk iso raw ||
boot ||
goto MENU

For reference here’s the thread:
https://forums.fogproject.org/topic/4264/integrating-hirens-boot-15-2-into-fog-1-2-0

His final menu is on page 2