FoG was running perfectly for years, as you may recall. The only recent changes are that we are no longer using Legacy Bios for the imaging - as we have added a secondary SSD drive (M.2 on SATA1) to the equation. However FoG was only sending the Primary image to SATA0 no matter what I put in FoG. However these same machines with a single standard Seagate 500gb drive in SATA0 was working fine under EUFI, both DEPLOY and CAPTURE. Ai recommended a change in the iPXE file, which started this whole nonsense. So this time we wiped the pxe files from TFTP and did a reinstall of FoG. Getting closer now, but still getting the same errors on the PXE screen.

Pretty much at my wit’s end here. I know were are close…

-J

@Jias94 Hey no worries, I’ve created that error a few times myself so I had a good idea where to look. I’m glad you have it sorted out and can get back to imaging.

@hariskar It looks like your root partition ‘/’ has 1.8T or 1800GB of space. The command I would have run is df -h to give you usage. but assuming that debian is less that 50GB you should have plenty of space to capture a modern computer with 50GB of data. Use single disk resizable to use zstd to compress that 50GB of data down even smaller.

What error message are you getting? A screen shot of the error might help set the context of the error.

@wamis let start by updating your fos linux kernel to something more modern. I think 6.8.86 may be the latest. FOG Settings->Kernel->update kernel. FOG 1.5.7 is old. Lets see if we can update the kernel without needing to update fog.

@Tom-Elliott

All 3 commands didn’t work.
Here is a output from /sbin/ip addr
I have also added a screenshot from my BIOS, i hope that helps
NOTE: the enp0s20f0u7 is a USB->NIC adapter i need this to go into the FOS kernel. So normally this USB->NIC adapter is not connected to the system.

Afbeelding van WhatsApp op 2025-06-13 om 16.28.10_f61de18b.jpg Afbeelding van WhatsApp op 2025-06-13 om 16.28.11_46943113.jpg

For the benefit of others, I had hoped that upgrading CentOS from 7.5.1804 to 7.9.2009 would add the network drivers for a MiniX PC with a RealTek network card but this was not to be.

We have thefore taken the hopefully working step of installing 1.5.10 from scratch on a new Ubuntu 24.04 LTS Hyper-V build.

It is hoped that this will work for us.

@pierre-baylet Bonjour, j’ai eu la meme erreur lors de la mise à jour en 1.5.10. J’ai aussi un storage node déporté sur un NAS Synology. J’avais une erreur après la capture, avec un “Update database failed”.
Il faut que tu refasses les permissions sur ton dossier images/dev sur ton FTP.

Pour mon syno j’ai fait la manip suivante :
depuis mon fog en ssh :
sudo mount -t nfs @IPNAS:/volume1/images /mnt
chown -R root:users /mnt/dev
chmod g+s /mnt/dev

@Clebboii Thank you for your comments. I’m following up on your responses below.

It looks like MAC Passthrough is only a thing on Latitude, Precision, and XPS laptops. We utilize Latitudes. We do disable Secure Boot when trying to go into PXE boot. We’re going to try to set up a USB with WinPE to disable bitlocker. What confuses me is that the XPS had bitlocker get triggered when secure boot was off but still made it through PXE. It makes me think Bitlocker isn’t the issue here. The Dell USB-C to Ethernet does not support our Dell Inspirons. We tried an Anker USB-C hub with Ethernet and a usb-Ethernet TP-Link adapter on the Inspirons which didn’t give us the option to PXE boot. 66 and 67 weren’t set up when it worked on the ThinkPads or XPS. We set it up on our Firewall not our Router. It also worked after enabling. Going to look into this once our ThinkPad returns from being issued out as a loaner laptop.

Nevermind, looks like it was an error in the script itself.

@Itay1787 I just pushed a change to the dev-branch. Please try installing it again from there and let me know how it goes.