@mrpumba Please search the forums and github for “php-gettext” and you will find out. If you still need further help you need to tell us which Linux OS and version you are using.

@wayne-workman

The FOG server is running at home and I forget exactly what else is running on it. KMS emulator, and some other things that are easy to migrate. It’s just… I suck at Linux and I remember making lots of tweaks here and there and the idea of doing that all over again is a PITA to me.

The more I think about it, it wouldn’t be a big deal to start fresh.

@sebastian-roth Will do! sorry about that.

Thanks again.

@reggiep9000 said in Supermicro AS -2024US, Intel x710 NIC No Network Interfaces found Kernel Missing the correct driver:

perfect thanks, do i need to restart any services?

No restart needed.

@kvothe88 said in Stuck at bzImage after selecting image to deploy:

hi, im using a UDM pro from Ubitiqui as DHCP so that doesnt help…i have a laptop and only boots with snponly.efi…but stuck in bzimage at deployment. Dont know what else to do

Well from your first message this sounded fairly different. Something about policy…

In this case I suggest you open a new topic in the forums so we don’t cause unneeded confusion. Post a picture of the screen where it is stuck along with information on yor FOG version, kernel version and the exact make and model of the device you see this issue on. We’ll take it from there.

Moved the VM’s to different Laptop, problems got resolved.
I think the Processor was not compatible to run VM’s i think.

Also one problem i find is enabling EFI mode in virtual box always throws error d404479a-1b02-41f4-a7ab-407e52b807fa-image.png
Works fine without EFI mode.

Also in dhcp service enable the policy as Fog suggestions.
Now Overall Fog server setup completed. Successfully deployed images to all models of Laptops.

Thank you

@Timmaaahh I am sorry, we can’t help you with that one. CentOS 8 is dead: https://www.centos.org/centos-linux-eol/

I suggest you look into using the new upcoming distros like Rocky or Alma Linux. Both have migration scripts so you don’t need to start from scratch.

@julianc-0 said in Deployment won't configure all network adapters:

FOG only deploys the configuration on the network adapter that is being used while deploying. For example when connected to port 1 only that network adapter would be configured with IP-settings etc…

I don’t understand what you mean by this. Could be I am just lost in translation. You might want to post that question in your mother language.

@sebastian-roth the link you provided was super helpful. Upon compiling new ipxe binaries, I had to update the kernel version in FOG, and voila, we are now able to get these machines registered in Fog and deploy images. Thanks for the help! @george1421 Thanks as well!

@sebastian-roth said in Fog stuck on "Running post init script":

ommand does not make sense. Should be chmod -R 777 /images.
If that still does not solve your issue you

thanks for all, problem was solved by reinstalling FOG Server

@zaqen said in Create second admin fog user:

Sorry, i try this on différent server where i use fog 1.5.9, example the new users can’t delete old image.

What error do you get when you try to delete the old image?

@tramirez Try using a different hard drive to deploy to, so we can rule out hardware issues.

@george1421 Hi,
So, you were right, i have dhcp offer from an adress ip (10.139.178.1) the ip adress doesn’t tell me anything, i have fix all my ip adress on my tru DHCP so i will investigate. Thanks for your help 🙂

@george1421 made it into all one script, even the mkkeys.sh

