Imposible to boot from hard drive
-
My bad … Doesn’t working with ‘Sanboot’, true !
But with ‘First HDD it’s ok’.
I have other model : Motherboard ASUS A58M-E : imposible to boot (Win 8.1/10).
-
@aksl said in Imposible to boot from hard drive:
Dell Optiplex 3020M.
I think I asked this before, but is the 3020M configured in uefi mode? Its important to know because uefi systems need a different exit mode than bios (legacy) mode. For uefi mode systems you should use the exit mode of rEFInd, sanboot is for bios(legacy) mode systems.
-
New windows 10 (legacy) is ok …
Windows 10 UEFI, imposible.
Regardless of the exit mode.
-
No solutions ?
Sorry
-
@aksl The things you posted are a bit mixed up. This way we won’t get any further I am afraid. So same question again. Is this happening on one single PC or several ones? All the same model/vendor or different ones? Please post a proper list of the PC you tested this on, like this:
- Dell Optiplex 3020M - UEFI - exit type: rEFInd - hangs on black screen
- …
-
Thanks for your help.
In fact, it’s simple.
For all PCs with Legacy mode, it’s working.
For all PCs with UEFI mode, isn’t working (tried all exit mode).
Windows 7, 8 & 10 !
-
@aksl For uefi, rEFInd is really your best option. Make sure you have the exit mode for the specific computer and uefi set to rEFInd and then lets tell refind to look in more places for a boot drive.
- On the fog server from a linux console prompt edit the following file:
/var/www/html/fog/service/ipxe/refind.conf - Search for the line
scanfor internaland comment it out to look like this
#scanfor internal- Search for the line
#scanfor internal,hdbios,external,biosexternaland uncomment it to look like this
scanfor internal,hdbios,external,biosexternal- Save and exit the editor.
- Now pxe boot the uefi system and see if that mode finds the hard drive.
rEFInd “should” find the boot disk if it’s installed.
- On the fog server from a linux console prompt edit the following file:
-
And as well, while you edit
/var/www/html/fog/service/ipxe/refind.confset the optiontimeoutto zero. Then it would show you another boot selection menu. So hopefully we will see anything on screen at least.@aksl said:
For all PCs with Legacy mode, it’s working.
For all PCs with UEFI mode, isn’t working (tried all exit mode).
Windows 7, 8 & 10 !Have you actually installed those systems in UEFI mode? It’s very different to install windows in legacy BIOS mode and then just switch over to UEFI later on.
-
Hi,
I edited the refind.conf and timeout is now zero.
I don’t see any difference in the boot menu.
Do I have to press a key ?
Currently functioning as before.
Thanks
-
@aksl Did you also change the things in refind.conf George suggested? See his post a little further down.
-
Oh, I had not seen sorry.
But I tested and finally it’s the same problem.
Always this line which flashes in the top left.
With your different shifts, I have not seen any behavior changes in the boot menu.
I don’t know what to do …;
Thanks
-
@aksl Secure boot is disabled I suppose?!
-
Yea … disabled
-
To your mind, the problem is FOG or my bios setup ?
-
@aksl said in Imposible to boot from hard drive:
To your mind, the problem is FOG or my bios setup ?
Well, I am still not quite sure. We have hundreds of users and almost no one reporting an issue with chainloading windows.
Please do me a favour, take one of these PCs where you see the issue, pop in a windows install CD and boot from it. For that change boot order to CD, HD, PXE and make sure to not change anything except boot order!!! Let it install completely, finish the initial setup, remove CD and then change boot order to PXE, HD, CD. Big question now: Does chainloading windows from the FOG menu fail again (should be a machine/BIOS issue) or does it chainload properly (tells us we have a FOG/iPXE issue I suppose.
Note down the result and do the reverse test now. Leave BIOS settings as is and let it deploy your image you had the issue with before. Then try chainloading from the FOG menu to windows again.I know this sounds a lot of pain but I ask you to give it a go to proove what is wrong here. Do it exactly as described, don’t try to be smart and use another PC to make this go faster or anything.
By the way, is this a resizable image type or non-resizable one?
-
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.
-
@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?
-
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
-
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 ?
-
@aksl said in Imposible to boot from hard drive:
UEFI 32 bit file name : ipxe32.efi
UEFI 64 bit file name : ipxe64.efiWhat 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
