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

FOG deploy: partitions 4 and 5 too big for disk

Scheduled Pinned Locked Moved
FOG Problems
2
24
4.1k
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.
  • M
    madeyem @Sebastian Roth
    last edited by Oct 28, 2021, 8:12 AM

    @sebastian-roth

    I re-captured an image on a SSD machine (with the new init) and deployed to the HDD machine, but got the same error message as before.

    From the re-captured image:

    d1.minimum.partitions:

    label: gpt
    label-id: 8C0CB60E-93F5-4C14-B633-3852928F826C
    device: /dev/nvme0n1
    unit: sectors
    first-lba: 34
    last-lba: 1000215182
    sector-size: 512
    
    /dev/nvme0n1p1 : start=        2048, size=     1433600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=2AFFEC30-5F77-4C6B-BA7C-902A01A971E1, name="EFI system partition", attrs="GUID:63"
    
    /dev/nvme0n1p2 : start=     1435648, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=E8336B4A-8C8F-48F5-85DE-E6237B7A372F, name="Microsoft reserved partition", attrs="GUID:63"
    
    /dev/nvme0n1p3 : start=     1697792, size=   995426761, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=38131294-BD57-43F5-ACE4-2E1413614C9A, name="Basic data partition"
    
    /dev/nvme0n1p4 : start=   997126144, size=     1060864, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=A31B261E-E3EB-4671-BE66-F71AEEB51DB8, attrs="RequiredPartition GUID:63"
    
    /dev/nvme0n1p5 : start=   998187520, size=     2027520, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=84072955-EDFD-4E05-84E6-C3A6C50CDB30, name="attrs=\x22RequiredPartition GUID:63
    

    d1.partitions:

    label: gpt
    label-id: 8C0CB60E-93F5-4C14-B633-3852928F826C
    device: /dev/nvme0n1
    unit: sectors
    first-lba: 34
    last-lba: 1000215182
    sector-size: 512
    
    /dev/nvme0n1p1 : start=        2048, size=     1433600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=2AFFEC30-5F77-4C6B-BA7C-902A01A971E1, name="EFI system partition", attrs="GUID:63"
    
    /dev/nvme0n1p2 : start=     1435648, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=E8336B4A-8C8F-48F5-85DE-E6237B7A372F, name="Microsoft reserved partition", attrs="GUID:63"
    
    /dev/nvme0n1p3 : start=     1697792, size=   995426761, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=38131294-BD57-43F5-ACE4-2E1413614C9A, name="Basic data partition"
    
    /dev/nvme0n1p4 : start=   997126144, size=     1060864, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=A31B261E-E3EB-4671-BE66-F71AEEB51DB8, attrs="RequiredPartition GUID:63"
    
    /dev/nvme0n1p5 : start=   998187520, size=     2027520, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=84072955-EDFD-4E05-84E6-C3A6C50CDB30, name="attrs=\x22RequiredPartition GUID:63"
    

    The third partition still seems to be too big (i.e. not shrunk), do you agree?

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Sebastian Roth Nov 7, 2021, 12:48 PM Nov 7, 2021, 6:16 PM

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

      ...
      /dev/nvme0n1p5 : ... name="attrs=\x22RequiredPartition GUID:63"
      ...
      

      Wohoooo, it still has that same name/attrs problem. No idea why as I thought I had fixed that.

      Edit: OMG, after some more digging I found that the change I made and committed to github didn’t make it into the test init I updated a few days after I asked you to test. My fault, because I work on another issue with someone else using the same test init. I am sorry. Please download the latest init from github once again, re-capture the image and we should see it work this time I am fairly sure. Pay attention to the Init Version: 20211107

      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

      M 1 Reply Last reply Nov 15, 2021, 9:06 AM Reply Quote 1
      • M
        madeyem @Sebastian Roth
        last edited by Nov 15, 2021, 9:06 AM

        @sebastian-roth

        With the new init (20211107) I re-captured from a SSD machine and was finally able to deploy to a HDD machine. So I guess the fixes can be implemented in the next official release. Thank you Sebastian!

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Nov 16, 2021, 12:47 AM

          @madeyem Thanks heaps for testing again and letting me know! As well thanks for your patience.

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

          149

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project