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

    Make fog deploy the image to entire disk

    Scheduled Pinned Locked Moved
    General Problems
    2
    7
    745
    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.
    • O
      obeh
      last edited by obeh

      I have a project that requires me to deploy more then 100 laptops (3 different brands).
      I’m able to clone and deploy the images successfully.
      The issue is that fog is deploying on the target system only the used space and leaves the rest of the disk as un assign, what requires me to allocate the space back.

      Is there a way to tell fog to use the entire disk and not only allocate the space he needs to deploy?

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

        @obeh Please take a look at he (text) files d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions that you find in your /images/<IMAGENAME>/ directory on your FOG server and post the contents here.

        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
        • O
          obeh
          last edited by obeh

          By the way, this is the info about my setup:
          Fog is installed on ubuntu 18.04 and is acting as DHCP
          FOG is on the latest version
          Source OS: ubuntu 18.04 EUFI
          Source laptop and destination laptop are equal

          here are the files you asked for:

          d1.partitions:

          label: gpt
          label-id: 1AE58181-D396-42E3-BB4D-1A968B8CE9C9
          device: /dev/nvme0n1
          unit: sectors
          first-lba: 34
          last-lba: 500118158
          
          /dev/nvme0n1p1 : start=        2048, size=     1048576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=81F5D915-3EEC-4FAB-A195-0139D0E84712, name="EFI System Partition"
          /dev/nvme0n1p2 : start=     1050624, size=    56385882, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=DE8E4D9D-7DB3-4D34-A0BA-D31AB193DE97
          

          d1.minimum.partitions:

          label: gpt
          label-id: 1AE58181-D396-42E3-BB4D-1A968B8CE9C9
          device: /dev/nvme0n1
          unit: sectors
          first-lba: 34
          last-lba: 500118158
          
          /dev/nvme0n1p1 : start=        2048, size=     1048576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=81F5D915-3EEC-4FAB-A195-0139D0E84712, name="EFI System Partition"
          /dev/nvme0n1p2 : start=     1050624, size=    56810149, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=DE8E4D9D-7DB3-4D34-A0BA-D31AB193DE97
          

          d1.fixed_size_partitions: :1:1

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

            @obeh Which version of FOG do you use? From what I see so far it looks like you are running into a bug where NVMe disks were not resized/expanded on deploy. We fixed that not long ago. Manually updating the init files should fix this for you.

            Download the latest inits - 64 bit / 32bit and put those in /var/www/html/fog/service/ipxe/ - rename the original ones to have a backup copy of those. As well go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000 if you haven’t done that already.

            Now try deploying again and see if it is resized/expanded to full disk size properly.

            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
            • O
              obeh
              last edited by obeh

              I’m on 1.5.6

              Edit :
              It’s working!
              Now i have snapin that is not working.
              I’m trying to mount an extra disk after the deploy.
              Is the snapin can be used in that way.
              if so what do i need to do to make it work?

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

                @obeh Great to hear this is fixed. May I ask you to open a new topic to not mix things up. Other people will find information better if it’s not all together in one topic. Give us a bit more details like what exactly you are trying to do with the snapin and possible fog.log from the client.

                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

                O 1 Reply Last reply Reply Quote 0
                • O
                  obeh @Sebastian Roth
                  last edited by

                  @Sebastian-Roth will do.
                  Thank you

                  1 Reply Last reply Reply Quote 0
                  • 1 / 1
                  • First post
                    Last post

                  205

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project