FOG Firmware and Partitioning Error

[Sebastian Roth]

@byu13 Have you tried shrinking the image (resolution, size) und upload again?

[byu13]

@Sebastian-Roth 

I have. I get the same error.

[byu13]

@byu13 

[byu13]

[george1421]

@byu13 Ok first do you have a non-standard disk layout?

From the fog host server can you run the results of this command and post the results here?

cat /images/Windows10_SysPrep/d1.partitions
cat /images/Windows10_SysPrep/d1.fixed_size_partitions

As for the d1.mbr would you upload that to a file share site, make it world readable and then post the link here. The developers can look at the file to see the structure of the disk. Applying the disk structure is where the process is failing.

[byu13]

@george1421

#  cat /images/Windows10_SysPrep/d1.partitions
label: gpt
label-id: 04B46A91-D22D-4B27-A02D-A8C20C8DE04F
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 1000215182

/dev/nvme0n1p1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E73101A3-6DA2-49A2-BC3B-C2BE10A4FD42, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=B2927C52-467C-49FF-8246-0496CE6309EB, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=      239616, size=   998936693, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=DABA19A8-9D61-49B6-AEED-51A4C502BE5F, name="Basic data partition"
/dev/nvme0n1p4 : start=   999178240, size=     1034240, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=03CC494C-3F3C-4FD5-98C8-30FE897D3627, attrs="RequiredPartition GUID:63"

# cat /images/Windows10_SysPrep/d1.fixed_size_partitions
1:2:4

[byu13]

@george1421 It is just a standard disk layout.

[byu13]

@george1421 https://drive.google.com/file/d/1TF07wv_1olwDD2zSRR_STgaTKja2PdPo/view?usp=sharing

[george1421]

@byu13 said in FOG Firmware and Partitioning Error:

@george1421 It is just a standard disk layout.

So just to be clear, you are copying an nvme structured disk to a different computer with a sata attached disk?

[byu13]

@george1421 Sata. Just your good ole regular sata hard drive.

[george1421]

@byu13 We may need to get a developer’s input, but I would think there might be an issue trying to deploy a nvme disk structure (source) to a sata disk (target). I’m not sure if the structure is compatible.

[byu13]

@george1421 I have deployed to a regular sata disk just today and it worked fine.

[george1421]

@byu13 So can you identify if its the image or the physical disk that might be at fault?

i.e. this image deployed just find to computer X but not computer Y where computer X and computer Y are exactly the same?

Or I can deploy image B to computer X and Y but image A will not deploy to computer Y?

Is the target drive (in this specific case) exactly the same size or larger than the source image?

As you can see there are a number of things that might cause the format to fail to load on the target drive.

[Sebastian Roth]

@byu13 It’s interesting it doesn’t print out more details when it fails on the sgdisk call. I though I had added some more debug output especially for this case as we get this every now and then… Maybe it’s just further up the screen. Anyhow.

Please schedule another deploy task for this machine but make sure you enable the checkbox for debug just before you hit the create task button. Boot the host, hit ENTER twice to get to the shell and start deploying using the command fog. Step through till you hit the error again which should bring you back to the command shell. Then run this manually: sgdisk -gl /images/Windows10_SysPrep/d1.mbr /dev/sda, take a picture of the screen and post here.

With that partition layout your destination disk needs to be at least 477 GB (last-lba: 1000215182 * 512 byte sector size / 1024 / 1024 / 1024)!