#!/bin/bash apt-get update apt-get upgrade -y apt-get install -y openssl efitools gnu-efi git build-essential help2man libssl-dev perl -e'use CPAN; install "File::Slurp"' mkdir -p /opt/fog/secureboot/efikeys cat << EOF > /opt/fog/secureboot/mkkeys.sh #!/bin/bash # Copyright (c) 2015 by Roderick W. Smith # Updated 26-Nov-2021 by George1421 for the FOG Project # Licensed under the terms of the GPL v3 NAME=FOGProjectSB openssl req -new -x509 -newkey rsa:2048 -subj "/CN=$NAME PK/" -keyout efikeys/PK.key \ -out efikeys/PK.crt -days 3650 -nodes -sha256 openssl req -new -x509 -newkey rsa:2048 -subj "/CN=$NAME KEK/" -keyout efikeys/KEK.key \ -out efikeys/KEK.crt -days 3650 -nodes -sha256 openssl req -new -x509 -newkey rsa:2048 -subj "/CN=$NAME DB/" -keyout efikeys/DB.key \ -out efikeys/DB.crt -days 3650 -nodes -sha256 openssl x509 -in efikeys/PK.crt -out efikeys/PK.cer -outform DER openssl x509 -in efikeys/KEK.crt -out efikeys/KEK.cer -outform DER openssl x509 -in efikeys/DB.crt -out efikeys/DB.cer -outform DER GUID=`python3 -c 'import uuid; print(str(uuid.uuid1()))'` echo $GUID > efikeys/myGUID.txt cert-to-efi-sig-list -g $GUID efikeys/PK.crt efikeys/PK.esl cert-to-efi-sig-list -g $GUID efikeys/KEK.crt efikeys/KEK.esl cert-to-efi-sig-list -g $GUID efikeys/DB.crt efikeys/DB.esl rm -f efikeys/noPK.esl touch efikeys/noPK.esl sign-efi-sig-list -t "$(date --date='1 second' +'%Y-%m-%d %H:%M:%S')" \ -k efikeys/PK.key -c efikeys/PK.crt PK efikeys/PK.esl efikeys/PK.auth sign-efi-sig-list -t "$(date --date='1 second' +'%Y-%m-%d %H:%M:%S')" \ -k efikeys/PK.key -c efikeys/PK.crt PK efikeys/noPK.esl efikeys/noPK.auth sign-efi-sig-list -t "$(date --date='1 second' +'%Y-%m-%d %H:%M:%S')" \ -k efikeys/PK.key -c efikeys/PK.crt KEK efikeys/KEK.esl efikeys/KEK.auth sign-efi-sig-list -t "$(date --date='1 second' +'%Y-%m-%d %H:%M:%S')" \ -k efikeys/KEK.key -c efikeys/KEK.crt db efikeys/DB.esl efikeys/DB.auth chmod 0600 efikeys/*.key echo "" echo "" echo "For use with KeyTool, copy the *.auth and *.esl files to a FAT USB" echo "flash drive or to your EFI System Partition (ESP)." echo "For use with most UEFIs' built-in key managers, copy the *.cer files;" echo "but some UEFIs require the *.auth files." echo "" EOF chmod a+x /opt/fog/secureboot/mkkeys.sh cd /opt/fog/secureboot/ ./mkkeys.sh git clone git://git.kernel.org/pub/scm/linux/kernel/git/jejb/efitools.git cd /opt/fog/secureboot/efitools make mkdir -p /opt/fog/secureboot/hwkeys cd /opt/fog/secureboot/ efi-readvar -v PK -o /opt/fog/secureboot/hwkeys/hw_PK.esl efi-readvar -v KEK -o /opt/fog/secureboot/hwkeys/hw_KEK.esl efi-readvar -v db -o /opt/fog/secureboot/hwkeys/hw_db.esl efi-readvar -v dbx -o /opt/fog/secureboot/hwkeys/hw_dbx.esl chmod 666 /opt/fog/secureboot/hwkeys/* cp /opt/fog/secureboot/efikeys/* /opt/fog/secureboot/efitools/ cp /opt/fog/secureboot/hwkeys/* /opt/fog/secureboot/efitools/ cd /opt/fog/secureboot/efitools cat hw_db.esl > DB.esl cat hw_KEK.esl > KEK.esl cat hw_dbx.esl > dbx.esl rm LockDown*efi LockDown.so LockDown.o make cp LockDown-signed.efi EnrollKeys.efi mkdir -p /tftpboot cp /opt/fog/secureboot/efitools/EnrollKeys.efi /tftpboot mv /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/bzImage-unsigned sbsign --key /opt/fog/secureboot/efikeys/DB.key --cert /opt/fog/secureboot/efikeys/DB.crt --output /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/bzImage-unsigned mv /var/www/html/fog/service/ipxe/bzImage32 /var/www/html/fog/service/ipxe/bzImage32-unsigned sbsign --key /opt/fog/secureboot/efikeys/DB.key --cert /opt/fog/secureboot/efikeys/DB.crt --output /var/www/html/fog/service/ipxe/bzImage32 /var/www/html/fog/service/ipxe/bzImage32-unsigned mv /var/www/html/fog/service/ipxe/refind.efi /var/www/html/fog/service/ipxe/refind-unsigned.efi sbsign --key /opt/fog/secureboot/efikeys/DB.key --cert /opt/fog/secureboot/efikeys/DB.crt --output /var/www/html/fog/service/ipxe/refind.efi /var/www/html/fog/service/ipxe/refind-unsigned.efi mv /tftpboot/ipxe.efi /tftpboot/ipxe-unsigned.efi sbsign --key /opt/fog/secureboot/efikeys/DB.key --cert /opt/fog/secureboot/efikeys/DB.crt --output /tftpboot/ipxe.efi /tftpboot/ipxe-unsigned.efi mv /tftpboot/snponly.efi /tftpboot/snponly-unsigned.efi sbsign --key /opt/fog/secureboot/efikeys/DB.key --cert /opt/fog/secureboot/efikeys/DB.crt --output /tftpboot/snponly.efi /tftpboot/snponly-unsigned.efi mv /tftpboot/snp.efi /tftpboot/snp-unsigned.efi sbsign --key /opt/fog/secureboot/efikeys/DB.key --cert /opt/fog/secureboot/efikeys/DB.crt --output /tftpboot/snp.efi /tftpboot/snp-unsigned.efi

