Chainloading Failed on EXIT - Hangs on REFIND_EFI

[88fingerslukee]

Okay, so totally weird. It must’ve worked at some point because I had to leave for a while but when I came back it was at the linux prompt. Here’s the lsblk command, sda is the system SSD.

NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sdb       8:16    0   298.1G  0 disk
└─sdb1    8:17    0   298.1G 0 part
  sda      8:0   0   238.5G  0 disk
└─sda4    8:4   0    238G   0 part
└─sda2    8:2   0   100M  0 part
└─sda3    8:3   0   128M  0 part
└─sda1    8:1   0   300M   0 part

When I rebooted it went back to the open timeout. So I have no idea what the deal is here.

[Tom Elliott]

@88fingerslukee do you use the location plugin by chance? RC-26 fixed an issue of a method call, of which the sounds like it’s failing rc25 s bug.

[88fingerslukee]

Unfortunately, no. I don’t use any plugins at all.

[Tom Elliott]

@88fingerslukee then are there any errors that might seem relevant in the Apache error logs?

[88fingerslukee]

@Tom-Elliott no error logs at all. I only have ssl_error_log or access_log. Neither of them have anything relevant.

[Tom Elliott]

Also, another possibility, for the open timeout isn’t because of a problem with the exit type, rather how it’s being told to pass the exit based on how the system is seen. For example booting something in legacy mode would, from what I can guess, would not be able to return the UEFI based data to the system.
It suddenly thinks there’s no os to load into and restarts the system to try again. I believe you can boot down though (from EFI to legacy), just as long as the data can be found to boot up.

[88fingerslukee]

@Tom-Elliott the BIOS has two different network boots, iPXE and Legacy LAN. Both of them exhibit the same behaviour

[Tom Elliott]

@88fingerslukee if your system is expecting to boot in UEFI, but your release from ipxe to system is in legacy it doesn’t matter which form of pxe on nic you’re using.

UEFI/EFI as far as I know uses the onboard ‘nvram’ to know how to boot the system but in legacy mode that element would not be accessible.

[88fingerslukee]

@Tom-Elliott I’m not certain I understand what you’re saying here. Are you suggesting an issue with the motherboard’s implementation of iPXE or something to do with FOG?

[sudburr]

@Tom-Elliott This depends on the motherboard / BIOS.

I have several models of Lenovo set to UEFI, but allow booting to both. I can drop a Legacy/CSM or UEFI image onto these systems and they will boot either OS fine.

In fact I just Legacy PXE booted an M73z with undionly.kpxe to transfer an OEM UEFI image. It transferred and booted fine and runs as a UEFI OS.

[JJ Fullmer]

@88fingerslukee In the bios/uefi firmware settings, what is the boot order?

i.e and or also…

Is UEFI enabled and Legacy enabled, or just UEFI?
What pxe boot file are you using? I’ve seen that make a difference. I haves some cheaper HP’s that won’t boot with sanboot to the hard drive if you use ipxe.kkpxe, but they work fine with ipxe.pxe or ipxe.kpxe.

Also have you played with the refind boot settings? There’s a file on the fog server at
/var/www/fog/service/ipxe/refind.conf
there is a line that starts with scanfor I’ve changed mine to only look for internal,external which means it only looks for uefi options and not legacy options. On a few of my devices, if I have it set as uefi only it has a pause on the host every boot if UEFI CSM isn’t set and it searches for the bios options that are enabled in fog by default.