Topics created by FuriousGamer065

@george1421 The campus has it’s own subnet, im changing the problem with it. When I used a VM to test it, desktops in the lab have a hard time trying to connect to the FOG server via pxe boot. It times out after it tries to bring the gui up. So I’m trying to figure out why it keeps timing out. VMs will boot to it fine, but any physical systems either time out or boot fine with it.

@george1421 That’s probably why its not working, I have my root account username is fog. Thank you, I will change it

@FuriousGamer065 There might be a PHP-FPM error log as well.

@sebastian-roth I’m just going to reinstall ubuntu

@sebastian-roth I looked in the registry and I deleted the left over fog files, I got it to work after a little tinkering.

@george1421 Thank you so much! It works now!

@FuriousGamer065 First let me say I’m asking because I don’t know.

Does NVMe disks work in bios mode?

For SANBOOT you have to remember that is a bios only boot loader (built into iPXE). It references disks by their bios ordinal position.

For example with FOG it issues this command when you pick SANBOOT. sanboot --no-describe --drive 0x80 In bios syntax drive 0x80 is the first hard drive 0x81 is the second hard drive and so on. Since you have 3 drives 0x82 is the last bios referenced drive. Its possible because of the bios order 0x80 may not be your NVMe drive but a sata drive (I don’t know) but that will explain why SANBOOT is not working for you.

So you might ask how can well tell. Good question…

I think what I would do is create 2 new iPXE menus for testing.

The concept is based in this tutorial: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

But we are going to make a twist on this.

Make two new iPXE menus:
Menu Item: os.Sanboot.D2
Description: Sanboot Drive 2
Parameters:
sanboot --no-describe --drive 0x81 || goto MENU
Menu Show with: All Hosts

Menu Item: os.Sanboot.D3
Description: Sanboot Drive 3
Parameters:
sanboot --no-describe --drive 0x82 || goto MENU
Menu Show with: All Hosts

Now boot into the iPXE menu and see if either of the new sanboot menus work. It will be interesting to know if one of the alternate menus work correctly.

@FuriousGamer065 So did you use my tutorial and config file exactly to setup your dnsmasq service? https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

@FuriousGamer065 Now if you were going to do 50 or more per year I would recommend a bit different approach in that you will create a fat image and include all of the applications you need right in the golden image. You would only install applications post imaging that require a system unique ID like enterprise virus protection. You would also use the unattend.xml file to answer all of the preinstall OOBE questions so the deployment is completely lite touch. https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem?_=1584219461172 You would also create a post install script to install the system specific drivers etc.

@FuriousGamer065 Wow quite a gap here in response.

You need to know what mode the firmware is in because it controls a number of things. In the case of the boot loader you will need to send ipxe.efi as the boot file to the target computer for uefi mode. The same thing kind of applies to the source image. You can only deploy an uefi captured image to a uefi based computer. You can’t mix bios and uefi systems.

@FuriousGamer065 You probably should run through the tutorial to ensure that all of the bits are in the right spot and then rerun the fog installer.

Understand this will only address the ftp issue. There still may be the issue related to unable to find the storage node. That’s on the NFS site of the image upload.