Failed to set disk guid (sgdisk-) (restoreUUIDInformation) error after deploying to new Lenovo laptops

[Brian Hoehn]

Server

• FOG Version: 1.4.4 Rev 6077
• OS: Ubuntu 16.04.3 LTS

Client

• Service Version: 1703
• OS: Windows 10

Description

When I push down my image made on my new Lenovo’s, ThinkPad T570 and Yogo 370. I get the error "Failed to set disk guid (sgdisk-) (restoreUUIDInformation). I don’t get the error when I push down my generic image, though that image is sda instead of nvme0n1.
I’m not sure if this is causing my issue of then not being able to license windows. the imaged machines say they cannot contact the KMS server but the machine that built the image works fine.

here is the d1.original.uuids for a lenovo image

/dev/nvme0n1 674471e0-83d1-4e08-8244-836a1ca3c0bf
/dev/nvme0n1p1 1:F0006F29006EF64E 1:e7603dce-a954-4023-b00a-c58dd298979e
/dev/nvme0n1p2 2:FC6F-347F 2:f269d22a-3486-41b8-90e0-7b8300e988be
3:5a103e14-fa6b-4517-810d-192e9b075d7a
/dev/nvme0n1p4 4:906E70206E700170 4:54a07814-8489-4b72-ab78-3ab94763142b

and here is a picture of the error screen

[ch3i]

@brian-hoehn said in Failed to set disk guid (sgdisk-) (restoreUUIDInformation) error after deploying to new Lenovo laptops:

Server

• FOG Version: 1.4.4 Rev 6077
• OS: Ubuntu 16.04.3 LTS

Client

• Service Version: 1703
• OS: Windows 10

Description

When I push down my image made on my new Lenovo’s, ThinkPad T570 and Yogo 370. I get the error "Failed to set disk guid (sgdisk-) (restoreUUIDInformation). I don’t get the error when I push down my generic image, though that image is sda instead of nvme0n1.
I’m not sure if this is causing my issue of then not being able to license windows. the imaged machines say they cannot contact the KMS server but the machine that built the image works fine.

here is the d1.original.uuids for a lenovo image

/dev/nvme0n1 674471e0-83d1-4e08-8244-836a1ca3c0bf
/dev/nvme0n1p1 1:F0006F29006EF64E 1:e7603dce-a954-4023-b00a-c58dd298979e
/dev/nvme0n1p2 2:FC6F-347F 2:f269d22a-3486-41b8-90e0-7b8300e988be
3:5a103e14-fa6b-4517-810d-192e9b075d7a
/dev/nvme0n1p4 4:906E70206E700170 4:54a07814-8489-4b72-ab78-3ab94763142b

and here is a picture of the error screen

https://forums.fogproject.org/topic/10447/failed-to-set-disk-guid-sgdisk-restoreuuidinformation-error-after-deploying-to-surface-pro-4

I think you have that problem.

[Brian Hoehn]

I did try the init files that tom said to try in that post and upgraded fog to the most current version. neither of those made a change. aside from the init files i downloaded didn’t list the args. I posted this in there and Sebastian asked me to open a new thread.

[Sebastian Roth]

@Brian-Hoehn Thanks for posting a new thread. I am not exactly sure what Tom fixed to make this work for those guys a few weeks ago. What I do know is that the very latest init files do change without notice. So probably those inits that they downloaded back then are not available anymore. Though I don’t know if or why this fix got lost.

@Tom-Elliott should be back soon.

[Brian Hoehn]

So on the d1.orginal.uuids if I change nvme0n1§ to sda it competes the task. I didn’t check if it still set the guids set in the file but the task completes and the PC boots just fine.
My licensing issue was because the time in the BIOS/UEFI wasn’t correct. I’m guessing that windows was using that as the trusted time and it was 12 hours out so the cert. was failing.

[Sebastian Roth]

@Brian-Hoehn Thanks for letting us know. We’ll surely fix the UUID issue as soon as Tom is back. I just don’t want to get into this without knowing what Tom was already doing. We’ll get this sorted!

Good to know that you got the licensing issue solved!

[JDnoble18]

@sebastian-roth said in Failed to set disk guid (sgdisk-) (restoreUUIDInformation) error after deploying to new Lenovo laptops:

@Brian-Hoehn Thanks for letting us know. We’ll surely fix the UUID issue as soon as Tom is back. I just don’t want to get into this without knowing what Tom was already doing. We’ll get this sorted!

Good to know that you got the licensing issue solved!

Just to let you know, we just got a batch of the t570 in as well and they do the same thing as the OP stated.

Image works fine, just have to clear out the task in fog.

Maybe its something with this particular model?

[Brian Hoehn]

@jdnoble18 I had it happen with my new HP desktop too… maybe something more likely that it has something to to do with nvme… but I’m sure if you change the nvme0n1§ to just sda it will complete the image process. The other issue besides it not clearing the task is that it doesn’t change the hostname of the device either.

[Tom Elliott]

@brian-hoehn Please install the latest RC version and see if you still have this error. I made this message a warning as opposed to an error now so you should still see this message, but you it shouldn’t prevent your machines from completing their tasks.

[JDnoble18]

@brian-hoehn Check the time on the imaged laptop and the fog server and make sure they match. I’ve had this problem before and it was very confusing until I changed the time or time zone inside the fog configuration web page.