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

Problem with FOS USB boot

Scheduled Pinned Locked Moved
General Problems
3
8
961
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.
  • X
    xburnerx00
    last edited by Sep 25, 2019, 3:54 PM

    I created a FOS USB using a CentOS7 server running FOG 1.5.7 following the instructions provided here. I followed the steps specifically for CentOS7.

    I can boot into the menu and upon selection it starts the process and then it errors out.
    FOS Menu.jpg
    FOS Error.jpg
    I also get these errors when I choose FOG iPXE Jumpstart BIOS or FOG iPXE Jumpstart EFI
    iPXE EFI Error.jpg
    iPXE BIOS Error.jpg

    Some guidance would be appreciated.

    Thank you.

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Sep 25, 2019, 7:21 PM

      @xburnerx00 About the kernal panic: The current init files we provide are bigger than the ones we had when George wrote this great tutorial. So you need the grub.cfg file and change ramdisk_size=127000 to ramdisk_size=275000 in the various kernel parameter lines. I am fairly sure this will fix the boot issue.

      @george1421 I just updated your tutorial. Hope you don’t mind.

      It’s strange both the iPXE jumpstarters won’t work. Is this machine set to UEFI or legacy BIOS (CSM)?

      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 Sep 25, 2019, 7:56 PM Reply Quote 0
      • G
        george1421 Moderator @Sebastian Roth
        last edited by Sep 25, 2019, 7:56 PM

        @Sebastian-Roth Sure no problem, did I miss a ramdisk_size=275000 in the tutorial or did I have it set to ramdisk_size=256000.

        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
        • X
          xburnerx00
          last edited by Sep 25, 2019, 9:09 PM

          Thanks @Sebastian-Roth, changing those settings worked. The FOS USB works now. I was able to register and capture a test image from a laptop that does not have ethernet ports. I tested 3 different USB Ethernet dongles and they were all recognized. Saves me headaches of working on two different models of laptops numbering into the 200’s without ethernet ports.

          Concerning the iPXE jumpstarters, I have the machines I tested on set to Legacy BIOS. Unless I am missing something, I do not see the reason why to use those now that the USB is working. As long as I can register a machine and capture/deploy now, I think that’s all I need. Right?

          G 1 Reply Last reply Sep 25, 2019, 11:13 PM Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sep 25, 2019, 10:27 PM

            @xburnerx00 said in Problem with FOS USB boot:

            As long as I can register a machine and capture/deploy now, I think that’s all I need. Right?

            Indeed!

            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
            • G
              george1421 Moderator @xburnerx00
              last edited by george1421 Sep 25, 2019, 5:13 PM Sep 25, 2019, 11:13 PM

              @xburnerx00 said in Problem with FOS USB boot:

              I do not see the reason why to use those now that the USB is working.

              There are caveats to booting FOS Linux directly from USB. You also lose some flexibility by not using the iPXE boot loader. So jump starting into iPXE will give you 100% of the capabilities of FOG without using the onboard boot ROM.

              Either way the goal here is to image systems, how you arrive there is up to you.

              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
              • X
                xburnerx00
                last edited by Oct 1, 2019, 7:56 PM

                Great point on flexibility @george1421, any idea on how to get the ipxe jumpstarters working? I have been using the USB to capture and deploy but I think I may need them eventually and it would be nice to use all features available if needed.

                G 1 Reply Last reply Oct 1, 2019, 8:40 PM Reply Quote 0
                • G
                  george1421 Moderator @xburnerx00
                  last edited by Oct 1, 2019, 8:40 PM

                  @xburnerx00 The short answer is it should just work if you have the dhcp boot options set.

                  With that said, let me explain why this usb boot disk exists in the first place.

                  We have historically seen the pxe booting process hang (stop/freeze/abend what ever you want to call it) in 4 spots that causes the FOG admin troubles.

                  1. Either the computer doesn’t have a pxe boot option or for what ever reason iPXE isn’t being sent to the target computer.
                  2. iPXE is delivered to the target computer but iPXE will not startup
                  3. iPXE will start up but will not start up the FOS Linux kernel (bzImage). We almost always see this in uefi mode due to buggy uefi firmware on the target computer.
                  4. In uefi mode the imaging tech is using a network adapter not supported by the computer manufacturer so pxe booting isn’t an option.

                  So what the FOS Linux usb boot drive does is boot into Grub and then calls FOS Linux directly from the usb flash drive. This bypasses pxe booting and iPXE eliminating the above conditions. In this setup the Grub menu is a weak analogy to the more capable dynamic iPXE menus.

                  We did include iPXE boot loaders on the flash drive to boot iPXE directly from the usb boot stick instead of by PXE. By doing that we can eliminate issues 1 and 4 from above. But any issues with iPXE in 2 and 3 would still exist.

                  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
                  1 / 1
                  • First post
                    1/8
                    Last post

                  160

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project