Selected boot device failed



  • Trying upload an image and keep getting the following error. I am using a dell branded usb to ethernet with a new Dell XPS 13.

    0_1515011320077_IMG_0830.JPG


  • Developer

    @sjensen said in Selected boot device failed:

    So basically i need to try the different bios setups combined with the different binaries in order to capture an Image of this Dell XPS13?

    As I said, it’s probably a lot easier than debugging why undionly.kpxe doesn’t work at all and undionly.kkpxe has transfer issues…

    So it’s all about the combination of Laptop, firmware and USB dongle. Here is a forum thread where someone was able to PXE boot in BIOS legacy (undionly.kpxe) with a USB dongle also based on the RTL8153 network chip. But as I said, it’s always a bit different as soon as you change one component in the equation.

    And here Dell is saying that “The XPS 13 with BIOS A05 or higher, supports PXE boot with LAN7500 chipset based USB NICs.”

    Just want to show you that there are many different ways and people were able to PXE boot the XPS13 but you can only know for sure when you test with the components you have at hand.

    Edit: Hope this is not causing too much confusion. Just wanted to show you that there are different solutions out there and trying to do plain UEFI might be the easiest one or at least worth a try. Here is a thread where the same issue as yours is described and was solved by switching to UEFI.



  • @sebastian-roth said in Selected boot device failed:

    ipxe.efi

    Thank you for setting me straight. You actually helped me solve another imaging issue, Microsoft Surface Pro’s need to use the .efi binaries.

    So basically i need to try the different bios setups combined with the different binaries in order to capture an Image of this Dell XPS13?


  • Developer

    @sjensen Please be careful with the wording. As far as I know there aren’t any “ipxe modes”. What I was talking about are what I’d call “firmware modes”. In the old days there was only BIOS or legacy BIOS as of now. Then came UEFI which is very different in many cases. Many (firmware) vendors thought it’d be to hard for people to go straight from BIOS to UEFI and so they invented CSM/BIOS compatibility mode in UEFI. That way you can still boot legacy BIOS systems from disk and via PXE while while the firmware is actually UEFI. This causes a lot of confusion, I know.

    So if you boot in legacy BIOS or BIOS compatibility mode your screen looks kind of like the pictures you posted. Most UEFI firmwares look very different to that on PXE booting. See the picture below.
    alt text

    So if you find the right firmware settings to switch to plain UEFI (every vendor/firmware is different and I can’t give you advice on where to find this) the boot screen should look more like on the picture I posted. If so you can use the iPXE binaries compiled for UEFI like ipxe.efi, snponly.efi, snp.efi, realtek.efi, any .efi binary really.



  • @sebastian-roth How long does it sit there loading the menu background image (bg.png)?? I let it sit for at least a 1/2 hour.

    Can you give the different ipxe modes? I am up for trying anything at this point


  • Developer

    @sjensen said in Selected boot device failed:

    This one is uefi boot with undionly.kkpxe as the dhcp config

    No definitely not! Probably this is CSM/BIOS compatibility mode. If you turn on real UEFI mode then only the *.efi iPXE binaries will work! You can’t use the undionly.kpxe (and all the others k/k/pxe) if your machine boots in full UEFI mode.

    I am not trying to confuse you here. Again, read through our wiki article on this: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

    Not saying that you have to go the UEFI way but it might be an option that could work out without much trouble (beside re-installing your client OS in UEFI mode).

    About the pictures. Yeah, this definitely got you hast the initial issue. How long does it sit there loading the menu background image (bg.png)?? Some USB NICs are just not playing nicely with iPXE and it costs a hell of a lot of time to debug and fix this (sometimes impossible as of buggy firmware). So the best you can do is try out all the different modes with different iPXE binaries and see which one works out of the box.



  • @sebastian-roth said in Selected boot device failed:

    realtek.kpxe

    Ok i tried switching between legacy and uefi boot modes, i got the same exact error as the picture above. I tried the different dhcp configs and the one that seems to get me closer to cloning is undionly.kkpxe. The screen shots both show it gets stuck at the same point.
    This screen shot is legacy boot with undionly.kkpxe as the dhcp config
    0_1515082389544_IMG_0838.JPG

    This one is uefi boot with undionly.kkpxe as the dhcp config
    0_1515082496254_IMG_0837.JPG


  • Developer

    @sjensen said in Selected boot device failed:

    If I have it in UEFI it does not boot into the os.

    Sure you can’t just switch between legacy BIOS and UEFI. You’d need to reinstall in UEFI mode. Just wanted to see if that could be an option.

    I also tried changing it to uefi just to capture the image and still get the same error.

    The exact same error? I am sure the screen looks different, it has to! Can you please try again and take a picture?

    Other than that you can try differnt iPXE binaries. In your DHCP server set filename to undionly.kkpxe (note the double k), ipxe.pxe, realtek.kpxe or realtek.kkpxe just to name a couple different ones you could try.



  • @sebastian-roth The only way the pc will boot into the OS is if I have legacy boot turned on. If I have it in UEFI it does not boot into the os. I also tried changing it to uefi just to capture the image and still get the same error.

    The way I am attempting to capture this image is no different than what I have done many times before. I am at a loss here.


  • Developer

    @sjensen said in Selected boot device failed:

    That’s the only way the pc will boot.

    What do you mean by that? What happens if you switch to UEFI? What does serve DHCP in your network? Maybe you can’t do UEFI PXE boot because nothing is serving the correct binary?! See here: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence



  • @sebastian-roth System bios is the latest, secure boot is disabled, as far as legacy boot vs UEFI. That’s the only way the pc will boot. We do not have WDS/SCCM on our network.



  • @wayne-workman fog version 1.5.0-rc-10 Dell model #dbjbcbc064


  • Developer

    @sjensen To add to Waynes important questions:

    • System seems to boot in legacy BIOS mode. Why not going UEFI?
    • BIOS firmware is the latest? Please upgrade if not.
    • Is secure boot disabled?

    The error message is kind of new to me. Seems like this is happening inn the middle of iPXE init. But searching for pxe "selected boot device failed" on the web I found a lot of WDS/SCCM posts. Do you have something like that in place?



  • @sjensen Two questions initially:

    • What version of FOG are you using?
    • Any model numbers at all on the USB to Ethernet dongle?

 

533
Online

41.8k
Users

12.3k
Topics

116.1k
Posts