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

    GPT UEFI ERROR PARTITION 4 TOO BIG

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    4
    324
    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.
    • A
      alexamore90
      last edited by alexamore90

      hi, i captured a win 10 image in uefi, but when i distribute it with fog i get this:
      error partition 4 is too big
      until a few days ago the old uefi image worked, now I wanted to update it and it gives me this error, on any pc.

      I always read on the forum that you have to remove the recovery partition, possible? even though the old uefi image worked normally, i never deleted the recovery partition

      who can help me?
      thank you

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

        @alexamore90 The recovery partition is the issue with FOG 1.5.9, if you update to the dev branch you will get FOG 1.5.9.115 or later that will solve the problem. You will need to recapture the golden image with FOG 1.5.9.115 or later to make that recovery partition movable again. This is a change that Microsoft released in 20h2 and later operating systems.

        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!

        A 1 Reply Last reply Reply Quote 0
        • A
          alexamore90 @george1421
          last edited by alexamore90

          @george1421

          ah ok how can I check and eventually update the fog real you say?
          logically without losing any deletions or data inside the fog.
          having 3 virtual fog do I have to update all 3?

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

            @alexamore90 Updating FOG is a normal process of fog administration. I agree its been quite a while since the last update but the process is the same. FOG 1.5.10 should be released soon, but until then the FOG developers are suggesting that people upgrade to a pre release but stable version of the development release.

            When you installed fog if you use the git method to download the installer files then upgrading is easy and you will not lose any configuration settings. To do the upgrade its pretty easy, to perform a dev-branch upgrade there is one more step.

            In your case if you are on FOG version 1.5.9 and you use the git method you would simply change to the base of the install directory (typically in /root/fogproject) and issue these commands on the fog server.

            cd /root/fogproject
            git pull
            git checkout dev-branch
            git pull
            cd bin
            ./installfog.sh
            

            The git checkout dev-branch command is what changes the installer to use the 1.5.9.115 (or later code base). When 1.5.10 is released you would simply replace that line with to go to the master code base with git checkout master and issue the same commands.

            The installer installfog.sh will look at all of the answers you provided when fog was installed and use them during the reinstall.

            After you update to the 1.5.9.115 dev release you will need to once again update the FOS Linux kernel to 5.15.x series (FOG WebUI->FOG Configuraiton->Kernel update, as well as recompile the latest version of iPXE using this tutorial https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe when you complete these after steps you will be at a level that FOG 1.5.10 will be when its released. The above install process will make sure your FOG install will support the newest hardware released by the hardware manufacturers.

            You say that you have 3 FOG servers you really should update them all to be on the same release or you won’t have the fix for the non-movable recovery partition that Microsoft created.

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

            152

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project