FOG deploy: partitions 4 and 5 too big for disk

  • Moderator

    @madeyem said in FOG deploy: partitions 4 and 5 too big for disk:

    After updating to 1.5.9.111, do I have to tell FOG to use a special init or so or is the fix included in the default init? So far I did not try any different settings after updating to 1.5.9.111.

    When you update to the latest dev-branch version it will pull the latest inits from github and use those straight away. no extra step needed.

    After applying the steps described here for my partitions 4 and 5, it’s still not working. After deploying in debug mode, I get this output

    I might have been on the wrong track with this. Looking at this again now I am wondering why nvme0n1p3 (third partition) is that big and obviously not being shrunk on capture!??!

    Please schedule a debug capture task on the source host/drive and take pictures of the whole capture process so we see what’s actually happening.


  • @sebastian-roth After applying the steps described here for my partitions 4 and 5, it’s still not working. After deploying in debug mode, I get this output:

    debug_deploy


  • @sebastian-roth I will try the solution from the thread you referred to and report back.

    Another question:

    After updating to 1.5.9.111, do I have to tell FOG to use a special init or so or is the fix included in the default init? So far I did not try any different settings after updating to 1.5.9.111.

  • Moderator

    @madeyem You are definitely on the right track with updating to the latest FOG version (1.5.9.111 as of now).

    Taking a closer look at the partition table I see that there does not seem to be any free space to work with. Partition one starts at sector 2048 and is 1433600 sectors long.
    2048 + 1433600 = 1435648
    1435648 + 262144 = 1697792
    1697792 + 995418624 = 997116416
    997116416 + 1071104 = 998187520
    998187520 + 2027520 = 1000215040

    Usually FOG would shrink one of the partitions to make room and then move partitions forward to fit all of them on a smaller size disk.

    both SSD and HDD are 500 GB

    In the world of hard drives the size given by vendors is just a very rough “estimate”. The figures we see in the partition layout tell us this disk is actually 476.9 GB in size (1000215182 * 512 byte sector size / 1024 / 1024 / 1024).

    To find out the sector count of the other disk you can run blockdev --getsz /dev/sda in a FOG debug session on that host.

    Main question is, why is none of the five partitions being shrunk? I can imagine you have the same issue that we’ve seen in this topic: https://forums.fogproject.org/topic/15215/deploy-issue-after-copying-image-to-an-other-fog-server

367
Online

9.0k
Users

15.6k
Topics

145.1k
Posts