Boot loop after imaging UEFI
-
@jemerson93 said in Boot loop after imaging UEFI:
Believe all laptops being affected are M2 SSD’s. Unsure if they are nvme.
Then it may be that there is something wrong with the imaging process - it may be that the exit types are working fine but the local disk simply isn’t bootable. Are there any errors during image capture or deploy?
-
@wayne-workman I do not notice any errors during capture or deploy.
-
@wayne-workman curiosity question as I was doing some more research. My current image I’m testing is formatted as a MBR partition. I read that UEFI needs to be formatted as GPT to be bootable. I just created a VM (using Proxmox) as UEFI bios and converted it to GPT. Going to upload it to Fog in the am. Think that could deal with the REFIND loop?
-
@jemerson93 If the image was captured/deployed to a disk in MBR format, UEFI would indeed not find the drive as the disks MUST be in GPT format.
-
@tom-elliott Thank you for the clarification. I will finish uploading the image in the morning and post an update.
-
As an update, after creating a GPT partitioned image and uploading it to FOG, the image will successfully boot.
The only issue I have now is that I still receive the REFIND menu. It allows me to boot into the OS afterwards, but each time it boots (unless I disable network boot), it will go into the REFIND menu. Is there a way to either, edit the conf file to not display REFIND or to fix the issue with it not detected a CSM?
I have not tried other exit types after fixing the image so if this is how REFIND will be, I can re-attempt other exit methods.
On a side note, thank you to everyone for the assistance. I did not even realize that UEFI used GPT partitions to boot.
-
@Tom-Elliott
After some more troubleshooting I am still stuck on trying to skip the REFIND screen. I will have some screenshots below. I’ve attempted to remove all scanfor BIOS options from refind.conf with no luck. If I enter any key, I can boot to the OS. I’m trying to find how to remove this scan as I’m trying to make the UEFI imaging as automated as the BIOS imaging. Images below…After imaging
After inputting any key
-
Trying to remove the need to hit any key to continue. I know this is technically a different issue now, if I need to open a new post, I understand.
-
@jemerson93 Have you played with rEFInd’s
timeoutoption yet? -
@sebastian-roth Yes, I did.
As another update, I spent this weekend editing rEFInd’s timeout, scanfor, and a few other settings I found browsing the forums and this morning I have successfully imaged 2 computers with my new UEFI image and did not receive rEFInd pop up at all. After it completed imaging, it booted straight into the OS.
Safe to say this has been solved. Thank you to everyone for the assistance. It is greatly appreciated!
-
@jemerson93 Would you please provide what you did to resolve this issue?
-
@quinniedid Sure!
Base steps were I created a new image in GPT format.
Afterwards, on the FOG server itself I edited the config file located at /var/www/fog/service/ipxe/refind.conf
Below are what I have the values at. This was after some troubleshooting so some may be back to their default values.
timeout -1
scanfor internal,external (I also have both lines commented out at the moment)
uefi_deep_legacy_scan is uncommented
scan_delay 5From my memory that is all that is changed. After the imaging is completed in UEFI, it will boot straight to the OS instead of pushing itself through FOG and/or rEFInd.
Hope this works for you!
