@sebastian-roth said in Image capture: reading partition tables failed:

@david-burgess You might want to point to a specific Primary Disk within the host settings, e.g. /dev/sda

Thank you. This was the fix.

@jalilg said in Fujitsu Lifebook E5511 / Intel 11th Gen Boot Failure:

What do you mean with the firewall only supports static dhcp options

This is specific to how the value of dhcp option 67 is managed. It is static in the sense of you have to manually configure it to send out undionly.kpxe for bios computers and ipxe.efi if you want to boot uefi computers. That is a static text field.

When I refer to dynamic options, that means based on the pxe booting computer, if the computer is bios based then the dhcp server will send out undionly.kpxe name. If the computer is uefi based then it will send out ipxe.efi. Its dynamic from the perspective of the pxe booting computer.

If you had a windows 2012 or later or linux dhcp server you can enable policies to make dhcp option 67 specific to the pxe booting computer. If you are not using one of those dhcp servers and your dhcp server doesn’t support dynamic dhcp options then we can deploy dnsmasq to provide that dynamic info only. We find most dhcp servers running on routers or switches don’t support dynamic pxe booting, pfsense is one exception that does support it.

@abde No problem. I am happy to answer your questions, we just need to follow the guidance of the developers to keep one problem one thread policy.

@aheerds Glad you have it working. Just for clarity ipxe.efi/snp.efi/undionly.kpxe will get you to the FOG iPXE menu. Once you select a menu selection that’s when FOS Linux (a.k.a “the kernel”) takes over. Both (ipxe and FOS) will throw the “No configuration method succeeded”.

@sebastian-roth Issue hase been fixed by using the 5.15.19 kernel. Many thanks @george1421 and @Sebastian-Roth for the quick support.

We found the solution. For anyone having the same problem with a emmc G1J39E, use the kernel arguments

sdhci.debug_quirks=0x65168080

we found the answer right here

@lsathya I really think there is something up/wrong with this hardware that causes iPXE to hang.

We do have a fall back method to get these computers to image without pxe booting. You will lose some capabilities, but you will be able to image them. Read through this article. https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image Because of the way the forum works the first part is at the top of the thread and the subsequent parts are at the end of the thread. Read through the tutorial and understand what you need to do and the caveats by creating a USB Boot image for FOS Linux.

Also look in the FOG Forum chat bubble at the top for a few more hints.

@andy-morris said in Lenovo 14w Gen2:

I just got it going by using the Kernel bzImage-5.15.5 from the fogproject.org/kernels/ list. I will make it the default for bzImage.

Nice! You might even use the newer kernel from github I just compiled a week ago: https://github.com/FOGProject/fos/releases/tag/20220203

By the way, the pictures you posted show that you were using 4.19.x kernel earlier… 😉

@kweldon said in Issue with loading Fog image to HP AMD systems with Realtek PCIe GbE Family Controller.:

5.15.x development kernel fixed my issue

Nice. We’ll need to get 5.15.x into the main stream kernels now. It is very strange for the latest linux kernel to fix a very old network adapter running on new hardware.

Just be aware that if you update FOG it will replace bzImage with what ever is being currently distributing with FOG at the time.

When FOG 1.5.10 is released it will probably ship with 5.10.x series kernels unless we can get more fog admins to test 5.15.x series before FOG 1.5.10 is released later this spring.

@sebastian-roth Thank you very much for your help. Now it works 100%

@sebastian-roth I had to hand over the U7511 and i did test on another laptop [E5511] ; i’m going to test on another U7511 when i’ll receive a new one next week. I’ll get you in touch.

Thank you again for the good work you do !

@george1421 Thanks a lot. It was the router that has dhcp and i just turned off the dhcp it work well thanks a lot

@george1421

Le problème s’est résolu avec le bon pack de pilotes.
Reconnaissance du disque dur et pas de soucis avec le partionnement.
En gardant la même version de fog, c’est à dire en 1.5.5.

Merci pour les réponse.
Nous allons mettre notre serveur à jour pour les prochaines stations.

Thanks.

@franck said in ACER VERITON N4670GT:

that mean i have to put everyone of them in AHCI mode too before doing it

The short answer is yes. Now just be aware that switching from raid mode to ahci might cause the system to not boot if the previous mode was selected.

This issue is related to the intel rst adapter, uefi and linux kernel. Intel won’t release the intel raid driver to the linux community so there are no linux drivers to reach the disk. This is not specifically a FOG issue, but a linux/intel issue.

@slang said in Fujitsu A3510 PXE UEFI Boot:

10EC&DEV_8168&

Thank you for sharing your experiences here. For new hardware we are seeing that iPXE needs to be rebuilt with the latest code from the iPXE project (different from FOG Project). That program manages the iPXE menu. For FOG, you also need to make sure you update the FOS Linux kernel (FOG Web UI->FOG Configuration->Kernel update) to at least the 5.10.x version of the kernel. This will allow FOS Linux (the engine that clones hard drives) to support the latest hardware too.

One last bit of information, you might want to upgrade to the dev-branch of FOG to bring your fog install up to 1.5.9.114 to address an issue if you plan on cloning Windows 20H2 or later. Microsoft changed the disk structure that requires the upgrade to FOG.

I just found this thread whilst searching for the “Stuck on EFI Stub” error which I also have on a Lenovo V130-151KB Laptop.

I changed our dhcp boot option 67 to point at the ncm–ecm–axge.efi file.

This resulted in my being able to re-image a laptop with a broken LAN port via a Dell USB Lan adapter.

I hope this might be of use to fellow victims of Lenovo. 😀

@austinjt01 The error message in the pictures does not seem to be the same than the one you describe via text. Please be more specific on what exactly the issue is.

I’ve been having the same issue with the G8 ProBooks and have finally got one to image throught the NIC however I’ve been through many steps so I followed this guide
https://docs.fogproject.org/en/latest/reference/compile_ipxe_binaries.html
I then re-downloaded & re-installed FogProject from github.
PXE is noticably faster and so far so good.
Whether compiling and copying the ipxe worked or whether it was the re-install or a bit of both I cannot say.

@george1421 Thanks so much @george1421 ! That fixed my issue.

@TKurtz12 Ok, there you go. Found several topics on this issue:
https://forums.fogproject.org/topic/15779/deploy-image-menu-not-coming-up
https://forums.fogproject.org/topic/15778/hp-elitebook-840-g8
https://forums.fogproject.org/topic/15940/hp-probook-g8-issues-imaging
https://forums.fogproject.org/topic/15715/problem-i-can-t-restore-image-on-hp-probook-450-g8-650-g8-430-g8

Carefully read through all those and you’ll see that some people even contacted HP support on this already. But I don’t think we have any positive feedback from them yet.