@Small0145 No, it’s not.

@george1421 said in [BUG] iPXE Boot Loop & Menu Failure After FOG 1.5.10.1660 Upgrade:

If undionly.kpxe worked in bios mode then snp.efi should work in uefi mode

Hi George, the BIOS claims its in UEFI mode but when booting it looks suspiciously like legacy (larger text etc). Its an old Viglin with a second generation i3 which is being retired this October so its not too much of a deal now I have a workaround.

@aurfalien said in Mellanox ConnectX 3 imaging issues.:

So all good here.

Did FOS Linux have the driver enabled for that 10GbE card (i.e. were you able to image with FOG once you got past the iPXE menu)?

FWIW: For uefi mode snp.efi or snponly.efi should work if undionly.kpxe worked in bios mode. I’m saying it should because ConnectX3 is a somewhat older card (circa 2017/2018).

@punch07 to view the /tftpboot use the command line terminal window. Now I do have to say that different distros have the directory in different locations like /var/lib/tftpboot.

@Eazis I created an experimental kernel that includes the drivers to fix this issue. Would you be willing to test it and let us know how it goes?

There is a BIOS update for the MiniX PCs that allows the PCs to be built from FOG 1.5.4 running on CentOS 7.5.2009.

I do not know the technicalities but upgrading from verion 6 to 8, was mentioned.

@george1421 This worked! Thank you so much for your help!

@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.

@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.

Greetings.
Same issues here with a LENOVO 50S, realteck chipset.
I’va speed of 9 Gbit/min on capture and 0.6 Gbits/min on deploy.
Debian Fog Server, version 1.5.10.1660, latest and beta kernel : same issue.
Do a bunch of test with an another hard disk, new kernel, same issue.

I tested with 5.15.68 kernel and my download speed go from 0.6 Gib/min to 4.5 Gbib/min !