Unable to Fog Image pulled from Large Size HDD to Small Size HDD
-
Fog Image created from Large size hard (for e.g 500 GB) does not get deployed on small size hard drive. I am using Fog 1.3.0 Beta build no. 6476.
-
In the settings for the image, is it set to a re-sizable image type?
If yes, under Images > List all Images, is the Image Size on Client smaller than the hard drive size you’re attempting to deploy it to? -
Did you select a resizeable image capture and deployment?
I can also suggest for your reference image, create it on a virtual machine with a small hard drive (smaller than you typical fleet hard drive). In my case I use a 40GB hard drive and then either let FOG or a diskpart script expand it to the full size of the target hard drive.
-
@george1421 But I never faced this issue in Fog 1.2.0. Is there anything which i need to make sure before pulling the image?
-
@moses Yes I always select Single Disk and Resizable option. Also my image size is maybe around 30 GB and my Target HDD is 256 GB but still giving error that Target HDD Boot Partition is smaller.
-
First you have to understand that really FOG 1.3.0 (when it is released) is really a different beast than 1.2.0. IMO it should have been 2.0, but that is for another time.
You need to make sure your image type is setup as Single Disk resizeable (Image Management->[ImageName]->Image Type)when you capture the image. The rest will be taken care of during image capture and deployment.
-
@chetansays said:
@moses Yes I always select Single Disk and Resizable option. Also my image size is maybe around 30 GB and my Target HDD is 256 GB but still giving error that Target HDD Boot Partition is smaller.
@Developers wasn’t this addressed?
-
@chetansays Please post the contents of /images/<img-name>/d1.partitions here in the forum. As well it would be helpful if you could post a picture and/or the exact text of the error message you see! We have worked on the resizable image scripts and you might want to upgrade to the very latest version to see if it works for you.
-
@Sebastian-Roth Content of d1.partitions
label: dos label-id: 0xc9acc7a0 device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 204800, type=7, bootable /dev/sda2 : start= 206848, size= 976564224, type=7
-
@chetansays said:
97656
What’s the output of the d1.minimum.partitions and d1.fixed_size_partitions file?
-
@Tom-Elliott d1.minimum.partitions:
label: dos label-id: 0xc9acc7a0 device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 204800, type=7, bootable /dev/sda2 : start= 206848, size= 63422216, type=7 -
@chetansays said: This is for d1.minimum.partitions while d1.fixed_size_partitions is blank
label-id: 0xc9acc7a0
device: /dev/sda
unit: sectors/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 63422216, type=7 -
@chetansays Do you mind updating first? You may need to reupload the image too, though I’m not 100% sure.
-
@chetansays Before reuploading add to the d1.fixed_size_partitions file.
Add 1 and save the file.
Try redeploying.
-
What Tom means by adding 1 to that file is essentially this:
echo "1" > d1.fixed_size_partitions(or use your favorite editor and write “1” into that file - without the quotes!). Then try deploying to the target machine again. Not need to re-upload for this test.As well, please run this deploy task in debug mode (just before creating the task check “Schedule task as a debug task”). To start the deploy use the command
fog. The step through and you should get back to a shell after the error. Then runsfdisk -d /dev/sdaand post a picture here. -
@Tom-Elliott Thank You Tom… When you asked for that file information I cross checked with old version Fog file and I saw that “1” was missing and I edited the file. After which it worked like a magic. I just saw your post and you were spot on. Thank you once again.
-
@Sebastian-Roth Thank You Sebastian. Really appreciate all developers effort here. FOG is wonderful tool. I simply love it. You guys are extremely responsive as well.
