@george1421

Hi Thanks for this informations, I maked the change but do you know if we can bypass the “press any key to continue” in rEFInd?

Thanks for your help

@yeet said in Error with UEFI:

Just two points to clarify here.

I’ve stopped using ipxe.efi altogether, since snp.efi seems to cover all of the devices I end up imaging.

snponly.efi for uefi is roughly equivalent to what undionly.kpxe is to bios. Both of these ipxe boot loaders use the network adapter’s built in firmware driver. For bios, the undi firmware interface is very mature and stable. For uefi the snp firmware interface has been historically very flaky until the last few years where it has matured a bit and become more stable. For both the undi and snp firmware drivers, its up to the nic manufacturer to make sure the firmware driver conforms to the strict standards. This doesn’t always happen.

Now ipxe.kpxe is to bios what ipxe.efi is to uefi. In the case of these boot loaders these are more like a linux kernel than not. These boot loaders have one of every known driver installed. The complete network and disk drivers are part of this boot loader kernel. The benefits are that ipxe has a very stable and known network and disk controller communication. The down side is that its sometimes difficult to keep up with emerging hardware. That is where undi and snp firmware drivers have helped since they are created by the hardware manufacturer when the new hardware is released. If the developers find that many people are having success with the snponly.efi drivers, they may change their default recommendations.

If that doesn’t work, I’d recommend updating the kernel version.

Don’t confuse the ipxe menu and the boot loader from the FOS Linux kernel. They are two different systems that work together. iPXE gets you to the FOG menu on the target computer. Once you select a menu item and bzImage is loaded then its FOS linux in charge. If you are having network issues and don’t get to the FOG iPXE menu then its a ipxe boot loader issue, if you get to the menu but when you select a menu item then see a network issue then its FOS Linux with the problem. I said all of that to say, if iPXE will not initalize then updating your {FOS Linux} kernel will not help you.

@sebastian-roth
indeed, I switched the fog server on the same network it works now
thank you

https://www.stellarinfo.com/article/repair-mysql-database-table.php

@walyson621 Please post the contents of the text files d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions of this image here in the forums. Find those files in the /images/OPTIPLEX3000/ directory on your FOG server.

I would like to update this thread, we found that the problem was with the DHCP Lease for some reason. We cleared the lease and now it is booting normally. It was very odd that this was an issue because we pulled another of the same machine from the box and it worked without any problems.

@JJ-Fullmer Just stumbled upon this again. Added a hint in the web UI (ref).

You might also add this to the documentation. Although when I looked into adding the hint to working-1.6 as well I saw that with the new web UI you actually have a checkbox for file deletion on deletemulti as well as single delete. So it’s only for FOG 1.5.x.

@joez455 normally yes, but I’m not going to guarantee it as I can’t know every case. I would highly suggest backing up the images folder, the /opt/fog folder, and a backup of the current database. Just to be safe of course.

@george1421
Thank you George, I’ll give it a go! Appreciate it.

@george1421 : Thank a lot for your fast && accurate answer. Have a nice day !

Did you ever find a fix for this issue? I have the same problem. I have a work around but its not really a fix for sure. If I use an external usb-c nic dongle it images fine, but this for sure is not a long term solution. If you ever figured this out i would be glad to hear how.

Thanks

@tom-elliott Excellent, thanks for your time.

@BrentC Probably the HDD you captured from is larger than the SSD you want to deploy to, right? What size are they each?

Please post the contents of the text file /images/LeahHolland/d1.minimum.partitions here in the forums. It contains the partition layout and we’ll surely figure out why it doesn’t deploy.

@bmick10 said in Renaming Windows10 Device with Secure Boot:

So I can ping from Windows computer but not our fog server.

One final check is to use the windows computer to get the IP address of that registered computer. Ensure you can ping the IP address of that computer. If you can then the issue is…

You need to setup DNS resolution on the FOG server so that it resolves the computer name correctly. You do this through the /etc/resolve.conf file OR for the linux distro that you use, if you have the gui for the FOG server linux OS, then use the network manager to set the DNS server to the IP address of your Windows DNS server (typically your AD DC). Make sure the search domain is set to your AD domain (i.e. ad.bigco.com)

As far as Fog changing settings for UEFI may I ask how that could happen

FOG will not do that. It doesn’t touch UEFI settings. I’m just saying that is only one of the few ways to upset secure boot, well actually bit locker. Secure boot only deals with the OS starting up.

@tom-elliott Awesome, thanks very much for your help.

@scott-boucher what is and version? If it’s Ubuntu 16.04 I would suggest upgrading to a more recent version and trying again. Ubuntu 16.04 is out of support and likely is stuck using repo that is no longer supported on it.

@tom-elliott hard to say. Most PCs are left running so I wouldn’t know if they were woken up or not. I can try to find a couple more to monitor.

@sebastian-roth This works great, replaced xinit.xz and all successful now. Thanks!