@kafluke It happens to me too. Also on the latest dev-branch, Advance Menu has stopped working.
Posts made by TaTa
RE: Issues after changing server IP
@Sebastian-Roth @Wayne-Workman Thank you for reminding me about another DHCP server. I double checked with our network admin and we found the old IP in DHCP server. We did some tests before but couldn’t get pxe to work so we opted for dnsmasq option and left the IP there.
Thank you again for your help!
Issues after changing server IP
We have to migrate our servers to a different building so we need to change our FOG IP. I follow instructions to change the server IP and IP in FOG website as instructed in here: https://forums.fogproject.org/topic/10841/problems-after-changing-fog-server-ip/2. I even ran updateIP tool and reran the installation several times. Client boots up fine but when it gets the palce to download default.ipxe file through tftp, it is still looking for the OLD server IP. FOG is running on Debian 8.11 with DNSMASQ 2.76. I checked dnsmasq configuration file and it does have the new IP and it’s not providing tftp service. I’m using tftpd-hpa for TFTP service . config.class.php does have the new IP as well. What am I missing here?
Thanks in advance for your helps or suggestions.
RE: Booting Ubuntu 18.04 Live CD
@nsherin I didn’t use any other files beside the ones came with 18.04.1 LTS. Can you re-extract all files in 18.04.1LTS iso and then reupload them back to /images/os/ubuntu/18.04/mate. You might need to add this line to your /etc/exports file and restart nfs services or restart your fog server.
Internet connection is still an issue with this method. You need to go to /etc/network/interfaces and change from manual to dhcp then restart your interface sudo /etc/init.d/networking restart
RE: Booting Ubuntu 18.04 Live CD
You need to add initrd=initrd.lz. I found it here: https://forums.fogproject.org/topic/11063/ubuntu-17-10-desktop-pxe-boot-no-internetl and it worked for me.
Your code should look something like this.
kernel nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/vmlinuz initrd nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/initrd.lz imgargs vmlinuz initrd=initrd.lz root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.0.14:/images/os/ubuntu/18.04/mate/ locale=en_GB.UTF-8 keyboard-configuration/layoutcode=gb quiet splash toram ip=dhcp rw boot || goto MENU
RE: Error 'Could not open inode 'XXXXXX" through the library'
RE: New to imaging Macs through FOG
@CoolbluHat as Sebastian Roth said, you need to bless your clients (SIP must be disabled) or you can create a bootable usb
- Format USB as FAT32
- create folders in USB drive EFI\BOOT
- Copy ipxe.efi in your tftpboot directory in your FOG server to EFI\boot and rename this file to bootx64.efi (try different *.efi files if this one does not work)
Prepare to upload image:
Like you do for Windows machines, create a standard image, add a new host for this Mac
create a new image in Image Management. Select Apple Mac OS, Multiple Partition Image - Single Disk
Schedule an image capture
Boot up this Mac using USB (hold down alt and select EFI).
You might need to grow the disk if you download the image to a bigger drive.
This method does not work for all Macs at least does not work on my MacBook Air early 2014 but worked on MacBook Air late 2015 using thunderbolt to ethernet with ssd formatted in 4K cluster size and most of the models with a built-in Ethernet card.
DNSMASQ 2.76-5 on Jessie
I saw that Debian released a stable version of DNSMASQ 2.76-5 for Stretch. Has anyone tried this version on Jessie? I want to use UEFI but worry about its comparability on Jessie. In general, is it okay to use packages designed for Stretch on Jessie?