Hi,
> Attached is the log file
Thanks
ok, so on a GPT partitioned disk, there is a backup table at the
end of the disk. If you dump an image to a larger disk this backup
table is now no longer at the end of the disk and this is the
condition we check to identify that the disk geometry has changed.
The tool we use to check this is this:
sudo sgdisk --verify /dev/nvme0n1
Can you please call this on your system directly after deployment
without you having done any manual changes and send us the output.
Thanks much
I can imagine some possible reasons for the issue:
1. The sgdisk utility was not added to the initrd. This would happen
if your image doesn't install the gptfdisk package. Can you double
check if you install this package ? It is set as a requires to the
dracut-kiwi-lib which you surely have installed, but better check.
Please also call:
sudo lsinitrd /boot/initrd | grep sgdisk
2. The sgdisk verification sends unexpected results. We will
know from the above output
3. The way you deployed the image to that VMware disk has already
moved the backup table to the end of the disk. Actually I doubt
that your image file is 12GB of size, is that true, it looks
pretty big. Your image <type> definition does not specify a fixed
size, thus it gets just as big as needed to store the data.
As your rootfs is ~1GB I would assume your original image is ~1G
Can you therefore also call:
gdisk -l your-image-file.raw
of if you only have the .vmdk at hand:
qemu-img convert -f vmdk -O raw your-image-file.vmdk foo.raw
gdisk -l foo.raw
Such that we can see the original partition table before you
used it inside of VMWare