Single disk, resizable - failed to set disk guid

[dylan123]

Server

• FOG Version: 1.4.0-RC-4
• OS: Ubuntu

Client

• Service Version:
• OS:

Description

Hey guy, created an image of a surface pro 3 60gb as a single disk, resizable. Pushed it to a 250gb surface pro 3 and I get an error at the end. The surface pro 3 then boots up fine and appears to work so I’m mainly just curious as to what the following error actually means (also means the task remains in the system because of the error) -

Not a huge problem as I can create and use the ‘not resizable’ option (would be nice for the 1-2 60gb Surface Pros we have). I was just wanting to know what this problem actually means as the computer I deployed the image to appears to be working fine.

[Wayne Workman]

It means the UUID from the reference partition could not be applied to the device’s partition you deployed to. I’m surprised it boots.

@Tom-Elliott an alternative if sgdisk fails is

tune2fs /dev/nvme0n1 -U `uuid`

[Tom Elliott]

@dylan123 Does your image have the d1.original.uuids file? if so, what’s the contents of that file?

[dylan123]

Hey @Tom-Elliott, see below for the content of that file -
/dev/sda dcfabb9e-4507-415e-b9a9-e437017df63b
/dev/sda1 1:0C86C94F86C939CA 1:9c90a090-937d-4c9b-9a25-0381f463b590
/dev/sda2 2:6CCA-8BF5 2:7e69ccb9-b499-4bf5-8528-293b71e42988
3:2de320a9-99b6-4191-aeeb-1c15e96fae1d
/dev/sda4 4:CC34D93B34D9296A 4:b1911679-d848-4e8b-82fc-98616b55452e

[Tom Elliott]

@dylan123 So the issue, if you’d like it fixed for now (I’ll relook at this code though).

Can you open the file, and add the /dev/sda components?

In other words make the file read as:

/dev/nvme0n1 dcfabb9e-4507-415e-b9a9-e437017df63b
/dev/nvme0n1p1 1:0C86C94F86C939CA 1:9c90a090-937d-4c9b-9a25-0381f463b590
/dev/nvme0n1p2 2:6CCA-8BF5 2:7e69ccb9-b499-4bf5-8528-293b71e42988
3:2de320a9-99b6-4191-aeeb-1c15e96fae1d
/dev/nvme0n1p4 4:CC34D93B34D9296A 4:b1911679-d848-4e8b-82fc-98616b55452e

[Tom Elliott]

I’ve updated the code base in hopes of properly generalizing the base code to get the UUID information.

Could you test deployment again after downloading the latest inits?

sudo mv /var/www/fog/service/ipxe/init{,_orig}.xz
sudo mv /var/www/fog/service/ipxe/init{,_orig}_32.xz
wget -O /var/www/fog/service/ipxe/init.xz https://fogproject.org/inits/init.xz
wget -O /var/www/fog/service/ipxe/init_32.xz https://fogproject.org/inits/init_32.xz

[Tom Elliott]

Here’s a look (if anybody wants to review logic process/give potential better ideas):

https://github.com/FOGProject/fogproject/commit/c327be5ff7936f361036b1e362d6ce011d4a6ed5

The applySgdisk and restoreSgdisk functions weren’t used anywhere in the code since sfdisk installed on the init’s can save and use the sfdisk from a gpt styled disk now.

[dylan123]

@Tom-Elliott said in Single disk, resizable - failed to set disk guid:

@dylan123 So the issue, if you’d like it fixed for now (I’ll relook at this code though).

Can you open the file, and add the /dev/sda components?

In other words make the file read as:

/dev/nvme0n1 dcfabb9e-4507-415e-b9a9-e437017df63b
/dev/nvme0n1p1 1:0C86C94F86C939CA 1:9c90a090-937d-4c9b-9a25-0381f463b590
/dev/nvme0n1p2 2:6CCA-8BF5 2:7e69ccb9-b499-4bf5-8528-293b71e42988
3:2de320a9-99b6-4191-aeeb-1c15e96fae1d
/dev/nvme0n1p4 4:CC34D93B34D9296A 4:b1911679-d848-4e8b-82fc-98616b55452e

Hey @Tom Elliott, tried the above code and that worked perfectly!

Will download the new init’s as suggested and see if that works also, thanks.