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

    Cant PXE boot to fog server

    Scheduled Pinned Locked Moved
    FOG Problems
    7
    42
    19.7k
    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.
    • M
      mkstreet
      last edited by

      i found this thread while searching for my hardware. I’m not sure if my problem would be fixed by this kernel or not?

      I have Lenovo M72z and it PXE boots ok, but if I choose (or it times out on the pxe menu) to the first option: “boot from local disk”… well, it doesn’t happen.

      I get a black screen that says “Booting from local disk…” in the upper left corner, then it hangs there forever.

      As far as I can tell, everything else seems to be ok. I can upload and deploy images. Sometimes when I multicast, one computer in the group (of five computers) won’t wake (for unknown reasons) and then the multicast will be stuck at “Please Wait” (blue screen) until I go power up the offending hardware. Then it takes off fine.

      After I deploy an image, it tries to reboot and I get to the black screen “booting from local disk” hang (as noted above) again. When I hit ESC to skip the pxe menu, I can get in just fine… but then it will reboot once the first time after a deploy after a minute or so… I think this must be a delayed reboot command from FOG left over from the image deploy (because the black screen hang didnt ever complete successfully).

      I did the hardware inventory option and I noticed a message fly by about unknown/unrecognized BIOS “please report”. Though I am not sure where to report this?

      Here are the results from the hardware inventory of a typical machine:

      System Manufacturer
      LENOVO

      System Product
      3554CTO

      System Version
      ThinkCentre M72z

      System Serial Number
      PBG8GDG

      System Type
      Desktop

      BIOS Vendor
      LENOVO

      BIOS Version
      F6KT32AUS

      BIOS Date
      09/03/2013

      Motherboard Manufacturer
      LENOVO

      Motherboard Product Name
      MAHOBAY

      Motherboard Version
      NOK

      Motherboard Serial Number

      Motherboard Asset Tag

      CPU Manufacturer
      Intel® Corporation

      CPU Version
      Intel® Core™ i5-3470S CPU @ 2.90GHz

      CPU Normal Speed
      2900 MHz

      CPU Max Speed
      2900 MHz

      Memory
      3433056 kB

      Hard Disk Model
      WDC WD10EZEX-08RKKA0

      Hard Disk Firmware
      80.00A80

      Hard Disk Serial Number
      WD-WCC1S6883074

      ++ ++ ++ ++
      Fog Server:
      O/S Ubuntu V14.0x, 64-bit
      Fog Software: v3121

      Deploy Computers:
      O/S Windows 7, 64 bit
      HDD: about 300 GB

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

        [quote=“mkstreet, post: 27254, member: 24215”]i found this thread while searching for my hardware. I’m not sure if my problem would be fixed by this kernel or not?

        I have Lenovo M72z and it PXE boots ok, but if I choose (or it times out on the pxe menu) to the first option: “boot from local disk”… well, it doesn’t happen.

        I get a black screen that says “Booting from local disk…” in the upper left corner, then it hangs there forever.[/quote]

        Change the exit type within the GUI. There are two types, exit and sanboot. For your setup, try with exit. It’s defaulted to sanboot.

        Location is: FOG Configuration->FOG Settings->FOG Boot Settings->FOG_BOOT_EXIT_TYPE

        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
        • M
          mkstreet
          last edited by

          [quote=“Tom Elliott, post: 27259, member: 7271”]Change the exit type within the GUI. There are two types, exit and sanboot. For your setup, try with exit. It’s defaulted to sanboot.

          Location is: FOG Configuration->FOG Settings->FOG Boot Settings->FOG_BOOT_EXIT_TYPE[/quote]

          Hi Tom,

          Thanks for the reply. I will try that on Monday. Would this FOG_BOOT_EXIT_TYPE affect all exits to the local disk boot – and not just boots-after-deploy? I have this same get-stuck “Booting from local disk…” when I choose “1” from the PXE menu.

          Do I need to be concerned about that message during FOG Hardware Inventory about unknown BIOS ?

          Sorry about not including the version info. I’m using… Fog Vers: 0.32 O/S: Ubuntu 12.04.04 LTS (Pangolin)

          ++ ++ ++ ++
          Fog Server:
          O/S Ubuntu V14.0x, 64-bit
          Fog Software: v3121

          Deploy Computers:
          O/S Windows 7, 64 bit
          HDD: about 300 GB

          1 Reply Last reply Reply Quote 0
          • JunkhackerJ
            Junkhacker Developer
            last edited by

            FOG_BOOT_EXIT_TYPE is only relevant for .33+ versions of Fog.
            does the computer boot properly when not connected to the network?

            signature:
            Junkhacker
            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

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

              [quote=“mkstreet, post: 27353, member: 24215”]Hi Tom,

              Thanks for the reply. I will try that on Monday. Would this FOG_BOOT_EXIT_TYPE affect all exits to the local disk boot – and not just boots-after-deploy? I have this same get-stuck “Booting from local disk…” when I choose “1” from the PXE menu.

              Do I need to be concerned about that message during FOG Hardware Inventory about unknown BIOS ?

              Sorry about not including the version info. I’m using… Fog Vers: 0.32 O/S: Ubuntu 12.04.04 LTS (Pangolin)[/quote]

              As you’re using 0.32. There are two options to fix this issue for you.

              First is, if you’re able to, upgrade to 1.x.x FOG. The reason being is related to what I’ll ask you to try secondly. You will have to make a change on the DHCP Option 67 to be looking for file: undionly.kpxe as opposed to pxelinux.0 as was done in the past. 1.x.x does chainloading natively and should help with your issue. With it, you’ll be able to change the exit type of FOG as well, so if one doesn’t work, try the other and you should be good to go.

              Second, look up chainloading howto on the wiki. This should help you out if you can’t upgrade.

              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
              • M
                mkstreet
                last edited by

                [quote=“Junkhacker, post: 27364, member: 21583”]FOG_BOOT_EXIT_TYPE is only relevant for .33+ versions of Fog.
                does the computer boot properly when not connected to the network?[/quote]

                If its not connected to the network, yes it will boot properly.
                It tries the network for about 40 seconds because PXE is our first boot device, then it gives up and goes on normally to the local HDD.
                If I press escape, it will exit trying PXE and go on normally as if it had given up on PXE too.

                ++ ++ ++ ++
                Fog Server:
                O/S Ubuntu V14.0x, 64-bit
                Fog Software: v3121

                Deploy Computers:
                O/S Windows 7, 64 bit
                HDD: about 300 GB

                1 Reply Last reply Reply Quote 0
                • M
                  mkstreet
                  last edited by

                  [quote=“Tom Elliott, post: 27365, member: 7271”]As you’re using 0.32. There are two options to fix this issue for you.

                  First is, if you’re able to, upgrade to 1.x.x FOG. The reason being is related to what I’ll ask you to try secondly. You will have to make a change on the DHCP Option 67 to be looking for file: undionly.kpxe as opposed to pxelinux.0 as was done in the past. 1.x.x does chainloading natively and should help with your issue. With it, you’ll be able to change the exit type of FOG as well, so if one doesn’t work, try the other and you should be good to go.

                  Second, look up chainloading howto on the wiki. This should help you out if you can’t upgrade.[/quote]

                  We’ve been using FOG a grand total of about two weeks.

                  In the first week, we tried getting 1.0.0 FOG from SVN (this was just prior to 13-May-2014) and installing it (on Ubuntu 14.04). Since we are using static IP in this computer lab, we did try setting up FOG as ProxyDHCP with dnsmasq (btw, those are what the wiki chainloading links redirect to). We had trouble getting any of that to work. Though offhand all the things we encountered are a blur now.

                  Our solution attempt was to go back to FOG 0.32 and Ubuntu 12.04.04. We did this and upload/deploy started working right away and so easily that our days/hours of earlier effort with 1.0.0 FOG and dnsmasq config seem like wasted hours of head-pounding-wall.

                  Right now, it’s really only this issue of BOOT LOCAL DISK remaining and this Com Lab goes live in under 24 hours. If changing that FOG_EXIT_BOOT_TYPE is not an option, then I will have to wait until there is time to “play” with this again.

                  ++ ++ ++ ++
                  Fog Server:
                  O/S Ubuntu V14.0x, 64-bit
                  Fog Software: v3121

                  Deploy Computers:
                  O/S Windows 7, 64 bit
                  HDD: about 300 GB

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

                    Try from this wiki:
                    [url]http://fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url]

                    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
                    • M
                      mkstreet
                      last edited by

                      [quote=“Tom Elliott, post: 27378, member: 7271”]Try from this wiki:
                      [url]http://fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url][/quote]

                      Ah, that looks interesting. It’s 8am on Sunday here. When I get to school tomorrow, I will try this and report back as soon as I can.
                      Thanks much!

                      ++ ++ ++ ++
                      Fog Server:
                      O/S Ubuntu V14.0x, 64-bit
                      Fog Software: v3121

                      Deploy Computers:
                      O/S Windows 7, 64 bit
                      HDD: about 300 GB

                      1 Reply Last reply Reply Quote 0
                      • M
                        mkstreet
                        last edited by

                        [quote=“Tom Elliott, post: 27378, member: 7271”]Try from this wiki:
                        [url]http://fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url][/quote]

                        FYI… on that link above it says:


                        [SIZE=5][B]Update SYSLINUX[/B][/SIZE]

                        [LIST]
                        []Download and extract the latest SYSLINUX (Currently using 4.04): [url]http://www.kernel.org/pub/linux/utils/boot/syslinux/[/url]
                        [
                        ]Copy/Overwrite the following files to /tftpboot/:
                        [/LIST]
                        syslinux-4.04/com32/modules/chain.c32
                        syslinux-4.04/com32/menu/vesamenu.c32
                        syslinux-4.04/core/pxelinux.0


                        But the “latest” syslinux (6.02) doesn’t have these files anymore.
                        I’ve downloaded the 4.04 version (since that was also referenced in the wiki link).

                        ++ ++ ++ ++
                        Fog Server:
                        O/S Ubuntu V14.0x, 64-bit
                        Fog Software: v3121

                        Deploy Computers:
                        O/S Windows 7, 64 bit
                        HDD: about 300 GB

                        1 Reply Last reply Reply Quote 0
                        • M
                          mkstreet
                          last edited by

                          [quote=“Tom Elliott, post: 27378, member: 7271”]Try from this wiki:
                          [url]http://fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url][/quote]

                          Tom,

                          It seems to have fixed the problem. Thanks!

                          I did use SYSLINUX 4.04…

                          Mark

                          ++ ++ ++ ++
                          Fog Server:
                          O/S Ubuntu V14.0x, 64-bit
                          Fog Software: v3121

                          Deploy Computers:
                          O/S Windows 7, 64 bit
                          HDD: about 300 GB

                          1 Reply Last reply Reply Quote 0
                          • M
                            mkstreet
                            last edited by

                            [quote=“mkstreet, post: 27393, member: 24215”]Tom,

                            It seems to have fixed the problem. Thanks!

                            I did use SYSLINUX 4.04…

                            Mark[/quote]

                            Perhaps I spoke to soon.

                            After I restarted FOG and Ubuntu, I tried to do a deploy with multicast. The computers tried to boot and would eventually timeout on trying to locate DHCP.

                            I un-did these SYSLINUX changes and then they could find DHCP again.

                            I wonder if it would be better if I used something more recent than SYSLINUX 4.04?

                            Mark

                            ++ ++ ++ ++
                            Fog Server:
                            O/S Ubuntu V14.0x, 64-bit
                            Fog Software: v3121

                            Deploy Computers:
                            O/S Windows 7, 64 bit
                            HDD: about 300 GB

                            1 Reply Last reply Reply Quote 0
                            • M
                              mkstreet
                              last edited by

                              I solved the problem. For some reason the isc-dhcp-server was not running. This hadn’t happened before, but starting that and restarting tftpd-hpa fixed the DHCP issue.

                              This is for Ubuntu 12.04.04 with Fog 0.32

                              ++ ++ ++ ++
                              Fog Server:
                              O/S Ubuntu V14.0x, 64-bit
                              Fog Software: v3121

                              Deploy Computers:
                              O/S Windows 7, 64 bit
                              HDD: about 300 GB

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

                              155

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project