@jmeyer Make sure you are paying attention to MB/s and Mb/s. It goes without saying there is a difference.

I wrote an article about 8 years ago now. https://forums.fogproject.org/topic/10459/can-you-make-fog-imaging-go-fast

This contained some benchmarks I did at the time. FOG imaging speed is (according to Partclone) is made up of several elements. FOG Server disk subsystem speed, the speed at which the fog server and move the image from the disk to network interface, network transfer time, the client receiving the file and expanding it in memory, and finally the client moving the data to local storage. All of those go into the number displayed by partclone.

For clarity let me present some theoretical best network speeds.

For a 100Mb/s network link the maximum transfer speed is 12.5MB/s or 750MB/m
For a 1GbE network link the maximum transfer speed is 125MB/s or or 7.5GB/m
For a 10GbE network link the maximum transfer speed is 1250MB/s

Pay attention if your network speed is getting capped at or around one of the maximum transfer speeds. I’ve seen someone in the past only get 8MB/s transfer rate. He/she had 1GbE on each end, but between the ends there was a network switch link that was running in 100Mb/s half duplex. Not saying that is your case, but stuff happens.

Now why I referenced that article above. It has the commands to benchmark your hardware. iperf3 will give you network speeds between the network interfaces and the kernel. It has nothing to do with moving fog image blocks between systems. If you put the FOS target system in debug mode you can run iperf3 between FOS Linux and the FOG server. This will give you an idea of the bandwidth you have. I would do this with a computer that is exhibiting the slow imaging speed and then one that has normal imaging speed. Lets see if the network speeds are compatible. I’m not willing to rule out is the linux kernel version 6.1.x vs 6.6.x it maybe there is something that is missing in FOS linux for this new hardware.

When you have the slow target computer in debug mode run this command to see if the kernel is complaining about the hardware/firmware. grep -i -e "firm" /var/log/syslog That should return any lines that complain about needing special firmware for the hardware.

@jmeyer said in what USB can support iPXE boot:

Do you mean using brand adapteur certified for PXE such as :

Exactly. They have to say pxe boot and then be branded to the device manufacturer. UEFI firmware is not like linux (well it is minux/linux) but in a general purpose linux it has one of every common driver, where uefi only needs drivers for the hardware actually installed in the device, there is no need for a 3com isa driver in a Dell laptop with a 14 gen processor (contrasting something really old with something new).

Typically if the uefi bios sees a uefi compatible nic adapter in the computer, the F12/boot manager will list pxe booting as an option. If its not listed then the network device is not supported by the uefi firmware.

@Tom-Elliott i’m on 1.5.10.1622 version

And little bit same @Nicolas-Bricet

[Fri Nov 08 15:34:56.324018 2024] [proxy_fcgi:error] [pid 358511:tid 358511] [client 192.168.100.1:50111] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught ValueError: max(): Argument #1 ($value) must contain at least one element in /var/www/html/fog/lib/fog/hostmanager.class.php:225\nStack trace:\n#0 /var/www/html/fog/lib/fog/hostmanager.class.php(225): max()\n#1 /var/www/html/fog/lib/fog/fogpage.class.php(4075): HostManager->getHostByMacAddresses()\n#2 /var/www/html/fog/lib/fog/fogpagemanager.class.php(220): FOGPage->importPost()\n#3 /var/www/html/fog/management/index.php(58): FOGPageManager->render()\n#4 {main}\n thrown in /var/www/html/fog/lib/fog/hostmanager.class.php on line 225’, referer: https://fog.deploy.com/management/index.php?node=host&sub=import

In my CSV i have 100 lines but only 8 first lines add in hosts

@davidsontiago If you are using sysprep, include the command line option to tell sysprep to power off the computer. You have this message because when you pick shutdown from the menu, windows doesn’t actually shutdown the computer but put it into a sleep state leaving some files open that FOG sees. Sysprep will power off the computer correctly for cloning or use the following command “shutdown -s -t 0” to properly power off the source computer and close all open files.