@jmvela2x Well this thread has been going on for 5 days now and I’m not sure I’ve done a good job explaining how FOG works.

With DHCP Profiles setup with the same computer.

BIOS Computer -> BIOS PXE Boot -> undionly.kpxe will be sent to target computer -> the global value of FOG Settings value contained in [BOOT EXIT TYPE] will be used -> SANBOOT for its Exit mode

UEFI Computer -> UEFI PXE Boot -> ipxe.efi will be sent to target computer -> the global value of FOG Settings value contained in [EFI BOOT EXIT TYPE] will be used -> REFIND_EFI for its Exit mode

This process works 99.9% of the time. The oneoffs that you might find would be UEFI based computers with quirky firmware or hardware.

turns out that the image had to be set to “Multiple partition image - single disk (not resizeable)”

@Sebastian-Roth for future reference, I will be sure to mention version numbers

Everything else worked including the .xml file.

Thank you for the assistance!! 🙂

@lgwapnitsky The advanced menu is something that you have to create by hand. Its creation is a bit more prehistoric than the rest of FOG. You create your Advanced menu via a text file and then paste the contents into a field in the FOG Settings page. I’d really like to see the Advanced menu integrated into the standard iPXE menu maker to make things easier for the FOG Admins. Maybe in time…

@duncan
removed the storage node and it seems to be working now.

Il try to rebuild the node and test again.

@sebastian-roth
Ping results showed it would drop completely once the PC froze. And by froze I mean it would completely freeze all of the sudden, not gradually. I ended up checked the RAM, and it turns out one of the sticks was bad so instead of a total of 16gb I had 12gb. I had my Fog server with 4gb of ram and the Windows VM 8gb, so no memory left for the actual PC running it all. Just lowered RAM on windows vm to 4gb and it’s all fine. I can now continue with my testing!!
Anyways, thanks for the reply, love seeing how helpful the FOG mods are!

@daansterckx There are a couple of things you want to check:

When the PC boots up, does it show the correct FOG server IP somewhere on the screen? On the FOG server run the following commands and post output here: ls -al /tftpboot/undionly* ps ax | grep -e xinet -e tftp netstat -antup | grep "LISTEN" | grep "69"