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

    HP PROBOOK 450

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    2
    6
    752
    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.
    • C
      crustyjeff
      last edited by

      We just received 40 HP Probook 450. Half have a 512 SSD, half have 256 SSD. I created the master image on a machine with a 512GB hard disk and I chose resizable. My 512 machines deploy no problem. However when I deploy on the 256GB machines I get the following error:

      FOG_Error_2.jpg

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Sebastian Roth

        @crustyjeff

        Please try the following:

        • Schedule a new deploy for a host with 256 GB SSD but before you click “Create Task” tick the checkbox for debug.
        • Boot up the client and hit ENTER twice to get to the shell - run command fog and step through till you hit the error.
        • Now back in the shell manually run sgdisk -gl /images/Accessing2019/d1.mbr /dev/nvme0n1, take a picture and post that here.

        As well, can you please post the contents of the text file /images/Accessing2019/d1.partitions you have on your FOG server.

        You might find this helpful: https://forums.fogproject.org/topic/13906/ssd-fails-at-restoring-partition-tables-gpt-with-error-code-4

        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
        • C
          crustyjeff
          last edited by

          Here is D1.partitions data:

          label: gpt
          label-id: CE5B249F-84C2-4D00-A031-F39148FE43AE
          device: /dev/nvme0n1
          unit: sectors
          first-lba: 34
          last-lba: 1000215182

          /dev/nvme0n1p1 : start= 2048, size= 532480, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=B8586629-C43F-4CA9-AF7B-CFBC5232B042, name=“EFI system partition”, attrs=“GUID:63”
          /dev/nvme0n1p2 : start= 534528, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=9339B7EA-F20B-4994-B339-3DE18D26F672, name=“Microsoft reserved partition”, attrs=“GUID:63”
          /dev/nvme0n1p3 : start= 567296, size= 997793792, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=6539D77B-28A8-48B5-94EF-2F696A12F6B4, name=“Basic data partition”
          /dev/nvme0n1p4 : start= 998361088, size= 1843200, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=61D808EA-CF03-46A5-8B36-DE5A2C5550A4, name=“Basic data partition”, attrs=“RequiredPartition GUID:63”

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth

            @crustyjeff said in HP PROBOOK 450:

            /dev/nvme0n1p4 : start= 998361088, size= 1843200, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=61D808EA-CF03-46A5-8B36-DE5A2C5550A4, name=“Basic data partition”, attrs=“RequiredPartition GUID:63”

            This partition number 4 is a recovery partition which FOG doesn’t move on the disk. So it’s unable to shrink your main Windows partition.

            The smallest size you can shrink this layout to is about 477 GB (998361088 + 1843200 sectors * 512 byte per sector). Do you really need that recovery partition if you have an image that you can clone out to all your machines??

            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

            C 1 Reply Last reply Reply Quote 0
            • C
              crustyjeff @Sebastian Roth
              last edited by

              @Sebastian-Roth No, so how can i remove the recovery partition from the clone?

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by

                @crustyjeff said in HP PROBOOK 450:

                No, so how can i remove the recovery partition from the clone?

                Well just delete it from your master host, maybe even expand the third partition using the Windows disk management view and re-capture the image.

                Probably a good idea that you leave the image Accessing2019 on your FOG server and create a new image definition for the capture you take after removing the forth partition. This way you can always go back to the original state in case you figure that you’d need it for some reason.

                Deleting partitions is kind of a dangerous task. Do it on your own risk and if unsure take another backup copy of the whole system before you go ahead!

                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

                130

                Online

                12.1k

                Users

                17.3k

                Topics

                155.3k

                Posts
                Copyright © 2012-2024 FOG Project