@kotson3 But you’re not attempting FTP to 10.234.90.212. you seem to be attempting to FTP (in the cli) to 127.0.0.1 or localhost. From what I can tell, your FTP instance isn’t passing over the 10.234.90.212 point.

@Tom-Elliott okay, i’ll do that.

(idk how to mark the topic as solved)

@NoIPName

I found a solution for this problem:

Apache2 dont care which SSL certificat you use, so you can use another path for your Custom CA on the website
So logicaly you can keep your intern Fog certificat and dont change it :

/var/www/html/fog/management/other/ca.cert.pem /var/www/html/fog/management/other/ssl/srvpublic.crt /opt/fog/snapins/ssl/.srvprivate.key

But you need to recompile the iPXE file for the boot PXE

After that you can check with your fog-client can comunicate with Fog server 😄

@Small0145 said in Client registration error:

il y a environ 18 minutes

@kelocktnt look in “Pending Hosts” on the hosts page. It should be the

OMG !!!
i’ve been walking past it since the beginning without seeing it!!! too newbiees

Thank youu @)

@dtiganas Did you get anywhere with this? I’m having the same issue on our machines and am getting no where with fixing it…

In case anyone else is experiencing the same issue, I figured this one out.
routeraddress was missing in .fogsettings

cd /opt/fog vim .fogsettings

enter router/default gateway IP between single quotes

routeraddress='192.168.1.1'

reboot server.

@Jim-Graczyk

The wiki on migration covers migrating a single FOG server using the only workable process, so I’ll leave that alone.

I think my issue with the entire “Server Migration” process is that it requires you take FOG down at the onset of the process - before you attempt to install FOG on the new server. This obviously stops all the PC IT maintenance processes FOG provides IT support, but also FOG’s benefits to the end users of the hosts, until the new server/system is back up and working.

I’ve used FOG on a fairly large scale - some instances have 10+ remote sites, each with its own FOG Storage Node. To say that shutting it down before starting migration is inconvenient to the business is an understatement. Storage node migration didn’t require that the storage node had use the same IP as the old storage node - so that helped.

I hope that my initial post to you comes up when other FOG users search “FOG Migration”, so they don’t waste the time I did trying to build a completely new FOG system, including storage nodes, to cut over to, only to find that you can image PCs and create new hosts, but the exiting host would not talk to the new server system - so all the existing host configuration is lost (a large chunk of work). Ironically, there are numerous FOG wikis that address most issues that I ran into - creating new certs, the ever-present Reset Encryption on the FOG Client, etc., but none mentioned that the CA of the old system HAD to be used in place of the new.

I’m glad there was some way forward without having to reconfigure everything manually, but like many things in FOG wikis, everything in them is true, but context and limitations are not defined at the beginning. Even the migration process link didn’t spell out requirements, nor include remote sites and storage nodes. It needs to spell out that harvesting the CA and certs and using the old server’s IP address are as important as the database, snapins, and images - and this is the ONLY way to migrate.

So - a suggestion to the great minds working on FOG:

Create a way to change the FOG Client CA in one step - delete old and replace new - from within the FOG Client. This could be something issued from the old FOG server, for security reasons. CA deletion should also be built into the FOG Client Installation MSI/EXE. I use FOG to build portable Windows images that are company and FOG server independent. The FOG client is installed at the initial boot and replaced in the image as FOG evolves.

If that capability could be added, migration would be possible such that the new system w database, snapins, images, host configs, could be build out with multi-storage nodes and multi-locations, side-by-side with the old FOG system, gated only by DHCP boot settings at each site (IP broadcast space).

Jim Graczyk

@george1421 Thanks! I wonder if a chat bot could help with reading through what worked and make a tutorial.

My good, i found it !!!

i the default.ipxe i change the value for my FQDN of my DNS and that work’s !!!

i lost 2 days with this issue :V thanks you !

@Tom-Elliott Success. I switched to single-user with init 1, and installing systemd-sysv worked fine.

As this is a machine upgraded from debian 11, maybe it wasn’t using systemd. Installation of 1.6 worked no problem Thanks,