Unsolved Hard drive space issues when deploying image
-
Hi
Recently ran into this problem. I captured my image as per normal but went to deploy it to a new 120GB SSD it has shrunk the hard drive to 55GBI never changed resizing options before. What should I do?
What has went wrong? Help!!
-
@CJR_ie What version of Fog are you using?
-
@CJR_ie said in Hard drive space issues when deploying image:
it has shrunk the hard drive to 55GB
What do you mean by that? Do you refer to the “Image Size: ON CLIENT” figure of 55.90 GiB? That is just roughly the amount of data stored on the client and is more or less just the lowest limit of disk size that image can be deployed to. But if you deploy that resizable image to a 120 GB SSD it should expand to the full 120 GB. Please post a picture of windows disk manager after you deployed that image to a machine.
-
@Wayne-Workman Running Version 1.4.4
-
-
-
@CJR_ie Please post the contents of
d1.partitions
,d1.original.partitions
andd1.fixed_size_partitions
- files are in/images/IMAGENAME
on your FOG server.Is upgrading to the latest FOG version 1.5.4 an option for you? If it turns out to be an issue with 1.4.4 we won’t be able to help properly as we can’t support back porting fixes to older versions.
-
d1.partitions:
label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 117024256, type=7d1.original.partitions:
/dev/sda2 ntfsd1.fixed_size_partitions:
:1:2 -
@CJR_ie Here you go. FOG detects your windows system partition to be fixed as well and therefore does not expand it on deployment. Edit the file
d1.fixed_size_partitions
by hand using a text editor and make it read:1
Then schedule a new deploy task for your host and it should expand to the full SSD size properly.