Unable to restore GPT partition tables on one image


  • I have an image that seems to be a little bit and miss if it works. On some of my newer and older machines it will fail here. But on a our desktops and one model of laptop. It works great. Is there something that these specific laptops don’t like?

    alt text

    I see it is complaining about partition sizes, Do they not resize for NVME drives or something? The image is set to resizable.

    alt text

    Thank you!

  • Senior Developer

    @cammykool said in Unable to restore GPT partition tables on one image:

    this is the stuff that broke after that init move.

    That has nothing to do with the init change. The version information in the FOG web UI is pulled from the fogproject.org server and I would guess either there was a connection issue or your network admin restricted access to this URL.


  • @sebastian-roth said in Unable to restore GPT partition tables on one image:

    @cammykool said in Unable to restore GPT partition tables on one image:

    But now fog is freaking out saying it’s our of date!

    What do you mean by that?

    fog.PNG

    this is the stuff that broke after that init move. I am at my other district today that also has fog.


  • @sebastian-roth after I replace those init files it suddenly can’t figure out if it’s up to date or not. Under the fog settings page it says it’s not and on the home page where it tells you version numbers and things it says can’t connect to server

  • Senior Developer

    @cammykool said in Unable to restore GPT partition tables on one image:

    But now fog is freaking out saying it’s our of date!

    What do you mean by that?


  • @sebastian-roth it seems to be doing a lot better! But now fog is freaking out saying it’s our of date! Lol. Before I leave my other district I’m going to upgrade the inits there too.

  • Senior Developer

    @cammykool said in Unable to restore GPT partition tables on one image:

    ill try the new init but there are those files anyways, Sorry! i only work at this school on tuesdays and wednesdays at the moment! and yes the machines were ordered at the same time and are identical

    Definitely download the latest inits because this partition layout won’t be resized to fit on a smaller size disk with that older inits! Though the new inits should be able to handle this and shrink properly.

    As I said, you need to re-capture the image using the new inits!


  • @sebastian-roth

    label: gpt
    label-id: 2ECDE8B1-0B1B-4158-9F5C-8771C1B07069
    device: /dev/sda
    unit: sectors
    first-lba: 34
    last-lba: 976773134
    sector-size: 512
    
    /dev/sda1 : start=        2048, size=      389120, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=0ED2601D-0323-4288-9475-00776EA0ABCC, name="EFI system partition", attrs="GUID:63"
    /dev/sda2 : start=      391168, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=0A25E7A4-56D5-4CE1-9C4D-9078F6F34C8C, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/sda3 : start=      653312, size=    81925234, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=D43DEA4E-4959-479C-B88E-A79AF1BFE763, name="Basic data partition"
    /dev/sda4 : start=   971900928, size=     2027520, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=3A6A781D-0FBE-4D4F-9D48-6BEC8E33F5DA, attrs="RequiredPartition GUID:63"
    /dev/sda5 : start=   973928448, size=     2844672, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=929B9739-0DB2-47F8-8234-1B6CE3324382, attrs="RequiredPartition GUID:63"
    
    

    that is d1.minimum

    label: gpt
    label-id: 2ECDE8B1-0B1B-4158-9F5C-8771C1B07069
    device: /dev/sda
    unit: sectors
    first-lba: 34
    last-lba: 976773134
    sector-size: 512
    
    /dev/sda1 : start=        2048, size=      389120, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=0ED2601D-0323-4288-9475-00776EA0ABCC, name="EFI system partition", attrs="GUID:63"
    /dev/sda2 : start=      391168, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=0A25E7A4-56D5-4CE1-9C4D-9078F6F34C8C, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/sda3 : start=      653312, size=   971247616, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=D43DEA4E-4959-479C-B88E-A79AF1BFE763, name="Basic data partition"
    /dev/sda4 : start=   971900928, size=     2027520, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=3A6A781D-0FBE-4D4F-9D48-6BEC8E33F5DA, attrs="RequiredPartition GUID:63"
    /dev/sda5 : start=   973928448, size=     2844672, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=929B9739-0DB2-47F8-8234-1B6CE3324382, attrs="RequiredPartition GUID:63"
    
    

    d1

    ill try the new init but there are those files anyways, Sorry! i only work at this school on tuesdays and wednesdays at the moment! and yes the machines were ordered at the same time and are identical

  • Senior Developer

    @cammykool I found there was an issue in the current inits that would cause the issue (partitions not moved). Should be fixed now. 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).

  • Senior Developer

    @cammykool Looks like something is still preventing FOS from properly shrinking and moving the last partition(s) forward to make it fit onto a smaller size disk.

    I have now tried pushing it to a machine of the exact same model and make as the original and I’m getting the same GPT issues. Using the newer init.

    Does the “exact” same model have the exact same disk model as well? Disks labeled as 250 GB for example are not all the exact same sector count and that would kind of explain the issue if the deploy host disk is just a tiny bit smaller.

    Again we need to find out why it doesn’t shrink to a way smaller disk size. Please post the contents of the text files /images/DellMaster/d1.minimum.partitions and /images/DellMaster/d1.partitions here in the forums.


  • @sebastian-roth I’m sorry. I’m all over the place. We figured that to be a dead drive. IO issues. But I’m still having a GPT partition issue. I rebuilt a brand new image from scratch using the hardware of our most modern computer in the district. Build it out perfectly and then had it pushed to an older machine which worked great. I have now tried pushing it to a machine of the exact same model and make as the original and I’m getting the same GPT issues. Using the newer init

    alt text

  • Senior Developer

    @cammykool said in Unable to restore GPT partition tables on one image:

    Now the img push seems to be failing but I’m not sure if it’s related

    What do you mean by “img push”? Th picture looks like you are capturing an image - I would call that “img pull” rather than “push”.

    I am not sure on why it fails at this stage. But what’s interesting in the picture you posted is that we see it is using partclone.imager on partition number 4. Why is that I wonder? Shouldn’t be the case for a normal Windows 10 installation I suppose.

    Please take a look at the text file /images/dev/28f10e170c67/d1.minimum.partitions and post the contents of that file here in the forums.


  • @sebastian-roth we got that issue solved by me following a guide about changing permissions in the images folder. That fixed it. This is an older machine with an integrated nic. Now the img push seems to be failing but I’m not sure if it’s related. alt text

  • Senior Developer

    @cammykool said in Unable to restore GPT partition tables on one image:

    looks like after doing that it’s struggling to find machines by Mac at the white fog screen. This is after registering it. Twice. It’s in the fog UI but it doesn’t see it when booting

    Changing the inits as suggested cannot cause the issue you describe now. Registered hosts (as seen in the web UI) not showing as registered in the PXE boot menu is usually caused through a USB network adapter that is passing through the internal device MAC address (which is different to the network adapter MAC address). Search the web or our forums for “pass through MAC” to find more information in this topic.


  • @sebastian-roth looks like after doing that it’s struggling to find machines by Mac at the white fog screen. This is after registering it. Twice. It’s in the fog UI but it doesn’t see it when booting

    alt text


  • @sebastian-roth 21h1 iirc ill do that now.

  • Senior Developer

    @cammykool Which version of Windows 10 so you use? 1909, 2004, 20H2?

    Since 2004 the partition layout changed in a way that prevents the image from being resized for deployment to smaller size disk than it was captured from.

    This issue is solved if you use the latest dev-branch inits. Manually download inits (64 bit and 32 bit) and put into /var/www/html/fog/service/ipxe/ on your FOG server. Rename the existing files as backup instead of overwriting!

    Now you need to re-capture the image again. Maybe even create a new image definition for this to not overwrite your existing image files as a backup. Assign the new image to the host you capture from and schedule the task.

    This image captured with the new inits is probably deploying fine to devices with smaller disks as well. If not, let us know.

241
Online

8.4k
Users

15.2k
Topics

142.6k
Posts