• Basics for WinPE PXE boot using fog

    Re: Using FOG to PXE boot into your favorite installer images

    Please Add “Paragon Hard Disk Manager” to your list this should work with any WinPE

    Configuration currently works for UEFI only. It appears the wim file is missing bootmgr.exe for the BIOS booting systems

    It is highly recommended to use this on a machine that has 4GB+ RAM.

    First we’ll create the required directories:

    mkdir -p /var/www/fog/Tools/{iso folder name}
    chmod -R 777 /var/www/fog/Tools/{iso folder name}

    Now we’ll mount the WinPE iso over the loop directory. Then we’ll copy the contents of the DVD to the directory we built above.

    mkdir -p /mnt/loop
    mount -o loop /{full path where you have the iso stored}/{iso file} /mnt/loop

    We are going to copy to /var/www/fog/Tools so we can use the http protocal already setup for fog management.

    cp /mnt/loop/bootmgr /var/www/fog/Tools/{iso folder name}
    cp /mnt/loop/boot/bcd /var/www/fog/Tools/{iso folder name}
    cp /mnt/loop/boot/boot.sdi /var/www/fog/Tools/{iso folder name}
    cp /mnt/loop/sources/boot.wim /var/www/fog/Tools/{iso folder name}
    cp /mnt/loop/efi /var/www/fog/Tools/{iso folder name}
    umount /mnt/loop

    Download and install the latest wimboot kernel and extract it from the zip file.

    cd /tmp
    wget http://git.ipxe.org/releases/wimboot/wimboot-latest.zip
    unzip wimboot-latest.zip

    Copy the wimboot file from the archive directory to root of the os directory (we’ll need this for every windows boot media, so we’ll place it in a common spot).

    mkdir -p /tftpboot/os
    cp ./wimboot-2.6.0-signed/wimboot /tftpboot/os
    chmod -R 777 tftpboot/os

    The last bit of magic we need to do is setup a new FOG iPXE boot menu entry for this OS.
    In the fog WebGUI go to FOG Configuration->iPXE New Menu Entry
    Set the following fields

    Menu Item: os.{iso file name}
    Description: {iso file you would like to boot from}
    set tftp-path tftp://${fog-ip}
    set http-path http://${fog-ip}/fog/Tools/HD_Manager
    kernel ${tftp-path}/os/wimboot gui
    imgfetch --name bootmgr ${http-path}/bootmgr bootmgr
    imgfetch --name bootx64.efi ${http-path}/efi/boot/en_us/bootx64.efi bootx64.efi
    imgfetch --name BCD ${http-path}/bcd BCD
    imgfetch --name boot.sdi ${http-path}/boot.sdi boot.sdi
    imgfetch --name boot.wim ${http-path}/boot.wim boot.wim
    boot || goto MENU

    That’s it, just pxe boot your target system and pick os.{iso file name} from the FOG iPXE boot menu.

    posted in Tutorials
  • RE: fog configuration problem

    @alexamore90 Is this a typo with IP, gateway and DNS all set to the same address?

    You might want to run systemctl status isc-dhcp-server (Debian/Ubuntu) or systemctl status dhcpd (Redhat based distros) and post output here.

    posted in FOG Problems
  • RE: Node is offline

    @alexamore90 Did the installer finish all the way to the end? When running it there is a point where you need to open the browser and let it populate the database. If you skip this the installer will fail and needs to be run again.

    The node offline sounds like the installer didn’t finish properly.

    posted in FOG Problems
  • RE: ability to load a menu item on a specific machine as an immediate task

    @ksrvpvl As soon as the machine is registered in the FOG web UI a task can be scheduled. This would send WOL packets to wake up the machine and let it PXE boot straight into the scheduled task.

    posted in FOG Problems
  • RE: "Image size: ON CLIENT" shows the total size of the captured disk

    @Tauric From the pictures we see that FOG recognized the filesystem as NTFS and should be able to resize it. It’s still strange the size was larger. Good you got this fixed by reinstalling the master to capture from. No idea what could have been wrong with the other one.

    posted in Bug Reports
  • RE: Error with after mdraid true

    @tomynocker Looks like you used the wrong field. Such an options need to go in Kernel Parameter.

    posted in FOG Problems
  • RE: Tips for reducing image size?

    @matthewadams12 It depends on the partitioning and filesystems used. If Ubuntu is installed with LVM it will be captured sector by sector (large). But if you choose plain GPT or MBR partitioning FOG should be able to capture the used space only.

    posted in General Problems
  • Owner and permissions in /images

    Hi FOGers!!

    We have some strange issues when we upload images to the server and we don´t have find the reason of this behaivour.

    The issue appears when the server try to move the image from /images/dev/abcdefg12345 directory to the destiny, the FTP can´t move the file or the directory and the destiny directory appears empty.

    In the vsftpd log appears the error:

    Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP command: Client "", "LIST -a images"
    Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP response: Client "", "150 Here comes the directory listing."
    Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP response: Client "", "226 Directory send OK."
    Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP command: Client "", "RNFR /images/dev/8cec4b6xxxxx"
    Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP response: Client "", "550 RNFR command failed."
    Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FAIL RENAME: Client "", "/images/dev/8cec4b6xxxxx"
    Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP command: Client "", "QUIT"
    Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP response: Client "", "221 Goodbye."

    The permissions in /images is:

    drwxrwxrwx  295 fogproject apache 16384 nov  3 09:40 images

    We have migrated the old server, fog 1.5.5, to the last one, fog 1.5.10, we made a fresh install but we migrated the storage from the old one to the new one. Then in /images we have a mix of owners XD:

    drwxrwxrwx    2 root       root     280 ago 24 10:27 aula-vc-filologia-aulavhm2-alumno3450
    drwxrwxrwx    2 fogproject apache   226 jul 26  2022 aula-vc-filologia-aulavhm2-profesor
    drwxrwxrwx    2 root       root     280 ago 24 14:52 aula-vc-filologia-aulavhm2-profesor3450
    drwxrwxrwx    2 root       root     226 jul 19 12:28 aula-vc-filologia-aulavhmm-docencia
    drwxrwxrwx    2 fogproject apache   226 mar  8  2023 aula-vc-filologia-aulavhmm-docencia-LTSC
    drwxrwxrwx    2 root       root     226 ago 25 12:36 aula-vc-filologia-aulavht1-cabina
    drwxrwxrwx    2 root       root     226 ago 28 09:55 aula-vc-filologia-aulavht1-profesor
    drwxrwxrwx    2 fogproject apache   226 abr 29  2021 aula-vc-filologia-aulavht1-roomserver

    The question is easy 🙂 Who is the owner of images directories?

    posted in FOG Problems
  • RE: Stuck in Deploy Image loop

    @w2log Does this SuperMicro X12 have more than two NICs onboard? Then it’s probably a bug in FOG fixed in the latest dev-branch version already.

    posted in FOG Problems
  • RE: installing package : php-mysqlnd failed

    @infotc While a clean migration would surely get you to a nice clean system you can first try to get this fixed manually.

    There is some logic in the FOG installer that should take care of the different package names that have changed over the years (php-mysql vs. php-mysqlnd).

    Please run the following command to see what PHP packages exactly are installed at the moment:

    dpkg -l | grep php

    Post the output here.

    Edit /opt/fog/.fogsettings and make sure only php-mysql (but not php-mysqlnd) is in the packages line.

    As well you might want to manually install the package needed - see if that gives you an error as well:

    apt install php-mysql
    posted in Linux Problems