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

    iPXE initialises devices ok but reboots when Configuring(net0 00:23:7d:b8:a5:54)......

    Scheduled Pinned Locked Moved
    FOG Problems
    7
    32
    7.9k
    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.
    • Wayne WorkmanW
      Wayne Workman @luislesi
      last edited by

      @luislesi It’s like iPXE isn’t getting any arguments, to me. I’ve not seen this one before, I’m going to need to defer to the other @Developers and @Moderators.

      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!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @Wayne Workman
        last edited by Tom Elliott

        @Wayne-Workman This isn’t something We’re doing. Maybe we can do more with the boot.php script output.

        http://fog-server/fog/service/boot.php

        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

        L 2 Replies Last reply Reply Quote 0
        • L
          luislesi @Tom Elliott
          last edited by

          @Tom-Elliott

          I Tom. I had to change the boot file again to undionly.kpxe.
          At this time i don’t know how i solved this problem.
          I tried two things:
          I updated the kernel to version 3.19.3 and I changed permissions of ipxe:

                   chmod -R 775 /var/www/html/fog/service/ipxe
          

          The only problem is that i have write exit in ipxe to download/upload start.

          https://goo.gl/photos/a38gXYjXiNCT3oEN6

          Many Thanks

          Wayne WorkmanW 1 Reply Last reply Reply Quote 0
          • Wayne WorkmanW
            Wayne Workman @luislesi
            last edited by

            @luislesi We need the output of the link that Tom requested.

            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!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            L 1 Reply Last reply Reply Quote 0
            • L
              luislesi @Wayne Workman
              last edited by luislesi

              @Wayne-Workman

              Today I installed another server with the same configurations and i noticed that the original problem was solved by getting another undionly.kpxe.

              wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe -O /tftpboot/undionly.kpxe
              

              I originally thought that the problem was solved by upgrading the Kernel and changing the permissions of ipxe, but the problem was solved by getting another undionly.kpxe. But I don´t know if this boot file is reliable.

              The only thing i know, is that after this, if i write exit in ipxe, the fog works. But i need to solve this.

              Photo: https://goo.gl/photos/GV6XxJUgdhqRAxgg6

              The contents of boot.php that you asked (http://10.1.8.1/fog/service/ipxe/boot.php) are:

              #!ipxe
              cpuid --ext 29 && set arch x86_64 || set arch i386
              colour --rgb 0xff6600 2
              cpair --foreground 7 --background 2 2
              console --picture http://10.1.8.1/fog/service/ipxe/bg.png --left 100 --right 80
              :MENU
              menu
              colour --rgb 0xff0000 0
              cpair --foreground 0 3
              item --gap Host is NOT registered!
              item --gap -- -------------------------------------
              item fog.local Boot from hard disk
              item fog.memtest Run Memtest86+
              item fog.reginput Perform Full Host Registration and Inventory
              item fog.reg Quick Registration and Inventory
              item fog.sysinfo Client System Information (Compatibility)
              choose --default fog.local --timeout 3000 target && goto ${target}
              :fog.local
              exit || goto MENU
              :fog.memtest
              kernel memdisk iso raw
              initrd memtest.bin
              boot || goto MENU
              :fog.reginput
              kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=10.1.8.1/fog/ consoleblank=0 loglevel=4 mode=manreg
              imgfetch init_32.xz
              boot || goto MENU
              :fog.reg
              kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=10.1.8.1/fog/ consoleblank=0 loglevel=4 mode=autoreg
              imgfetch init_32.xz
              boot || goto MENU
              :fog.sysinfo
              kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=10.1.8.1/fog/ consoleblank=0 loglevel=4 mode=sysinfo
              imgfetch init_32.xz
              boot || goto MENU
              autoboot
              
              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by

                @luislesi Why does it fail on the first DHCP request is the main question I suppose…

                Maybe spanning tree /port fast setting on the switch? Please search the wiki and forum for this.

                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
                • L
                  luislesi @Tom Elliott
                  last edited by

                  @Tom-Elliott

                  I still don’t understand why computer reboots with the original undionly.kpxe that comes with the fog installer (1.2.0) and when i get the undionly.kpxe from https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe
                  it works but i have to write exit in IPXE.
                  You can see it in this photo:
                  https://goo.gl/photos/GV6XxJUgdhqRAxgg6
                  I will try to do spanning tree /port fast setting on the switch like @Sebastian-Roth said but i think this is not the reason.
                  Is there any script that i can do to automatically exit from IPXE?
                  Thanks

                  Tom ElliottT 1 Reply Last reply Reply Quote 0
                  • Tom ElliottT
                    Tom Elliott @luislesi
                    last edited by

                    @luislesi If I had to guess, if you go to the browser at url (Making adjustments for your environment)

                    http://10.1.8.1/fog/service/ipxe/boot.php?mac=00:23:7d:b9:2d:f2

                    What’s output to the browser? My guess is it’s missing a “boot” line.

                    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

                    L 1 Reply Last reply Reply Quote 0
                    • L
                      luislesi @Tom Elliott
                      last edited by Tom Elliott

                      @Tom-Elliott

                      The output of the file is:

                      #!ipxe
                      cpuid --ext 29 && set arch x86_64 || set arch i386
                      colour --rgb 0xff6600 2
                      cpair --foreground 7 --background 2 2
                      console --picture http://10.1.8.1/fog/service/ipxe/bg.png --left 100 --right 80
                      :MENU
                      menu
                      colour --rgb 0x00ff00 0
                      cpair --foreground 0 3
                      item --gap Host is registered as RP044390
                      item --gap -- -------------------------------------
                      item fog.local Boot from hard disk
                      item fog.memtest Run Memtest86+
                      item fog.keyreg Update Product Key
                      item fog.quickimage Quick Image
                      item fog.quickdel Quick Host Deletion
                      item fog.sysinfo Client System Information (Compatibility)
                      choose --default fog.local --timeout 3000 target && goto ${target}
                      :fog.local
                      exit || goto MENU
                      :fog.memtest
                      kernel memdisk iso raw
                      initrd memtest.bin
                      boot || goto MENU
                      :fog.reginput
                      kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=10.1.8.1/fog/ consoleblank=0 loglevel=4 1
                      imgfetch init_32.xz
                      boot || goto MENU
                      :fog.keyreg
                      login
                      params
                      param mac0 ${net0/mac}
                      param arch ${arch}
                      param username ${username}
                      param password ${password}
                      param keyreg 1
                      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                      :bootme
                      chain -ar http://10.1.8.1/fog/service/ipxe/boot.php##params ||
                      goto MENU
                      :fog.reg
                      kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=10.1.8.1/fog/ consoleblank=0 loglevel=4 1
                      imgfetch init_32.xz
                      boot || goto MENU
                      :fog.quickimage
                      login
                      params
                      param mac0 ${net0/mac}
                      param arch ${arch}
                      param username ${username}
                      param password ${password}
                      param qihost 1
                      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                      :bootme
                      chain -ar http://10.1.8.1/fog/service/ipxe/boot.php##params ||
                      goto MENU
                      :fog.quickdel
                      login
                      params
                      param mac0 ${net0/mac}
                      param arch ${arch}
                      param username ${username}
                      param password ${password}
                      param delhost 1
                      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                      :bootme
                      chain -ar http://10.1.8.1/fog/service/ipxe/boot.php##params ||
                      goto MENU
                      :fog.sysinfo
                      kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=10.1.8.1/fog/ consoleblank=0 loglevel=4 mode=sysinfo
                      imgfetch init_32.xz
                      boot || goto MENU
                      :fog.debug
                      login
                      params
                      param mac0 ${net0/mac}
                      param arch ${arch}
                      param username ${username}
                      param password ${password}
                      param debugAccess 1
                      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                      :bootme
                      chain -ar http://10.1.8.1/fog/service/ipxe/boot.php##params ||
                      autoboot
                      
                      Tom ElliottT 1 Reply Last reply Reply Quote 0
                      • Tom ElliottT
                        Tom Elliott @luislesi
                        last edited by

                        @luislesi Does it only show the menu IF you type exit, or is exit needed only presented when the host is tasked? The Reason I ask: The picture from earlier shows the host was in a task.

                        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

                        L 1 Reply Last reply Reply Quote 0
                        • L
                          luislesi @Tom Elliott
                          last edited by

                          @Tom-Elliott

                          Fog stops in IPXE even when i just want to get to the menu.

                          1 Reply Last reply Reply Quote 0
                          • Tom ElliottT
                            Tom Elliott
                            last edited by

                            Are you using undionly.kpxe or undionly.kkpxe? Could you try ipxe.pxe?

                            Is this on ALL machines, or just this particular model?

                            Is it ONLY this machine itself and all others work?

                            I’m just trying to get all the info.

                            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

                            L 2 Replies Last reply Reply Quote 0
                            • L
                              luislesi @Tom Elliott
                              last edited by

                              @Tom-Elliott

                              Now i’m using undionly.kpxe. I tried undionly.kkpxe but it did not work.
                              I will try ipxe.pxe.
                              This occurs in all machines.

                              Thanks

                              1 Reply Last reply Reply Quote 0
                              • L
                                luislesi @Tom Elliott
                                last edited by

                                @Tom-Elliott

                                I changed the boot file to ipxe.pxe and i’ve got the same original problem.

                                So i downloaded the boot file ipxe.pxe using this command:

                                wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.pxe -O /tftpboot/ipxe.pxe

                                And the result was the same as using undionly.kpxe, stops at IPXE.

                                G 1 Reply Last reply Reply Quote 0
                                • G
                                  gwhitfield @luislesi
                                  last edited by gwhitfield

                                  @luislesi I spent almost the entire day today trying to figure out a very similar issue - I was seeing the same response to pxe boot. We have two VLANs in the building and one worked and the other did not. On our “problem” VLAN it turns out we had spanning tree turned on, but it was turned off on the “good” VLAN. To make matters worse we can’t turn it off because the network issue it is resolving hasn’t been located yet.

                                  What I ended up doing was turning portfast (props @Sebastian-Roth) on individually for each of the ports being used by the machines I wanted to image. I’m NOT a network guru, I can’t explain to you why it works but it did in my case. Just my 0.02, I don’t see that you have yet posted the results of the STP/PF adjustments you planned to make.

                                  Edit: To try to clarify, I believe the iPXE messages you’re seeing up to the point of the “iPXE>” prompt is the output of the PXE boot ROM of the computer, not anything coming from the network. The DHCP boot process is failing and the PC is not reaching the FOG server. In my case it was due to spanning tree being turned on in our network. The only way around that was to enable portfast on the switch.

                                  L 1 Reply Last reply Reply Quote 0
                                  • L
                                    luislesi @gwhitfield
                                    last edited by

                                    @gwhitfield The portfast it’s enabled in all ports of the switch so at this moment i dont know what to do anymore. Thanks for all that helped me.

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

                                      @luislesi Sorry if this is a repeat, I quickly looked through the thread and didn’t see this…

                                      Can you upgrade your 1.2.0 stable version of fog to 1.3.0-rc4? This will upgrade the FOG environment to the latest. https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

                                      I feel you have done everything with 1.2.0 with no success. I’m not saying for absolute that 1.3.0-rc4 will fix your issue, but there has been quite a few enhancements in the boot code for ipxe as well as the fos engine (linux OS that is booted on the target 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!

                                      1 Reply Last reply Reply Quote 1
                                      • Wayne WorkmanW
                                        Wayne Workman
                                        last edited by

                                        I agree with George. There’s just no reason to not use the latest RC. It’s solid. And the more people we have testing it, the more sure we can be that it’s ready.

                                        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!
                                        Daily Clean Installation Results:
                                        https://fogtesting.fogproject.us/
                                        FOG Reporting:
                                        https://fog-external-reporting-results.fogproject.us/

                                        1 Reply Last reply Reply Quote 0
                                        • K
                                          koenkeersmaekers
                                          last edited by

                                          I’m having the same problem trying to image using ASIX88772B dongle …
                                          I’m using undionly.kkpxe as boot file fog 1.2.0 and the machine is in legacy mode.
                                          What can be wrong?

                                          Tom ElliottT 1 Reply Last reply Reply Quote 0
                                          • Tom ElliottT
                                            Tom Elliott @koenkeersmaekers
                                            last edited by

                                            @koenkeersmaekers As the other answers suggest, please upgrade to the RC’s as it will have much better support for these things. FOG 1.2.0 is nearly 3.5 years old now. The RC’s are much more reliable (I think) and will likely address common issues related to what you’re possibly seeing as well as the LARGE number of improvements made overall.

                                            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

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

                                            159

                                            Online

                                            12.1k

                                            Users

                                            17.3k

                                            Topics

                                            155.3k

                                            Posts
                                            Copyright © 2012-2024 FOG Project