Failed to set disk guid ...

[Sebastian Roth]

@kratkale We are aware of this issue but still need more information to be able to solve this. Can you please schedule a debug capture on your master client (not the one you tried to deploy to here but your master client). When you get to the shell run blkid -po udev /dev/sda | grep "PART_TABLE_UUID" and sfdisk -d /dev/sda | grep "label-id" and post outputs here.

[Sebastian Roth]

@kratkale As well please post the contents of the text file /images/M910_201901131240/d1.partitions here.

[kratkale]

@Sebastian-Roth said in Failed to set disk guid ...:

/images/M910_201901131240/d1.partitions

root@FOG:/home/kratkale# cat /images/M910_201901131240/d1.partitions
label: dos
label-id: 0x426ff929
device: /dev/nvme0n1
unit: sectors

/dev/nvme0n1p1 : start=        2048, size=     1124352, type=7, bootable
/dev/nvme0n1p2 : start=     1126400, size=   498989056, type=7

[kratkale]

@Sebastian-Roth
Now I have restored on my Setup PC the Image with Clonzilla: Windows 10 with sysprep

the Windows 10 system Disk is: nvme0
the second Disk hold just data for installation: sda (e.g. Firefox, … )

sda - Data disk: /dev/sda /dev/sda1

+) blkid -po udev /dev/sda | grep “PART_TABLE_UUID”
no output
+) sfdisk -d /dev/sda | grep “label-id”
The size of this disk is 2.7TiB (3000592902016 bytes). DOS partition table format cannot be used on drives for volumes lager than 2199023255040 bytes for 512-byte sectors. Use GUID partition table format (GPT)
system Disk - to clone

nvme0 - Windows System disk: /dev/nvme0 /dev/nvme0n1 /dev/nvme0n1p1 /dev/nvme0n1p2

+) blkid -po udev /dev/nvme0n1 | grep “PART_TABLE_UUID”
no output
+) sfdisk -d /dev/nvme0n1 | grep “label-id”
no output

[Tom Elliott]

Do we need to set guid if layout is mbr?

[Sebastian Roth]

@Tom-Elliott No we don’t from my point of view. Just pushed a fix for that. The inits should be build by tomorrow (or later this day your time).

[Sebastian Roth]

@kratkale New init files are available. Manually download those (32 bit and 64 bit) and put in /var/www/html/fog/service/ipxe/ on your FOG server.

Please let us know if the warning is gone with those inits.

[kratkale]

@Sebastian-Roth
sorry no success …

[Sebastian Roth]

@kratkale Yeah, just saw that as well. Please go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000.

[kratkale]

@Sebastian-Roth said in Failed to set disk guid ...:

275000

yes it works

Ave. Rate: 11.36GB/min
Thats much more faster than clonzilla live with internal HDD?

Perfect - I love the fogproject.

Do you think upload will also be now faster? There I’ve a rate of about 2.8GB/min …

(Single Computer)

[Sebastian Roth]

@kratkale said in Failed to set disk guid ...:

Do you think upload will also be now faster? There I’ve a rate of about 2.8GB/min …

There is no general answer to this. It all depends on the hardware you have. Bit CPU and lots of RAM will make compression faster. The more you can compress, the less data needs to be transfered to the FOG server and written to the disk there…

[kratkale]

@Sebastian-Roth
do you need also a multicast session?

[Sebastian Roth]

@kratkale You can give it a try but I am fairly sure there won’t be an issue with that. Marking as solved.

[kratkale]

@Sebastian-Roth Thank you so much …

[Sebastian Roth]

@kratkale You are welcome. It’s good to have people around who rapidly test things that we push out. Thanks to you!