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

    PXE boot stuck on initialising devices

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    2
    6
    1.2k
    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.
    • B
      Baessens
      last edited by Baessens

      I have one FOG server; when i boot from network(legacy nic) on a Hyper-v server, i can’t seem to get past the “initialising devices…” screen.

      I have another FOG server in a different location that works fine on hyper-v, the difference being:

      • the version of FOG (fog1: 1.5.7 vs fog2: 1.5.5)
      • DHCP server is Unifi USG router(fog1), the other one uses Windows DHCP(fog2)

      On both DHCP servers i use undionly.kpxe as the boot file name.

      pxe.PNG

      EDIT: when i set the fog1 as boot server in dhcp option on my first location, it works just fine, so it would seem it has something to do with the VM on my other hyperv, so far the only difference is that the configuration version is 9.0, the other one is 8.0 … hm

      Any suggestions on how to troubleshoot this?

      Thanks in advance

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @Baessens
        last edited by

        @Baessens So the point at which its hanging is when iPXE is transferred to the target computer. Nothing else with FOG is in play at the moment.

        So it may be the version of undionly.kpxe that is working vs not working at the other location. Or the version of hypervisor being used.

        So a quick test would be to copy undionly.kpxe from a working site to a non-working site. The files are in /var/www/html/fog/service/ipxe directory. Lets start here and see what happens when the file is copied.

        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 1
        • B
          Baessens
          last edited by Baessens

          @george1421
          Fog that’s working
          fogworking.PNG

          Fog that’s not working
          fognotworking.PNG

          I do see some differences but i have no idea if they matter. i’ll try and copy the files tomrrow, thanks for the help already! 🙂

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @Baessens
            last edited by

            @Baessens Well I must have just had a senior moment. The pxe boot files you want are in /tftpboot The path I gave you was for FOS Linux. We are not that far yet. tftpboot is where iPXE boot loaders are.

            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!

            B 1 Reply Last reply Reply Quote 0
            • B
              Baessens @george1421
              last edited by

              @george1421

              Works:
              pxeworks.PNG

              Doesn’t work;
              pxenotworks.PNG

              The total is different and the rights on default.ipxe (3th row) different user aswell.

              Do you spot anything that’s obviously wrong?

              Thanks 🙂

              george1421G 1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @Baessens
                last edited by george1421

                @Baessens We there is nothing wrong with what there. What I see is a different version of undionly.kpxe for FOG 1.5.5 and 1.5.7. So the recommendation as a test take undionly.kpxe from the working FOG server and copy it over (renaming the original first) to the not working fog server then pxe boot.

                If the problem goes away on the not working fog server then the problem is with undionly.kpxe if the problem stays then its with the different version of hyper-v

                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

                195

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project