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

Issue with Single Disk (resizable)

Scheduled Pinned Locked Moved
Hardware Compatibility
acer hardware ipxe legacy uefi
2
17
2.2k
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.
  • S
    Sebastian Roth Moderator
    last edited by Sebastian Roth May 12, 2021, 9:13 AM May 12, 2021, 3:11 PM

    @Eruthon Awesome documentation! If everyone in the forums would post that many details we wouldn’t have to ask that many questions. 😉 Well done.

    Interesting that it didn’t work on the first try. In the other topic we also had someone report that the last partition was not moved forward on the first try. As we don’t have any details on it I just can’t help it. So far it always worked in my tests on the first go. But I can’t proof there is no issue in the scripts. So please keep your eyes open and let us know if it happens again.

    The issue occurs on capture already. Deploy can’t fix it if the partition is not moved forward and you see this in d1.minimum.partitions right after the capture.

    Edit: Just noticed that FOG detected only one NTFS partition in your setup. Shouldn’t the recovery partitions be NTFS as well?!

    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 May 12, 2021, 4:10 PM Reply Quote 1
    • E
      Eruthon @Sebastian Roth
      last edited by May 12, 2021, 4:10 PM

      @sebastian-roth
      Thank you for the appreciation!

      Also maybe I just overlooked something, maybe edited wrong host, as I had multiple tabs and didn’t keep track of it. Otherwise I don’t see any other reason for it not working on the first try.

      1 Reply Last reply Reply Quote 0
      • E
        Eruthon
        last edited by Jun 4, 2021, 7:40 AM

        After some time I tried to deploy new Win10 21H1 image with some pre-installed software again with UEFI and GPT… also using the new init… sadly it didn’t capture the partitions correctly again… lost my nerve, so didn’t try the debug mode, but will try next week 🙂

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Sebastian Roth Jun 4, 2021, 6:49 AM Jun 4, 2021, 12:48 PM

          @Eruthon Before you capture again, please get us a copy of the text files /images/IMAGENAME/d1.minimum.partitions and post the contents here in the forums.

          If you have enough disk space on your FOG server you might even leave that image untouched and create a new image definition for the next capture/deploy test. It might be handy we have this “not working” one for debugging.

          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 Jun 4, 2021, 1:51 PM Reply Quote 0
          • E
            Eruthon @Sebastian Roth
            last edited by Eruthon Jun 4, 2021, 7:59 AM Jun 4, 2021, 1:51 PM

            @sebastian-roth In the heat of the moment I tried to edit the data partition size in that file to try it that way; I didn’t think it would work, but tried it as last resort. The issue persisted, also the log during deploying showed the same amount of blocks that were problematic because of smaller disk size.

            Sadly I didn’t back up the original file, but before the change I saw that the d1.partitions had the same values as the d1.minimum.partitions, so I copied the values from d1.partitions back after trying the mentioned experiment.

            d1.minimum.partition for the new 21H1 image:

            label: gpt
            label-id: D7496BEB-B8A7-4BDA-84D1-A924BDEB9789
            device: /dev/nvme0n1
            unit: sectors
            first-lba: 34
            last-lba: 1953525134
            sector-size: 512
            
            /dev/nvme0n1p1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=25DAF354-4243-415E-9163-8AA61F158BBC, name="EFI system partition", attrs="GUID:63"
            /dev/nvme0n1p2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=3C51C90A-87D5-4C14-9D3E-378D17FF0882, name="Microsoft reserved partition", attrs="GUID:63"
            /dev/nvme0n1p3 : start=      239616, size=    77211472, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE6CC19C-A52C-4909-B57D-E2915E54BB55, name="Basic data partition"
            /dev/nvme0n1p4 : start=  1952640000, size=      884224, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17790088-AF7B-4D4B-B155-8C7E9DAFE516
            

            The starting lba of the partition 4 is the same as in the posts of the 20H2 image you can see in my earlier posts. My point is I don’t see any differences between the working 20H2 image and the new 21H1 image, except for the size of the data partitions which is, ofc, expected.

            Also I wonder if the name of the issue here could be changed as it’s not longer a suitable name for the problem here. Could be changed to sth regarding the gpt partitions, so it wouldn’t sound like a problem with the PC model mentioned in the title.

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Jun 4, 2021, 2:24 PM

              @Eruthon No worries, I think that’s telling us that sometimes the move of the partition is not working. We see that size of nvme0n1p3 is way smaller than the start of nvme0n1p4. In that case the new init should notice the gap between those two partitions and move nvme0n1p4 forward for capturing (and move it back to it’s original position afterwards).

              Though without further information it’s kind of impossible to figure out why this happens. It never happened to me when I came up with this and tested on my systems. So I can’t replicate the issue as of now.

              Possibly this issue only can happen when you don’t run in debug mode anyway. Kind of a timing issue. We have had such a thing before and it’s really nasty to find and fix. But hey, I think there is no other change than trying major debug over and over on your system and see if it happens at some point.

              PS: Changed the title.

              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 1
              • S
                Sebastian Roth Moderator
                last edited by Jun 6, 2021, 7:26 PM

                @Eruthon Good news! I figured out why this would fail and fixed the issue. Please re-download the inits (http://fogproject.org/inits/init.xz and http://fogproject.org/inits/init_32.xz), put in /var/www/html/fog/service/ipxe/ and capture again (no debug mode).

                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 2 Replies Last reply Jun 6, 2021, 7:33 PM Reply Quote 0
                • E
                  Eruthon @Sebastian Roth
                  last edited by Jun 6, 2021, 7:33 PM

                  @sebastian-roth, thank you, files downloaded and ready, will report back with results tommorow!

                  1 Reply Last reply Reply Quote 0
                  • E
                    Eruthon @Sebastian Roth
                    last edited by Jun 7, 2021, 8:40 AM

                    @sebastian-roth, it’s working! Managed to deploy the image from 1TB to 240GB, hopefully it will work for others, too. Thank you verymuch for your time! Should I post some files here for reference?

                    1 Reply Last reply Reply Quote 0
                    • S
                      Sebastian Roth Moderator
                      last edited by Jun 7, 2021, 7:52 PM

                      @Eruthon Thanks for the quick feedback. Should be all fine now I think. No need to post partition files as long as it works for you now.

                      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

                      157

                      Online

                      12.1k

                      Users

                      17.3k

                      Topics

                      155.3k

                      Posts
                      Copyright © 2012-2024 FOG Project