Posts made by aaoyagi

@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

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

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

@the_duke What @Wayne-Workman said. Tried it after reading this when I started having trouble with my machines and it works 100% of the time. https://wiki.fogproject.org/wiki/index.php/Talk:Building_undionly.kpxe#kkpxe

Okay changed the partitions on the master to Primary Partitions instead of Logical Partitions and everything seems to be working fine now. I guess logical drives don’t really work well. In any case I’ll mark this solved because the issue has veered wildly from the initial question, which Tom answered for me. Thanks all.

@the_duke Which boot file are you passing via PXE? undionly.kpxe? Can you try undionly.kkpxe instead? I’ve had better luck using it since I have some machines with firmware quirks.

@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

Still having trouble getting a good image. I’ve updated to r3591 and tried to upload an image using the settings from my first post and I get what appears to be a good image:

-rwxrwxrwx 1 root root 0 Jun 23 09:26 d1.has_grub
-rwxrwxrwx 1 root root 1.0M Jun 23 09:26 d1.mbr
-rwxrwxrwx 1 root root 0 Jun 23 09:26 d1.original.swapuuids
-rwxrwxrwx 1 root root 250M Jun 23 09:27 d1p1.img
-rwxrwxrwx 1 root root 14G Jun 23 09:51 d1p2.img
-rwxrwxrwx 1 root root 138 Jun 23 09:51 d1p3.img
-rwxrwxrwx 1 root root 1.4G Jun 23 09:54 d1p5.img

When I try to run a download task on a separate machine it restores grub and the mbr, but doesn’t restore any of the partition data. I saw an error about EBR signature for logical partitions being invalid and then it finishes and reboot to a grub rescue prompt.

It occurred to me just now that there is a d1p3 and a d1p5, but no d1p4 which I’m guessing is the ubuntu root partition. It looks like the image may not be uploading properly. Or the upload script isn’t detecting/saving the partitions correctly.

As a test I tried uploading a new image with Single Disk - Resizable as the image type and that definitely didn’t work. It created files, but didin’t pull any of the data from the drive.

@Tom-Elliott Should I give the latest trunk a try?

@mccabem Which pxe file are you passing to your machines? Undionly.kpxe?

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

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

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

@Wayne-Workman Thanks for your reply. A little more background here, in case the water wasn’t muddy enough. On a prior FOG install using the Official 1.2.0 release from last summer, or an SVN from very shortly after anyway, r2100s maybe, those were the image settings that I needed to use in order to get a working image that could then be pushed to other workstations in the lab I’m maintaining. I’m sure code has changed significantly in the last year so I have no idea what is and isn’t expected behavior here.

@Tom-Elliott Thanks for checking on it. Should I be/try using Single Disk - Resizable for this case or will that not work given the 4 partitions on the disk?

svn r3562 installed. I’m running into an issue trying to upload a dual boot image with Win8.1 and Ubuntu 14.04. My image settings are as follows:
OS: Linux - (50)
Image Path: /images/15SU
Image Type: Multiple Partition Image - Single Disk (Not Resizable) - (2)
Partition: Everything - (1)
Protected: Unchecked
Compression: 6

When the image process is complete this is what I end up with in my /images/15SU directory:

-rwxrwxrwx 1 root root 0 Jun 16 17:07 d1.has_grub
-rwxrwxrwx 1 root root 1048576 Jun 16 17:07 d1.mbr
-rwxrwxrwx 1 root root 0 Jun 16 17:07 d1.original.swapuuids
-rwxrwxrwx 1 root root 10702305 Jun 16 17:08 d1p1.img
-rwxrwxrwx 1 root root 90732163352 Jun 16 19:28 d1p2.img
-rwxrwxrwx 1 root root 137 Jun 16 19:28 d1p3.img
-rwxrwxrwx 1 root root 20 Jun 16 19:28 d1p5.img

Then when I try to send a download task to a different machine using 15SU as the image, the script complains that it can’t find the d1.original.partitions file and quits out. Should I be using a different Image Type for this?

@Tom-Elliott updated this morning to r3562 and everything is working like a champ. Kudos to the dev team. You all are doing great work!

@Tom-Elliott Thanks Tom. I will test today with the latest SVN.