FOG Partition Issues 1.5.0

[imagingmaster21]

I am having the same issue with the FOG partition resizing as in my previous post. In my previous post the issue was on a FOG Server with version 1.5.3 and updating the init files resolved the issue using the following link:
https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/master/88/artifacts/

We have a second FOG Server running 1.5.0, this has the same images on it and the same issue as mentioned in this post:
https://forums.fogproject.org/topic/13336/partition-resizing/5
I tried updating the inits on it and it did not break anything it just did not fix the issue of the partitions not resizing. Any ideas on what to do. I am thinking of updating the FOG server that is running 1.5.0 to the latest version, but I just want to know if there is anything else suggested before I do the update.

@Sebastian-Roth

[Sebastian Roth]

@imagingmaster21 said in FOG Partition Issues 1.5.0:

We have a second FOG Server running 1.5.0, this has the same images on it and the same issue as mentioned in this post:

Are you absolutely sure it’s the exact same images? I mean, do you replicate the image files from one server to the other? Just want to make sure as partition layouts can be quite different although they might look similar at first.

Please post the contents of the following three files from the image on your 1.5.0 server: d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions

Updating to the latest version is still a good idea!

[imagingmaster21]

@Sebastian-Roth They are replicated exactly the same as on the 1.5.3 server.

Here is the image files:
d1.partitions

label: gpt
label-id: 066202D1-4FDA-44C2-A0A0-3C26A816B87E
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=3366A936-7B65-43E1-AFDF-9DE4F8FE13A7, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=0DBFD8B3-44AC-4600-926D-FDFB469EFF2A, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=BC00D195-83B5-4B15-BFF8-DDCEC9B3ADFF, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=   498855936, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=890554EA-E1AB-4D7F-8C9D-7F8C83FA2A62, name="Basic data partition"

d1.minimum.partitions

label: gpt
label-id: 066202D1-4FDA-44C2-A0A0-3C26A816B87E
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=3366A936-7B65-43E1-AFDF-9DE4F8FE13A7, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=0DBFD8B3-44AC-4600-926D-FDFB469EFF2A, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=BC00D195-83B5-4B15-BFF8-DDCEC9B3ADFF, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1261568, size=    79997904, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=890554EA-E1AB-4D7F-8C9D-7F8C83FA2A62, name="Basic data partition"

d1.fixed_size_partitions

:2:3:1

[Sebastian Roth]

@imagingmaster21 Nice, here we have a perfect example. You see that both files are similar but there is one important difference. The size= of partition number 4 is smaller in the p1.minimum.partitions file. What this means is that FOG is able to deploy this partition layout to a smaller disk. FOG would Not be able to do that if those two files where identical.

So I am still wondering hob you came to the idea those two files need to be identical?!?

[imagingmaster21]

@Sebastian-Roth No clue, so what do I need to fix something in these files, I never really messed with any of the code in these files after capturing the image. Is there something specific I need to change? Please let me know I am trying to follow.

[Sebastian Roth]

@imagingmaster21 said:

I am having the same issue with the FOG partition resizing as in my previous post.

We need the exact error you are seeing this time to be able to help. From what you describe I think you are having a different issue than what you had last time on your other server.

[imagingmaster21]

@Sebastian-Roth
So when you image the image it and go into disk management it has the following when imaging to a 500 gb drive HHD…

• Recovery:
  499 MB NTFS
  Healthy OEM Partition

• 100 MB Healthy (EFI System Partition)

• C:\ 118 gb ntfs healthy boot page file crash dump, primary partition

• 346.52 gb unallocated

Also one thing I noticed on this FOG Server is after it images it gives the following warning on the machine being imaged:
Failed to set disk guid (sgdisk -U) restoreUUIDinformation
Args passed: /dev/nvme01n/images/Win10_Student_1809_v4/d1.original.uuids 1 /images/Win10_Student_1809_v4

It displays this warning and the machine reboots, only thing to appear wrong with machine is incorrect partitions.

Let me know if there is any additional info you need.

[imagingmaster21]

@Sebastian-Roth

Updating the FOG server to the latest image appears to have resolved the issues. Good thing is did not have to modify anything after the update all models appear to be imaging successfully.