Net Boot Issue



  • After successful setup and configuration of FOG, I have been using Windows Server DHCP with a hyper-v instance of Ubuntu 18.04 to run FOG. In the past week, I have been receiving a persisting error message during PXE network boot and I am unsure why that is happening. Thoughts? (See Image Attachment). Here’s the setup guide that I followed originally to install FOG:

    Part 1/2
    https://www.ceos3c.com/sysadmin/install-fog-server-ubuntu-server-16-04-lts-ultimate-guide-virtualbox/
    Part 2/2
    https://www.ceos3c.com/sysadmin/create-generalized-windows-10-image-deploy-fog-server/

    alt text

    https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

    • Expand DHCP server Right click IPv4 Select Define vendor classes Click Add Repeat for each of the following:
      PXEClient:Arch:00000
      PXEClient:Arch:00002
      PXEClient:Arch:00008
      PXEClient:Arch:00009
      PXEClient:Arch:00007

    • Expand DHCP server
      Expand IPv4
      Right click Policies
      Select New Policy Name/Desc: Allow UEFI PXE handout Click Next Click Add Criteria: Vendor Class Operator: Equals Value: Select each of the following, check Append Wildcard, and Click Add PXEClient:Arch:00007* PXEClient:Arch:00008*
      PXEClient:Arch:00009*
      Click Ok
      Click Next
      Select Option 067 from DHCP Standard Options
      Set String Value to: ipxe.efi

    • Right click Policies
      Select New Policy Name/Desc: PXEClient:Arch:00000
      Click Next
      Click Add Criteria: Vendor Class Operator: Equals Value: Select each of the following, check Append Wildcard, and Click Add PXEClient:Arch:00000
      Click Ok
      Click Next
      Select Option 067 from DHCP Standard Options Set String Value to: undionly.kpxe

    • Name/Desc: i386 EFI boot
      Click Next Click Add Criteria: Vendor Class Operator: Equals Value: Select each of the following, check Append Wildcard, and Click Add PXEClient:Arch:00002* PXEClient:Arch:00006*
      Click Ok
      Click Next Select Option 067 from DHCP Standard Options Set String Value to: i386-efi/ipxe.efi

    Thanks!


    Dylan Parsons
    dylan.parsons at smsu.edu
    http://dylanparsons.me/

    EDIT:
    Hi @Sebastian-Roth!
    The issue seems to have originated from a winter power outage that resulted in DHCP failure upon reboot. I apologize for any confusion.


  • Senior Developer

    @dparsons said:

    I have been receiving a persisting error message during PXE network boot …

    Can you give us some more information on this. Usually when a client PXE boots and there is no FOG task scheduled for this host it will boot to the PXE menu and as a default chainload the OS from disk. You’d never run into the screen that you posted in the picture.

    See if you still have a task scheduled in the FOG web UI (icon in the top menu that looks like a stack of three horizontal bars). Take a screenshot an post here.

    The errors seen in the picture are most probably pointing to a hardware issue. Not something FOG is causing I think. What happens when you change boot order to directly boot from disk on this machine? Does it load Windows from the disk? Or is this a machine with an empty disk that you wanted to deploy your image to? We need more information on this to be able to help.

    Here’s the setup guide that I followed originally to install FOG:
    https://www.ceos3c.com/sysadmin/create-generalized-windows-10-image-deploy-fog-server/

    This guide does not seem to talk much about the FOG installation itself. So I am wondering what exactly did you follow?! Just asking because the pictures show a very old version of FOG and I really hope you have a more recent version installed!


  • Senior Developer

    @dparsons said:

    I have been receiving a persisting error message during PXE network boot …

    Can you give us some more information on this. Usually when a client PXE boots and there is no FOG task scheduled for this host it will boot to the PXE menu and as a default chainload the OS from disk. You’d never run into the screen that you posted in the picture.

    See if you still have a task scheduled in the FOG web UI (icon in the top menu that looks like a stack of three horizontal bars). Take a screenshot an post here.

    The errors seen in the picture are most probably pointing to a hardware issue. Not something FOG is causing I think. What happens when you change boot order to directly boot from disk on this machine? Does it load Windows from the disk? Or is this a machine with an empty disk that you wanted to deploy your image to? We need more information on this to be able to help.

    Here’s the setup guide that I followed originally to install FOG:
    https://www.ceos3c.com/sysadmin/create-generalized-windows-10-image-deploy-fog-server/

    This guide does not seem to talk much about the FOG installation itself. So I am wondering what exactly did you follow?! Just asking because the pictures show a very old version of FOG and I really hope you have a more recent version installed!


Log in to reply
 

343
Online

7.4k
Users

14.5k
Topics

136.5k
Posts