Imposible to boot from hard drive

[aksl]

Hello,

Does chainloading windows from the FOG menu fail again (should be a machine/BIOS issue) : yes.

But I have this concern from the beginning. It is not on a restored image but on a direct installation.

[Sebastian Roth]

@aksl So Chainloading from the FOG menu to disk (windows) has never ever worked for you in UEFI mode on Dell Optiplex 3020M and Motherboard ASUS A58M-E?! Not even when installing the OS by hand. Do I get this right?

[aksl]

Hello,

I just tested on a laptop ASUS (uefi) and it works!

Which means that it comes from the computer or the bios.

J’ai essayé toutes les configurations possibles du bios mais impossible.

Thanks

[aksl]

Informations :

My DHCP : Default bios file name : undionly.kpxe

UEFI 32 bit file name : ipxe32.efi

UEFI 64 bit file name : ipxe64.efi

posible Kernel problem ?

[george1421]

@aksl said in Imposible to boot from hard drive:

UEFI 32 bit file name : ipxe32.efi
UEFI 64 bit file name : ipxe64.efi

What is this? These are not standard FOG boot file names. For x64 the boot file should be ipxe.efi. And for x86 the boot file should: i386-efi/ipxe.efi

[aksl]

Modified, but this is not the problem.

Is it possible that it can not work with this motherboard?

[Sebastian Roth]

@aksl said in Imposible to boot from hard drive:

Is it possible that it can not work with this motherboard?

Definitely possible. We have seen buggy UEFI firmware that wasn’t able to chainload the linux kernel so it is also possible to see issues with chainloading to rEFInd on some crappy firmware. This just sparked an idea… Are you able to deploy/capture from those PCs that have an issue with chainloading? I suspect rEFInd and linux kernel just being EFI stub binaries and should actually show the same behavior (hang). Can you confirm?

[aksl]

I am able to capture image from this PC.

[Sebastian Roth]

@aksl said in Imposible to boot from hard drive:

I am able to capture image from this PC.

Ok then we need to go dive into the ugly underworld of UEFI… Download 03_ipxe.efi here and put it into /tftpboot folder on your FOG server. Rename the original ipxe.efi and name that new one like this so clients will use this for booting. This should give is some debugging output on where it hangs. Just take a picture of the hanging screen and post here.

[aksl]

I feel like it’s like before.

I do not see a debug.

This is my pfSense - DHCP server config : is it correct for the boot?

[george1421]

@aksl

1. As long as next server points to your fog server that field is correct.
2. The BIOS name is correct.
3. You should probably add in uefi 32 bit of i386-efi/ipxe.efi
4. And finally uefi 64 of ipxe.efi

[aksl]

Then, the problem is the same.

Always this stroke that flashes at the top left.

Nothing displayed on the screen.

Or it is the messages before the boot menu ?

[Sebastian Roth]

@aksl Reading your earlier message I had the impression that you were in UEFI mode not legacy BIOS… For that I need to compile a different debug enabled binary. Did you change from UEFI to legacy BIOS or what?

[aksl]

No, i’m in UEFI mode.

[Tom Elliott]

What is “last” version?

[aksl]

@tom-elliott last version of what ?

[george1421]

@aksl Just interested to know if the 3020M, since you are in uefi mode, what is the disk configured as? Is it achi or raid mode? There IS an issue with linux and uefi and raid-on mode with most hardwares.

[aksl]

I can’t test with 3020M because there is not UEFI, just Legacy. I can’t format it actually. I can just play with the ASUS motherboard.

[Tom Elliott]

Last version of FOG? Per the posting we still don’t know what version of fog you’re actually running, we just know it’s Last, whatever that means.

[aksl]

Running version : 1.4.4