Unable to deploy to smaller drive

[joeyberkovitz]

I created a Debian image from a 1TB hard drive with an image type of Single Disk - Resizable.
The final image size was 6GB.
When I tried to deploy the image to a 100GB machine, it said “No image file(s) found that would match the partition(s) to be restored”.
If I restore to a drive that’s the same size or bigger, then it works fine.
I’m running FOG version 1.4.4

[joeyberkovitz]

@george1421 Thanks. I’ll try the upgrade and see if that fixes it.

[george1421]

I just found this link in another thread: https://forums.fogproject.org/topic/10556/failure-to-expand-shrunken-resizeable-image-from-linux-machines It appears to discuss your problem too. The solution is to either upgrade to 1.5.0RC9 or keep working with 1.4.4 stable until 1.5.0 stable is released.

[Sebastian Roth]

@joeyberkovitz Ok then we need more information on the partition layout you have. Best of you upload d1.mbr, d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions so we can have a look. You should find all those files in folder /images/<IMAGENAME> in your FOG server.

As well you might schedule a debug deploy task for one of your hosts. When it brings you to the shell run command fog to start the deploy. After that it should drop you back to the shell again. Run gdisk -l /dev/sda. Please take a picture of the screen and post here as well.

[joeyberkovitz]

The source image isn’t LVM.
The 3 partitions on the source OS are as follows:
/dev/sda1 - EFI
/dev/sda2 - ext4 Linux Filesystem
/dev/sda3 - swap

[george1421]

Is the source image LVM based? AFAIK you can’t resize (or more correctly fog can’t) resize a disk that has been created as LVM. FOG should have copied it as raw partitions. You can test this by deploying to a disk bigger than the source disk. Does the new target use the entire disk or is it constrained to the same allications as the source disk?