Error trying to restore GPT partition tables on multiple Dell machines



  • Dear,

    I’m very new to FOG imaging, so probably something went wrong on my side, but I can’t seem to figure out what exactly. I’ve already been troubleshooting for quite some time before opening this ticket.

    I’ve captured a new Windows10 Pro image (by following all the steps here: https://www.theitcave.com/post/561).
    I managed to get it working yesterday and deployed it to another type of Dell, but since that was the 1st image and I forgot quite some things, I decided to remove that one and create another one, which is what I tried today.

    I’m able to capture the image, but I can’t deploy it anymore, whatever I try, tried adjusting quite some settings in the BIOS and adjusting several settings for the image, nothing seems to help, I keep getting the following error message:

    Fog error.jpg

    Any idea what I’m doing wrong and how I can get to deploying again?
    Please let me know if you would need more information.
    Thanks for looking into this!



  • Ticket can be closed for me.
    I’ve captured a completely new image, before doing so, I’ve shrunk the disk, just to make sure.
    Deployment is now working as expected for me.
    Thanks for your assistance.



  • @Tom-Elliott

    label: gpt
    label-id: 2B93DFE7-2C81-4C8A-9000-BEF1E8E64AA3
    device: /dev/nvme0n1
    unit: sectors
    first-lba: 34
    last-lba: 1000215182

    /dev/nvme0n1p1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=1257976B-8CEF-4391-8FD8-815CAC3B26B6, name=“EFI system partition”, attrs=“GUID:63”
    /dev/nvme0n1p2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=D1113659-47AF-43F3-9E7A-BC08C44268CE, name=“Microsoft reserved partition”, attrs=“GUID:63”
    /dev/nvme0n1p3 : start= 239616, size= 3665920, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=295314FF-104B-45AB-A1F1-5CBFDC52CBB8, name=“Basic data partition”, attrs=“RequiredPartition GUID:63”
    /dev/nvme0n1p4 : start= 3905536, size= 59116948, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE33BD1E-F4CA-4E1A-91E7-FECA59FA53CA, name=“Basic data partition”


  • Senior Developer

    Can you paste the contents of your d1.minimum.partitions here?

    There may appear to be an error, but that’s not a bad thing in and of itself. The reason it failed to create any other partitions was because line 8 (the first partition) had met symbols that didn’t make sense (the .)

    Replacing all of the . with " should allow the partitions to at least get created.



  • @Tom-Elliott Ok, so I’ve replaced the . by ", but it doesn’t really change anything, I’m still getting exactly the same error when I run the commands.



  • @Tom-Elliott Good question, I just copy/pasted them from what you gave me, just noticed myself.
    I’ll edit those and see if that changes anything.


  • Senior Developer

    @vanopy Why are all the quotes listed as .?



  • @Tom-Elliott I believe so, this is how it looks:

    Fogminpart.PNG


  • Senior Developer

    @vanopy Is this what your d1.minimum.partitions file looks like?

    label: gpt
    label-id: 2B93DFE7-2C81-4C8A-9000-BEF1E8E64AA3
    device: /dev/nvme0n1
    unit: sectors
    first-lba: 34
    last-lba: 1000215182
    
    /dev/nvme0n1p1 : start= 2048, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=1257976B-8CEF-4391-8FD8-815CAC3B26B6, name="EFI system partition", attrs="GUID:63"
    /dev/nvme0n1p2 : start= 206848, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=D1113659-47AF-43F3-9E7A-BC08C44268CE, name="Microsoft reserved partition", attrs="GUID:63"
    /dev/nvme0n1p3 : start= 239616, size= 3665920, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=295314FF-104B-45AB-A1F1-5CBFDC52CBB8, name="Basic data partition", attrs="RequiredPartition GUID:63"
    /dev/nvme0n1p4 : start= 3905536, size= 59116948, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=EE33BD1E-F4CA-4E1A-91E7-FECA59FA53CA, name="Basic data partition"
    


  • @Tom-Elliott This is the output I’m getting:

    fog partprobe.jpg


  • Senior Developer

    @vanopy don’t try to deploy yet as it will still error out the same way.

    What’s output when you run:
    partprobe /dev/sda; fdisk -l /dev/sda



  • @Tom-Elliott Ok, so this is what I’ve done and got:

    Fog clear partitions.jpg

    Want me to try to deploy again now?


  • Senior Developer

    @vanopy I might suggest clearing all partition tables using sgdisk -Z /dev/sda

    Then try:
    (using the d1.minimum.partitions as I requested to be modified.)
    sfdisk /dev/sda < /images/winv10.3/d1.minimum.partitions

    From there can you get us the screenshot?



  • @Tom-Elliott @Sebastian-Roth Getting the following error when I ran through debug mode again:

    fog debug sda.jpg



  • This post is deleted!


  • @Tom-Elliott I’m out of the office now. Will be able to test again on Tuesday and will let you know the outcome


  • Senior Developer

    @vanopy I imagine the GPT Error is due to the d1.mbr file. We may have to manually run the process to get the image to push onto the machine.

    Can you redo the tasking into a debug mode again? (Goto create new tasking and just before confirming there will be a checkbox to “Schedule as debug”. Check this box)

    Then boot the machine you want to deploy too.

    My editing of the files doesn’t change the MBR file which I believe is where you’re seeing the error.\

    @Sebastian-Roth Theoretically, at least for the case of GPT, we shouldn’t need to apply the MBR file in order to build the partition data, correct? I know we’ve talked about this in the past and I really don’t know what we need the MBR for when we have the exact partition layout information in the d1.partitions and d1.minimum.partitions files. I’d think we could apply the minimum and do our adjustment calculations based of the new table.

    I’m sure there’s a reason we’ve kept mbr applying though I can’t see why at the moment.



  • @Tom-Elliott Just made the changes as requested, but I’m still getting the same GPT error when trying to deploy unfortunately. Any other ideas/suggestions?


  • Senior Developer

    @vanopy Would you be willing to try the things I suggested? I might suggest creating a backup of the current image just so you have the original ready to go.

    If you need help just let us know and I’m sure we can help.

    I’m not sure if this would work, but theoretically it would as it would place your data partition at the end of the disk and in line based on the sizes used.



  • @Tom-Elliott @Sebastian-Roth Really appreciate the help. Just let me know if you want me to make any change or if you want to test anything.


Log in to reply
 

374
Online

5.8k
Users

13.1k
Topics

123.3k
Posts