Image Size differences -Legacy/Uefi
Not sure if I am doing something wrong. I have being using fog to capture images, usually 250GB partitions on a 1TB disk configured for legacy bios. Installs are small linux based systems and the image sizes are usually about 10GB or so after capture. We have moved to UEFI and increased the partition size to the full disk. Linux again and using up about 10GB or so in the OS, however the catpure size is 1TB. I have always set the image as “resizable” but Im not sure why the difference?
@fatbunny I think I would take this approach. Recreate your master image using the smallest disk possible. Make sure the root lvm volume is the last one allocated on the disk. Capture with FOG it will still capture as RAW. Then using a post install script that detects either the image name or linux issue the LVM commands to extend the lvm volume to the size of the (new) disk and then extend the root lvm volume to the size of the lvm disk. Its a bit strange on how to handle it, but it should work.
The basic idea is to create your source image as small as possible then expand it post deployment.
FOG can’t interact at the moment with LVM disk structure so it copies it as RAW. If you want the single disk resizable recreate your linux disk using standard disk partitions then it will work as you expect with single disk resizable.
That makes sense. Thank you for that. It is showing as RAW but as this is a freepbx 15 system we are imaging, it has to use LVM unfortunately.
however the catpure size is 1TB
So when the partclone program is running (blue screen with bargraph of completion) towards the top 1/3 of the screen does it say RAW mode?
So you are using linux, but is your disk structured as standard partitions or are they LVM volumes. FOG can’t interact at the moment with LVM disk structure so it copies it as RAW. If you want the single disk resizable recreate your linux disk using standard disk partitions then it will work as you expect with single disk resizable.