Posts made by jmeyer

@george1421 I have run all test and first, there were a firewall rule that were blocking TFTP from the FOG server then after running more test, I realised that it’s not link to hardware or sofware on the server.
During test, I just changed the port on the switch next the computer to keep most of the hardware between server and client.
On same vlan I run at 450 Mbits/s (around 50 mo/s) and when I change vlan, I run at 150 Mb/s only.
And under 20 mo/s max with Windows TFTP client so I give up using it to run more tests.
Colleagues says there is not QOS but there is definitly something reducing the speed.

@george1421
Do you mean using brand adapteur certified for PXE such as :
https://www.dell.com/en-us/shop/dell-adapter-usb-30-to-ethernet-pxe-boot/apd/443-bbbd/pc-accessories
or
https://www.lenovo.com/fr/fr/p/accessories-and-software/cables-and-adapters/cables-and-adapters_adapters/4x90s91831

@george1421 I have created a 500mo file since most of original files are small in the FOG tftpboot directory and try to download it with Windows TFTP client.
It takes me around 10 to 15 min to download it.
I have also tested on ThinkPad E15 gen 4.
Is there a speed limit in TFTP ?

On the E15 and the E16, it’s a Realtek RTL 8168 Series.
ID on E15 is PCI\VEN_10EC&DEV_8168&SUBSYS_50B117AA&REV_15
ID on E16 is PCI\VEN_10EC&DEV_8168&SUBSYS_50D517AA&REV_15

edit : I have find out that Windows TFTP client is mess up with max speed.
I have reach 450Mb/s with Ivanti from PXE when I still stuck at less than 20 Mb/s with Windows TFTP client.
Another thing is that I have add FOG menu entry to download a file from Ivanti PXE (chain command) and I also download at only 6 Mb/s.
I’ll run more test directly from PXE diring the next days.

We found IPS rules (I think it’s the name) on the firewall that was blocking TFTP.
It’s now loading but terribly slow (average 6 Mb/s on a Gb link).
We will make more test today.

As said, no problem with legacy boot that use same configuration on dhcp (option 66 and 67) and use the same vlans.
I get well the IP then it give timeout.
I’m not on the same vlan but is there differences between legacy and efi or if one work, the other should ?
Maybe it’s rights between vlan that block only efi.
I’m not sure since when I have the problem but we changed switchs few weeks ago.

I’ll put a wireshark tomorow to look what happen.

Thank you

Hello,
I have a timeout during pxe boot with an install of FOG (version 1.5.10.1622) on a Lenovo ThinkPad E16 gen 1.
SecureBoot is disabled.
I didn’t notice error with legacy boot on older computers and a tftp client under Windows can download the “.efi” files.
I tested with snponly.efi and ipxe.efi, same error.
My personnal FOG server under version 1.6.0 doesn’t give any error.
In other high school, I didn’t had problem with a FOG 1.5.10
I have download last kernel (6.6.49), the last Initrd (2024.02.5) and build ipxe file using the doc here : https://docs.fogproject.org/en/latest/kb/reference/compile_ipxe_binaries/ but problem is the same.
I’m out of idea.
Thank you for your help.

@george1421 Rebuild to last version didn’t fix the problem.
@Tom-Elliott Exit type to EXIT give a “chainloading failed…”

using snponly.efi fixed the problem.

Thank you for your help.

Hello,

For the first time, I had “zstd /stdin unsupported format” during deploy after moving an image between FOG servers and crossing two Windows computers.

I end checking CRC with the commands directly inside image directory :

• On Linux with :

cksum *

Result :

4102865288 6 d1.fixed_size_partitions
1553301511 1048576 d1.mbr
21074109 873 d1.minimum.partitions
3930731312 20 d1.original.fstypes
4294967295 0 d1.original.swapuuids
3323012245 11304005 d1p1.img
4080882029 767 d1p2.img
4038447468 7834146234 d1p3.img
1735290603 153344 d1p4.img
1356735187 873 d1.partitions
2087979657 873 d1.shrunken.partitions

• On Windows Powershell with :

Get-ChildItem * | Select-Object -Property Name,@{name="Hash";expression={(Get-FileHash $_.FullName).hash}}

Result :

d1.fixed_size_partitions 8F2326E98FF66634578EC07879B45A6ADA0B681444819A581F5F3BFCA5FA6029
d1.mbr                   5113DDB273F26E0D6F88367B5330BEF6E2A7FD399984EDB3519268DDE7B4FFCE
d1.minimum.partitions    8A04A480F69C6A6084DDF9EB43F37E913C14C5EF57AF58CBB7406CD2CB832CAC
d1.original.fstypes      A061EFCFAA6B32FBD533450D14E71E2C1EC422AC67A8F8296B773A46407F5914
d1.original.swapuuids    E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855
d1.partitions            3F23AA64C5AFDCE83CCB59AACF2F03EDAD3EA6429B22010339C43B29DE406D2C
d1.shrunken.partitions   59D5B234D923B3B73EA0CB808853397B8D19644C9E135BFDD8C538633ECE4106
d1p1.img                 6B3A9D5B0C26BE448A24339F7DE1067A4C0F3615D9BE42B86BEB355BA6F9BCE6
d1p2.img                 511CBE019A39980DF90F7D9A547BAE4521551EEF53625705538713AB14311DD0
d1p3.img                 5F2223BB3D63C9400C77C10A5ADF5AE2DCA48D8C768AC2097F20E3731E843FC9
d1p4.img                 A8D21F3E22C596EA01B8F7BAC981C9FB265938D0A1A3F2C3599ADF170A75CE9E

