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

    Stuck on iPXE Initializing Devices

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    12
    5.1k
    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.
    • Tom ElliottT
      Tom Elliott
      last edited by

      Can you try using the ipxe.pxe file? I’ve seen hp machines act wierd due to the kernel doing something with firmware on the nic, and windows doing something else. By using ipxe.pxe it helped fix that strange issue for me.

      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      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
      • J
        jclumbo33
        last edited by

        No luck with ipxe.pxe. Got the same result, stuck on initializing devices. Think downgrading the kernel would have any effect?

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

          @jclumbo33 two things.

          1. The kernel is not at issue just yet. This is in the iPXE realm. (ipxe starts the kernel [bzImage], but you need to see the iPXE FOG menu first).
          2. Test by starting the computer from a cold start not a reboot.

          I take it this computer is in legacy (bios) mode? Is the firmware up to date on this unit?

          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
          • J
            jclumbo33
            last edited by

            I’ve tested it from a cold boot with no success and on a few of the same machines that worked a month ago. Yes the machines are in legacy mode. I have not updated the firmware, could this be the issue even though it previously worked?

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

              @jclumbo33 What version of fog were you using 1 month ago?

              Sorry, second part. When you pxe boot a target computer it displays ipxe banner on that banner there is a hex code in square brackets. Can you post what that code is?

              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!

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

                @george1421 OK my memory is not so good, it was parentheses not squared brackets. In this case the number is 356f.

                0_1528131121427_pxe_boot.png

                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
                • J
                  jclumbo33
                  last edited by

                  I was on 1.5.2 when it last worked on those machines. I actually updated to 1.5.3 today to see if that would solve the issue, so it didn’t work on either version.

                  It doesn’t get to that point, it stops right before it. Here’s a screenshot of where is hangs:

                  0_1528133667001_20180604_132313.jpg

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

                    Interesting 2 months ago it worked and you were on 1.5.2 , and now it didn’t work, you upgraded to 1.5.3 and it still doesn’t work.

                    OK lets try rolling back undionly.kpxe back to 1.4.4 version.

                    On your FOG server change into /tftpboot
                    cd /tftpboot
                    Rename your existing undionly.kpxe to a save file.
                    sudo mv undionly.kpxe undionly.kpxe.sav
                    Now copy in the 1.4.4 undionly.kpxe into the /tftpboot directory. (look at your fog forum chat bubble)
                    Now ensure that you update your dhcp server to send out undionly.kpxe as the FOG boot file.

                    Lets see moving back to 1.4.4 version of iPXE does anything different.

                    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
                    • J
                      jclumbo33
                      last edited by

                      Still no luck, it hangs in the same spot. I appreciate your help, I was hopeful on that one.

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

                        @jclumbo33 OK SO… its probably not ipxe that is causing things to stick, but the target system because we’ve kind of ruled out any changes to iPXE kernel or FOG since 1 year ago.

                        Would you ensure a firmware update does not address this?

                        It would be interesting to know what is different between the 400 G1 and others that do work.

                        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
                        • J
                          jclumbo33
                          last edited by

                          Upgrading the firmware worked!!! No idea what has changed in the last month, but I am just glad for a fix. Thanks for your help!

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

                          159

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project