HP EliteBook 840 G7 stuck at "rEFInd - Initializing..."
-
-
Started today with rEFInd Version 0.11.04, scanfor set to manual, menuentry for Windows. LT would get to a rEFInd menu, but would fail to load Windows.
Error: Not Found while loading bootmgfw.efi. -
Changed to rEFInd Version 0.12.0. LT got stuck at rEFInd - Initializing…
-
Edited refind.conf to scanfor netboot, internal and disabled manual menu entry. LT got stuck at rEFInd - Initializing…
-
Edited boot order of LT to boot to disk first and it loaded the OS.
There seems to be an issue going from pxe boot to hard disk. Once the network boot times out and tries to boot to the hard disk it encounters difficulty at the rEFInd stage.
-
-
@tech04 Have you tried adjusting the scan_delay?
It really feels like refind cannot find the drives. So if it’s set to 0 the and doesn’t find anything, how would it get past initializing?
I could be wrong of course. I’m not seeing all the differences.
-
@tom-elliott Yes, I have the scan_delay set to 5. Timeout is also set to 5.
-
@tech04 Okay,
So there’s 2 main efforts for EFI booting that you could attempt:
- rEFInd - which isn’t working. Maybe you can try v10.9, not sure if you tried all three versions?
- Try setting the machine’s Host exit type to Exit? Specifically the EFI exit type?
-
@tom-elliott Some further testing:
-
Changed to rEFInd Version 10.9. The rEFInd - Initializing screen came up, but then said Scanning for boot loaders; please wait… LT stayed at this screen.
-
Changed Host EFI Exit Type for this host to EXIT. Got message
Chainloading failed, hit ‘s’ for the iPXE shell; reboot in 10 seconds.
Device would reboot, then do it all over again. -
Changed to rEFInd Version 11.0. Still got the ‘Chainloading…’ message.
-
Turned off EXIT for the host. The rEFInd - Initializing screen came up and went to a ‘Scanning for boot loaders; please wait…’ message. It stayed there.
rEFInd just does not want to load Windows for some reason. I saw this thread which referenced a comment on Reddit that non-signed kernels have trouble chainloading to a signed Windows kernel.
Could this be the issue I am dealing with? If so, what can I do to resolve this?
-
-
@tech04 If secure boot is disabled on the machine, maybe re-enable it now that imaging is done?
-
@tom-elliott Interesting…enabling Secure Boot did in fact cause the computer to boot to the Windows OS. But it bypassed the FOG menu. It downloaded the NBP successfully, but then loaded Windows.
Disabling Secure Boot caused it to once again boot to the FOG menu, which then timed out, and then hit the rEFInd snag.
Is this model of hardware unable to boot to the FOG server, timeout, and then load Windows?
At this point, it seems it can do either Windows or FOG, but not both together.
-
@tech04 Were you able to figure this out?
I’m having the same issue with an HP 450 G7. Tried all the exit types.
I can pxe and image fine but it will not boot to Windows unless I have HD set as first boot.
-
@rankinc Seems like HP systems are a pain when it comes to chainloading the OS from disk. Can you try different versions of rEFInd to see if maybe the newest one works with your device.
-
@sebastian-roth Well I tried a few versions and ultimately I copied the original refind.efi to be refind_x64.efi and it is working…? the v12, v12 _x64.efis were not working so I just threw something at the wall. going to test some other models that previously worked to see if I broke them.
-
@rankinc We might have a hint for you which @RobertD posted just an hour ago: https://forums.fogproject.org/post/141591
-
Also I have this rEFInd hangup screen… there are a solution? hw Is a hp all-in-one the temporary solution Is to Press f9 at boot to start via pxe so if hard disk Is the First start option in BIOS list Windows starts up normally, but Is Crazy pressing f9 Every time when you have to do a multicast session of 20-30 PC…