This way I can check between my 2 computer under Windows before checking between my two FOG servers.

@george1421 As it’s happening only on my personnal FOG install, I don’t care to have to unplug lan cable.
I’ll try rebluild iPXE when I have time.
Thank you.

@garrett-stevenson
I’m not sure of your question but I have installed fog from zip without internet (I am also behind a firewall) by using the -X (–exitFail Do not exit if item fails").
Then I downloaded them with other computer and have copied them in the /var/www/html/fog/service/ipxe/ directory with winscp (using home as intermediate directory and then puting back rights and owner)
Yet I had all packages needed to run fog already installed.

The problem doesn’t appear with my other FOG server .
FOG version 1.5.9.37
Kernel 5.15.19
Exit type : REFIND_EFI

Hello,

FOG 1.6.0-alpha 1182
Kernel 6.1.22
Exit type : REFIND_EFI

After deploying an image that have been sysprep with the two last version of Windows 10 (21H2 and 22H2) and 11 22H2 on Lenovo M75q Gen2 and Lenovo M70q, I have BSOD “DRIVER VERIFIER DMA VIOLATION” if i go through EFI PXE.
If I disconnect network cable during boot, I don’t have this BSOD.

I don’t have the problem with Lenovo and HP computer from 2018.

What PXE could change during Windows boot that can create a BSOD ?

Thank you.

Add NAS on the same network of the FOG server.
In my case, FOG server has IP 192.168.0.50 and NAS has 192.168.0.55.

On the ReadyNAS web interface

• Add a share and select NFS protocol.
  

• Click on the
  
  of the share to add allowed computer.

• Enter the IP of the FOG server and clic Add
  

• On the FOG server, create a new image directory and mount your NAS share
  

• Test write from FOG server
  

You should see the new directory on the ReadyNAS web interface

To mount it add FOG server boot, edit the /etc/fstab file and add this line

192.168.0.55:/data/images /images2  nfs      defaults    0       0

• Reboot and check auto mount working (create a file or a directory as previous test from manual mount)

• Change owner of the /images2 directory with command

chown fogproject:root /images2

• Edit or add your storage on FOG GUI to use it.
  

• If you added a new storage node in the same storage group, you should see your images, dev and postdownloadscripts directories on NAS share after replication.
  

@Sebastian-Roth
I think to know what is blocking.
I have to change vlan and fog IP adress to make updates but it use IP parameter in the updateDB() function :

wget --no-check-certificate -qO - --post-data="confirm&fogverified" --no-proxy ${httpproto}://${ipaddress}${webroot}management/index.php?node=schema >>$error_log 2>&1

I think -X with help to finish install.

@Sebastian-Roth
Hi,
I have run

./installfog.sh -y

Here is what script says at the end :

* Updating Database...........................................Failed!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! The installer was not able to run all the way to the end as   !!
!! something has caused it to fail. The following few lines are  !!
!! from the error log file which might help us figure out what's !!
!! wrong. Please add this information when reporting an error.   !!
!! As well you might want to take a look at the full error log   !!
!! in /home/adminfog/fogproject/bin/error_logs/fog_error_1.6.0-alpha.1182.log !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

           ├─8301 php-fpm: pool www
           └─8302 php-fpm: pool www

mars 31 13:46:33 fogserver systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
mars 31 13:46:33 fogserver systemd[1]: Started The PHP 7.3 FastCGI Process Manager.

I have no request to update DB on GUI.
It directly go to the dashboard and GUI works well.

Hello,

I try to update to last dev version from 1.6.0-alpha.1133 but it stuck at “Updating Database”.
Last install error log is : Started The PHP 7.3 FastCGI Process Manager.

Any idea of what i can do to reach the end of the install script ?

Thank you.

@Hope1983

And for manual mount command used was :

mount ip_of_the_qnap:/Directory_of_the_qnap /fog_directory/

ex :

mount 192.168.0.2:/Images /images2/

I just tested on my QNAP.
I have allow write to my fogserver IP, mount and tested file creation and it works fine.
I can’t do more test (such as creating images folder to test deploy) since my fogserver is on private network that I can’t access from work network.

@axander
Hello,
it’s all write here : https://wiki.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options

Upload the iso on the server in somewhere in www directory.
Create new “Boot Menu Items” from GUI and add something like this as parameters :

initrd http://${fog-ip}/ISO/MultiBoot_2k10.ISO
chain memdisk iso raw

I have the same problem.
Any idea what is doing this ?
Could that check be disabled ?

I had to do quick registration and write down mac to change name and image on gui.