Files not updating with version upgrade
-
I’ve had this FOG install since 1.2.0. Been using it for really basic stuff and never had a problem so I feel like a complete noob, please treat me like one.
We’ve been doing BIOS images until now and I’m switching to UEFI, vendor classes, and all the fun new stuff that comes with. I thought I had everything set up perfectly but it wouldn’t work. I hit the laptop with wireshark and found it’s looking for the surface pro 4 efi file (ipxe7156.efi). So I go hunting for it and and discover I don’t have it or any other efi files…turns out there are a lot of files not in my tftp directory that I should have for being on v1.5.9. Comparing to 1.4.4 I’m 1 directory and 10 files short. Current files seem to be updating but I’m not pulling any new files…maybe since 1.2.0?
Maybe I messed something up when I upgraded to trunk 4 or 5 years back, or I’m not pulling from Git correctly? Here’s how I’ve been upgrading:
cd /opt/fog
sudo git pull
cd bin
sudo ./installfog.shcheck git version:
cd /opt/fog
sudo git log -1Huge thanks for everyone’s help!
-
@dudenamedben What device is your dhcp server? It is responsible for sending out the boot loader file name, not the FOG server (unless the FOG server is the dhcp server for your network).
-
@george1421 Thanks for that quick reply! DHCP server is Windows server in AD. I have the boot file name in option 67, but the actual file, ipxe7156.efi, is not present on the Fog server in the tftp directory.
-
@dudenamedben said in Files not updating with version upgrade:
ipxe7156.efi
That boot file was deprecated in the FOG enviroment quite a while ago. It was only used to support the ms surface books for pxe booting because at the time the latest ipxe boot loader was breaking on the surface books. The proper boot loader for efi is
ipxe.efi -
@dudenamedben said in Files not updating with version upgrade:
cd /opt/fog
sudo git pull
cd bin
sudo ./installfog.shTwo things I notice here:
- The directory /opt/fog is used by FOG itself to store the settings file, certificates and snapins. I am not sure what happens if you use that same location for the git repo as well.
- We don’t advice to use sudo to run the installer anymore as it has cause problems in the past. Switch to root (
sudo -i) and then run the installer.
-
@george1421 Sheesh, deprecated files. I hadn’t considered that or even NOT comparing what I have to 1.4.4. Did I mention noob?
I tried to edit my initial post to reflect that I was wrong about not having any efi files, we have ipxe, intel, and realtek. I’ve changed my DHCP config back to the way it was before tinkering with the efi stuff.
I now have ‘server option 67’ as ipxe.efi. Now, attempting to pxe boot gets me a “no configuration methods succeeded”. I installed a dumb switch between the target PC and our enterprise switches to eliminate the spanning tree problem.
Don’t know if this helps, I had wireshark on this during pxe boot and it’s IDing as Arch:00007:UNDI:003016 (which is why I initially went with the ipxe7156.efi).
-
@dudenamedben said in Files not updating with version upgrade:
I now have ‘server option 67’ as ipxe.efi. Now, attempting to pxe boot gets me a “no configuration methods succeeded”. I installed a dumb switch between the target PC and our enterprise switches to eliminate the spanning tree problem.
So you still have a no methods succeeded with a dumb switch in between?
-
@george1421 Correct…however I just found that there’s an snponly.efi that I hadn’t previously tried and I got the menu!
You should totally delete this whole thread. It’s simply full of me not paying attention. However, it does highlight your immense patience with an absolute dolt. So maybe it’s worth something. Thanks for your help, it did help me refocus, eliminate, and double check my work before posting.
-
@dudenamedben What hardware are you booting on?
For your INFO
snponly.efi is to undionly.kpxe
as
ipxe.efi is to ipxe.kpxeIn the only boot loaders, snp and undi use the built in nic firmware drivers to talk to the nic card. Where ipxe. has all of the network card drivers built into the ipxe boot loader. In the early days of uefi the snp drivers were terrible, that is where the FOG developers recommend to use ipxe.efi. The problem is with very new hardware, the iPXE developers might not have included the drivers in the ipxe build just yet, where the snp nic driver will work.
