@El-Fogito will you post the output of the following commands executed on the fog server. You may need to execute the sudo su - command to allow you to run all of these commands.
df -h
ls -la /images
showmount -e 127.0.0.1
cat /etc/exports
Where it is failing is the fos linux engine (OS running on the target computer), it connects to the FOG server using NFS as ‘root’. For some reason this connection is being blocked. Lets see the configuration so we can know what to test next.
@bmick10 a quick google-fu search of the error shows your ubuntu install is missing a needed library to completely compile the updated version if iPXE.
sudo apt-get install -y liblzma-dev
@bmick10 said in Fog stops at init.xz...18% and other percentages:
So it will load to Fog stops at init.xz…and different % each time.
This sounds like an iPXE issue, where its not loading FOS Linux’s virtual hard drive completely for some reason. Lets start out by having you rebuild/compile the latest version if iPXE using these instructions: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe Lets see if there is an update to iPXE that solves this issue.
@maximefog said in Deploy Image:
it is mandatory to register the workstation
This is not a requirement under certain conditions. There is a method I call “load and go”. It is a process that system builders use where once they load the OS on the target computer they never see the computer again. In this method you can not use the FOG Client for any of its function. The install process must be self contained or use a FOG post install script to make the install time adjustments to the target computer. Using this method you do not need to register the computer with FOG. Once the image is deployed to the target computer FOG forgets it ever saw this target computer. Once you have the master image setup as needed you deploy the image from the FOG iPXE menu “Deploy Image” menu. You never have to touch the FOG web ui for image deployment.
@jenesis I’m going to say that since this is a hardware security device its not possible to pxe boot it. I can see the device manufacturer using the hardware security key as part of its integrity control to ensure its OS hasn’t been tampered with.
But I would not rely on my guess alone. I would contact the company’s support team and ask if the software can be pxe booted. If yes, then we can probably get it to boot via iPXE. You also want to ensure you are not in violation of the manufacturers EULA by pxe booting something you shouldn’t.
@jenesis The quick answer is maybe you can, but also maybe no.
There are some iso images you can convert to ipxe boot. Lets first start by getting the name of the software you want to pxe boot. What is the name of the software?
@pilipp_edv said in general questions about storage / master storage nodes:
After that, I configured the windows DHCP servers in the other locations to point to the main FOG server.
FWIW: You can (should) point the remote dhcp server to the remote storage node so the clients doesn’t need to transfer the ipxe boot image across your wan. The storage node will instruct the clients to “check in” with the fog master node.
The part you are missing is the FOG server plugin “Location”. With the location plugin you first identify your different locations. Then assign storage nodes to the “location” then assign existing client computers to the location. As you full register new clients there will be an added prompt for location during registration. This plugin pulls all of the bits together to make the clients find the proper storage node.
@Bhav Just for clarity, do you have an isolated imaging network or are you trying to image on your business network?
If you have an isolated imaging network then you should have configured FOG to setup a dhcp server. The configuration will work for both bios and uefi computers.
If you plan to image on an existing business network, then your primary dhcp server needs to be configured to support pxe booting.
So lets start with how do you plan on imaging?
Second if you are planning on imaging using your business network, what device is your current dhcp server?
@rdfeij For the record, what computer hardware do you have?
@luilly23 To follow on with what luilly23 said. If you have the original 7010 from 10 years ago, that was the first version of Dell desktops that supported UEFI mode. BUT if you tried to pxe boot in uefi mode iPXE would hang at initalizing devices because of a bug in the Dell 7010 uefi firmware that was never fixed by dell. In this case you must use bios mode and undionly.kpxe to boot.
If you have the modern version of the Dell 7010 and it says no boot device found… The actual problem depends on where you see the error. I’m going to guess this error is when you first turn on the computer and tries to pxe boot. In this case your dhcp server is not sending an IP address or pxe boot info to the client computer. If this is truely the “new” 7010 then your boot file will be ipxe.efi or snponly.efi. If you put a functioning windows computer on the same subnet as your dhcp server, does it get an IP address? That will tell us if your dhcp server is working. Also with that windows computer verify what device is your dhcp server.
@MonsterKaos There are 3 issues (well really 4 issues) that is probably impacting your deployment.
For issues 2, I have instructions on how to compile the latest version of iPXE here: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe Your fog server will need to have internet access to get the latest source code for iPXE. This should address the no configuration methods.
For issue 3, in the fog ui go to fog configuration-> kernel update. Download the latest kernel 6.x series to get support for the newest hardware.
Lets see where that works for you with deploying images.
@EuroEnglish I’m finding it hard to believe that there is a connection of having win11 on the computer that is causing this behavior. When the fog menus are being displayed, we are running iPXE boot loader. This in a way is an OS by itself. The OS on the target computer is not even known about at this point in the booting process.
The only thing I can think is that the format or disk structure is now allowing iPXE to fully initialize correctly.
Could you make this test for us? If you have 2 computers of the same model (make sure that bit locker is disabled on both systems) and secure boot is disabled.). One with win11 and one with win10. Verify they both behave the same way as you mentioned above.
On the win11 computer remove the hard drive/nvme drive. Boot into the FOG iPXE menu. Does it still have the slow speed?
Move the hard drive from the win10 computer to the win11 computer. Does the system act slow or normal?
@professorb24 said in How to use fog with two different VLANs:
Yes, I can ping the 192.168.54.X network.
This is positive. OK hopefully last question, what is device the dhcp server on the 54.x subnet? Is it the fog server on the 52.x subnet or something else?
@professorb24 from 192.168.52.X can you ping devices on 192.168.54.X. If yes then you have network routing setup.
Once you pass full routing, what is your dhcp server for 192.168.52.X and 192.168.54.X?
@RogerBrownTDL said in PXE TFTP File Not Found:
TFTP_DIRECTORY=“/srv/tftp”
OK then in this directory, is it blank? Different distros have different locations for the boot directory. I thought the fog installer created a standard but maybe not. If its blank, the most often cause is that you did not perform step 3 in the installer. Step 1 is to run the fog installer script, step 2 is to open a web browser to install the database, then in step 3 you return to the fog console and press enter to complete the install. This is the part where the tftpboot files are installed.
@RogerBrownTDL This condition could have several root causes, with some not FOG related.
First look to see if there is content in /tftpboot on the fog server. If that directory is missing or simply empty then you missed a step during installation (high probability)
The boot file option (dhcp option 67) needs to match the type of computer you are booting. For uefi computer it needs to be ipxe.efi or bios computer it needs to be undionly.kpxe.
If you are using a soho router for your dhcp server, many will send their IP address instead of the IP address you configured into the dhcp router. So what device is your dhcp server?
@professorb24 The quick answer is if both vlans are routable back to the fog server then yes.
If they are not, then no.
The FOG server can only support a single imaging interface. FOG is not designed to have multiple imaging interfaces.
@JJ-Fullmer said in Dell Latitude 3340 with USB-C Ethernet Adapter - bad mac address registered:
I am unable to get wol with or without fog on my lenovo laptop with the lenovo branded usb-c ethernet adapter.
Is the computer powering off the network adapter in sleep mode or keeping it active?
I know WOL from anything other than g3 mode and windows is involved (i.e. s1-s4 has some kind of windows os interaction). So the windows OS needs to leave the power on the nic to be able to be woke up from these modes. Windows is a fickle beast.
@Nicolas-Bricet This really sounds like a spanning tree issue vs dot1x authentication (unless your authentication process is taking a really long time to authenticate the port). Make sure the port is configured for port-fast, fast-stp, rstp or whatever your switch manufacturer calls it.
Secondly if TIME is the resolution then this can probably be addressed too.
First of all we have the ability to update the iPXE boot loader from a fog install. This tutorial is intended to solve a different problem but you will need this in your solution: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe
So at this point you know that you can rebuild iPXE right from your fog server. Now we need to adjust iPXE to wait 30 seconds before requesting an IP address (FWIW, by default spanning tree it take 27 seconds to start forwarding data, so the timing is suspiciously similar).
When iPXE boots up it runs a FOG custom script file that tells iPXE how to configure itself. If you can remember back to the DOS days, this was the autoexec.bat files function. iPXE has a similar script. Within the iPXE source directory the file is call ipxescript (a look on github) https://github.com/FOGProject/fogproject/blob/a4bb1bf39ac53c3cbe623576915fbc3b5c80a00f/src/ipxe/src-efi/ipxescript#L1 This is the script that runs inside iPXE to configure the network.
To take this concept one step more, the FOG developers have already created a version of the iPXE that has a 10 second boot delay (remember you need a 30 second delay). An example of this 10 second delay startup is here: https://github.com/FOGProject/fogproject/blob/a4bb1bf39ac53c3cbe623576915fbc3b5c80a00f/src/ipxe/src-efi/ipxescript10sec#L3 All you need to do is either update that 10 to a 30 or copy that line over to the ipxescript main script and change it to 30. Once that is done recompile ipxe using the instructions above.
The FOG delivered 10second delay versions of iPXE are located in the /tftpboot/10seconds directory. So you have two paths to get this done, but I would surely look into spanning tree first to make sure port fast is enabled and make the above second way unnecessary.