Testers

@Fimlore You have to change the path in a couple of places

The storage node image path has to be adjusted on the WebGUI of the server.

Then on the server itself:

/opt/fog/.fogsettings : storageLocation

If you let FOG build exports automatically, then just rerun the installer after that change.

If not, you have to edit /etc/exports

Do be careful of ownership and permissions in a shared image location.

Just in the fwiw bucket, we recently found out that if you have 2 or more simultaneous multicasts streams going at one time, the trasfer rates drop off quite a bit. I do remember seeing someone create a patch to change the multicast base IP address with each new stream. That seemed to resolve the issue.

[edit] Updated info: https://forums.fogproject.org/topic/12300/multicast-data-address-not-change-from-one-task-to-another-one/16

@robertkwild Why are you using syslinux to pxe boot? That is not even within the scope of FOG. FOG uses iPXE for its boot environment not syslinux. You are making things way to hard for your self.

You might want to review this post to see if there is a different way to go about it even if you are not using FOG for imaging: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

Typically to launch the distro’s installer its a kernel parameter passed from the boot launcher. With iPXE you can use tftp, http, or nfs protocols. I think that post above uses all three at different times. As Sebastian said, you just need to use the right directory root based on the protocol.

tftp == /tftpboot
http == /var/www/html
nfs == /images

@mckayj That’s great news! I’m not sure why x2apic support wasn’t enabled. As far as I know, it’s typically only used for multi CPU systems which aren’t your typical usecase for FOG I suppose. It’s very strange that it would be enabled on a single CPU board to me, but there you go anyway.

@Sebastian-Roth
I don’t think it will harm anything if we enable x2apic support going forward, it can always be disabled with a kernel parameter on boot anyway.

@aborn Only for /images

Since you are reducing permissions for “everyone” (which is ok since FOG should connect with the fog user account), you need to ensure the folder structure where it places the images has the correct ownership.

chown -R fog:root /images

probably works fine too.

New images should have fog as the owner as far as I’m aware.

@aborn Why do I see FOG 1.2.0 in the file path?

AFAIK: The postinit scripts were not added until after FOG 1.2.x

@aborn Postinit runs just after the kernel and init files load in on the client. (not on the server)

It will work on the unpacked filesystem in memory on the client device before the capturing of the image takes place.

It will work just fine.

@mckayj Okay, I think this one should have it enabled

https://drive.google.com/open?id=1ZiRWrrN3dv26bLwW8GAEdLtzGw5xkyQI

@Pikmin use this as a proven ltsp.conf file

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,<fog_server_IP>

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<fog_server_IP>
dhcp-boot=net:UEFI,ipxe.efi,,<fog_server_IP>
dhcp-boot=net:UEFI64,ipxe.efi,,<fog_server_IP>

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 1

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

dhcp-range=<fog_server_ip>,proxy

@Sebastian-Roth Gotta love how reflective this computer’s screen is…Took a picture of the debug output
https://photos.app.goo.gl/mVL8zAGAi9PN2sNc7