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

Ubuntu wont boot up after the image is deployed

Scheduled Pinned Locked Moved
Linux Problems
2
7
1.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.
  • E
    emreonder
    last edited by Sebastian Roth Dec 22, 2020, 11:49 PM Dec 15, 2020, 12:56 AM

    Hi,
    I have those ubuntu hosts after downloading the image they do not boot up properly if they are still in the network that the fog server is there.

    I have tried all the combination in the FogSettings => FogBoot Settings EFI BOOT EXIT TYPE, BOOT EXIT TYPE it does not boot unless i unplug the fogserver from the network. It keep stuck at booting from hdd 3 sec and again and again.

    I am going crazy here PLEASE HEEEELP šŸ˜„

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Dec 15, 2020, 6:47 AM

      @emreonder said in Ubuntu wont boot up after the image is captured:

      I have tried all the combination in the FogSettings => FogBoot Settings EFI BOOT EXIT TYPE, BOOT EXIT TYPE

      Those two settings are for two different modes and I reckon it’s good we start out with finding what your machines are booting up. Are they setup to boot in legacy BIOS mode or UEFI?

      Is the image type set to resizable or non-resizable?

      Please grab the text file containing the partition table on your FOG server in /images/IMAGENAME/d1.partitions and post that here as well so we might see if your partition layout can cause an issue.

      In the topic caption you say ā€œā€¦ after the image is capturedā€. We use the term capture for when an image is pulled from a master and saved to the FOG server. From the description it sounds as if you mean the issue is when deploying. Just want to make sure we don’t bark up the wrong tree.

      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

      E 1 Reply Last reply Dec 22, 2020, 10:15 PM Reply Quote 0
      • E
        emreonder @Sebastian Roth
        last edited by Sebastian Roth Dec 22, 2020, 11:50 PM Dec 22, 2020, 10:15 PM

        @sebastian-roth

        Correct. After the image is deployed i should have said.

        it is single disk resizable everything

        ubuntu@machine-c023d04h04w1-103:/images/ubuntu16$ cat d1.partitions
        label: dos
        label-id: 0x743426a3
        device: /dev/sda
        unit: sectors
        sector-size: 512
        
        /dev/sda1 : start=        4096, size=    52023296, type=83, bootable
        /dev/sda2 : start=    52031486, size=     8032258, type=f
        /dev/sda5 : start=    52031494, size=     8028160, type=83
        
        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Dec 23, 2020, 6:11 AM

          @emreonder Can you explain what you have installed on this disk/partition layout? Why do I ask? The first partition (sda1) is roughly 24.8 GB and marked bootable. I cannot imagine this is a normal Linux boot partition. Then second (sda2) is an extended partition (container for logical partitions), fine! And last (sda5) is a logical partition of 3.8 GB size. So possibly your Linux root filesystem is stored in sda1 and /home in sda5?

          So to your initial request: This seems to be a legacy BIOS setup and therefore only ā€œBOOT EXIT TYPEā€ will play a role in your case. Focus on that, try the different options (like SANBOOT, EXIT, GRUB_HDD) and tell is what exactly happens on each of them - there should be differences. Best if you can take pictures of each and post here.

          I can’t promise you one of them is working as it depends on the hardware used. Some devices (or actually the BIOS of those) is not playing nicely. If non of the default exit types work you might be able to adjust the GRUB_HDD type in the code to make it work. We’ll discuss this later.

          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

          E 1 Reply Last reply Dec 26, 2020, 7:38 PM Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth Dec 23, 2020, 12:35 AM Dec 23, 2020, 6:31 AM

            @emreonder All your posts seem to be about the same matter (exit type not working after the deploy) and information is spread across three different posts:
            https://forums.fogproject.org/topic/14972/need-to-install-fog-server-urgent-remote-support-needed
            https://forums.fogproject.org/topic/15028/is-it-possible-to-update-bios-setting-via-fog-server

            Let’s try to keep this all together. One interesting information from the other topic is this:

            I have 2 type of mother boards one of them called color. I have never heard this before but it works perfect.
            If i deploy the same image to the gigabyte (GA-H110-D3A) then i run in troubles.

            So as I said earlier, the exit types don’t behave the same on each and every hardware. So Gigabyte is to blame here. Do you have the latest BIOS version installed on those??

            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
            • E
              emreonder @Sebastian Roth
              last edited by Dec 26, 2020, 7:38 PM

              @sebastian-roth said in Ubuntu wont boot up after the image is deployed:

              xplain what you have installed on this disk/partition layout? Why do I ask? The first partition (sda1) is roughly 24.8 GB and marked bootable. I cannot imagine this is a normal Linux boot partition. Then second (sda2) is an extended partition (container for logical partitions), fine! And last (sda5) is a logical partition of 3.8 GB size. So possibly your Linux root filesystem is stored in sda1 and /home in sda5?

              I am a bit confused to be honest.

              28971281-7977-4b21-a2da-5c7d4fabb535-image.png

              Because i can not see the sda2 and 5 in the disk lay out

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Jan 4, 2021, 10:15 AM

                @emreonder Sorry for my late reply. Lost track of this over the holidays.

                I am still at a loss on why your partition looks like this. What is the extended partition actually used for?

                Beside that I can’t really guess what might be special about this setup/layout that prevents it from chainloading to disk after iPXE is loaded on the Gigabyte motherboard. We know it works on other hardware and therefore I’d think the bootloader on disk is being properly imaged through FOG.

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

                182

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright Ā© 2012-2024 FOG Project