• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

UEFI can't PXE boot

Scheduled Pinned Locked Moved
FOG Problems
5
18
4.8k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Y
    YoshiDeOeuf
    last edited by Jun 8, 2021, 7:56 AM

    Hello,

    I have some Dell Latitude 5411 laptop to configure, so I try to use fog.
    I have an image on my fog server that I want to deploy, but I’m unable to boot with PXE from my physical machines, there is no legacy mode in the BIOS unfortunately.

    I put the right boot order in the BIOS and i enabled the UEFI network stack.

    I tried on older Dell Latitude (5440), and I’m able to boot with PXE if i put legacy mode, but not UEFI.

    I also enabled options 66 67 and 60 on the DHCP server.

    Thank you

    E 1 Reply Last reply Jun 8, 2021, 7:58 AM Reply Quote 0
    • E
      EduardoTSeoane @YoshiDeOeuf
      last edited by Jun 8, 2021, 7:58 AM

      @yoshideoeuf can you paste the error?, do you use a proxydhcp or a dhcpd server? have you configure de proxydhcp/dhcp server to provide de efi client? and are you using the correct client?

      Y 1 Reply Last reply Jun 8, 2021, 8:09 AM Reply Quote 0
      • Y
        YoshiDeOeuf @EduardoTSeoane
        last edited by Jun 8, 2021, 8:09 AM

        @eduardotseoane I get an “no bootable device found” error.
        I use a DHCP server (windows server 2012 R2)

        Here are my DHCP options : PXE.png

        Fog uses the 192.168.2.23, and my DHCP server is 192.168.2.5.

        E 1 Reply Last reply Jun 8, 2021, 8:31 AM Reply Quote 0
        • E
          EduardoTSeoane @YoshiDeOeuf
          last edited by Jun 8, 2021, 8:31 AM

          @yoshideoeuf undionly.kpxe is only for legacy clients, you must use one from *.efi collection on /tftpboot directory of the fogserver that is working as boot server, I dont know how to do it but maybe you mas configure the windows dhcp server to send different files, on arch dependant

          Maybe this links can help you…

          • https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence
          • https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
          Y 1 Reply Last reply Jun 8, 2021, 10:02 AM Reply Quote 0
          • Y
            YoshiDeOeuf @EduardoTSeoane
            last edited by Jun 8, 2021, 10:02 AM

            @eduardotseoane Yes, I already use ipxe.efi for UEFI, but it doesn’t work. Do I have to remove the undionly.kpxe ? Or maybe I just need to type /tftpboot/ipxe.efi instead of ipxe.efi ?

            E 1 Reply Last reply Jun 8, 2021, 10:46 AM Reply Quote 0
            • E
              EduardoTSeoane @YoshiDeOeuf
              last edited by EduardoTSeoane Jun 9, 2021, 2:00 AM Jun 8, 2021, 10:46 AM

              @yoshideoeuf NO, you must configure dhcp for UEFI/BIOS Coexistence, take care because efi clients don’t work on all machines, each machine type has his efi client, with NIC chip dependency, the same for legacy.

              I don’t work with Windows dhcp server, (are you using it?) so I don’t know how to do it exactly

              You must do that when client has UEFI archs send the correct efi file, filtering by Arch and by vendor…, when client has BIOS Archs, you must send the correctl legacy file, filtering by Arch and vendor too.

              Read the urls before posted with attention, i think that it has a how-to to solve your problem… with Windows 2012/2008 dhcp server, if it’s your case…

              Read this with attention, and if you can post a photo showing the error:

              https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

              Y 1 Reply Last reply Jun 9, 2021, 8:20 AM Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Jun 8, 2021, 5:01 PM

                @YoshiDeOeuf Your Windows DHCP config looks ok in first sight but there is more to it. I am not an expert in this but I do remember a topic here in the forums not too long ago where someone seemed to have the right settings but one final piece was still missing. Give the forum search a try or maybe @george1421 still remembers as He was the one who was able to help and fix the case back then.

                Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                G 1 Reply Last reply Jun 8, 2021, 8:39 PM Reply Quote 0
                • G
                  george1421 Moderator @Sebastian Roth
                  last edited by Jun 8, 2021, 8:39 PM

                  @sebastian-roth said in UEFI can't PXE boot:

                  but one final piece was still missing

                  The final bit was / for when the OP of that thread used the bios_and_uefi coexistence process he forgot to activate the policy. I don’t have a windows dhcp server in front of me, but there is a definite option to enable the policy or the scope. Once that was done then the dhcp server was dynamic in the boot file name according to the policy/rules.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  Y 1 Reply Last reply Jun 9, 2021, 8:22 AM Reply Quote 1
                  • S
                    Sebastian Roth Moderator
                    last edited by Jun 8, 2021, 9:34 PM

                    @george1421 Thanks!

                    @YoshiDeOeuf Just found it, find all the details on this story in this topic: https://forums.fogproject.org/topic/15102/uefi-bios-coexistence-help

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    1 Reply Last reply Reply Quote 0
                    • Y
                      YoshiDeOeuf @EduardoTSeoane
                      last edited by Jun 9, 2021, 8:20 AM

                      @eduardotseoane I already red these urls many times, and I use a Windows Server 2012 R2 as I said, maybe i need to put another .efi instead of ipxe.efi ?

                      1 Reply Last reply Reply Quote 0
                      • Y
                        YoshiDeOeuf @george1421
                        last edited by YoshiDeOeuf Jun 9, 2021, 2:24 AM Jun 9, 2021, 8:22 AM

                        @george1421 My policy is enabled : 894cbccb-bd80-4c65-817d-09760978000d-image.png

                        9d0c56fe-f569-46ba-aa6c-aa060cd2274a-image.png

                        I created this policy like in this tutorial : https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

                        1 Reply Last reply Reply Quote 0
                        • S
                          Sebastian Roth Moderator
                          last edited by Sebastian Roth Jun 9, 2021, 11:21 AM Jun 9, 2021, 5:17 PM

                          @yoshideoeuf said in UEFI can't PXE boot:

                          maybe i need to put another .efi instead of ipxe.efi ?

                          Well from your initial post it very much sounds like PXE boot for legacy BIOS machines work but not for UEFI mode ones in general. Sure there are some machines that don’t properly work with ipxe.efi but they usually still load it and then fail to get an IP via DHCP within iPXE or something like that.

                          Sure you can try snp.efi and snponly.efi but I doubt it will help in your case.

                          I get an “no bootable device found” error.

                          Do you see it trying to pull an IP and PXE information from the DHCP at all? Without knowing what stuff you actually see on screen it’s kind of hard to help.

                          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                          1 Reply Last reply Reply Quote 0
                          • Y
                            YoshiDeOeuf
                            last edited by Aug 11, 2021, 12:13 PM

                            Hello,

                            Back to this problem, so I followed the tutorial with UEFI PXE boot with options 60, 66 (fog IP) and 67 (ipxe.efi) as shown in my previous messages.

                            I took a screen of what I get on the computer i try to PXE boot.

                            PXE.jpg

                            192.168.3.1 is the IP of the computer.

                            Do you think he’s able to reach the fog server at least, or maybe the problem is the boot file ?

                            Thank you in advance

                            G 1 Reply Last reply Aug 11, 2021, 1:10 PM Reply Quote 0
                            • G
                              george1421 Moderator @YoshiDeOeuf
                              last edited by Aug 11, 2021, 1:10 PM

                              @yoshideoeuf This is saying the dhcp server did not send the boot file name or received a proper offer packet from the dhcp server. At this point its not a fog server issue, but communication between dhcp server and client computer.

                              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                              Y 1 Reply Last reply Aug 11, 2021, 3:36 PM Reply Quote 0
                              • Y
                                YoshiDeOeuf @george1421
                                last edited by Aug 11, 2021, 3:36 PM

                                @george1421 I can ping without problem the DHCP server from the computer client

                                P 1 Reply Last reply Aug 12, 2021, 7:01 AM Reply Quote 0
                                • P
                                  PeterL @YoshiDeOeuf
                                  last edited by Aug 12, 2021, 7:01 AM

                                  @yoshideoeuf

                                  What is the netmask of the DHCP server and the PXE client (considering the 192.168.2.x and 192.168.3.x addresses of your screenshots)?
                                  Asked in another way: is there a relay agent between the two?

                                  Also: is Secure Boot disabled on the client?

                                  Y 1 Reply Last reply Aug 12, 2021, 10:10 AM Reply Quote 1
                                  • Y
                                    YoshiDeOeuf @PeterL
                                    last edited by Aug 12, 2021, 10:10 AM

                                    @peterl it’s /24 for both

                                    george1421G 1 Reply Last reply Aug 12, 2021, 3:19 PM Reply Quote 0
                                    • george1421G
                                      george1421 Moderator @YoshiDeOeuf
                                      last edited by Aug 12, 2021, 3:19 PM

                                      @yoshideoeuf said in UEFI can't PXE boot:

                                      it’s /24 for both

                                      So do you have a dhcp helper service enabled on the router between .2.x and .3.x subnets?

                                      Do you have the dhcp option 66 and 67 filled out for both subnets?

                                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                      1 Reply Last reply Reply Quote 0
                                      • 1 / 1
                                      • First post
                                        Last post

                                      202

                                      Online

                                      12.0k

                                      Users

                                      17.3k

                                      Topics

                                      155.2k

                                      Posts
                                      Copyright © 2012-2024 FOG Project