@Sebastian-Roth I actually forgot to grab the df -h output before resizing things, but after resizing and re-capturing, it seems to be deploying correctly without consuming all the free space. So this can be closed now I think, at least as far as it affects me. Thanks for the assistance.
Latest posts made by bordercollie
-
RE: First partition is not resizing when deploying an image
-
RE: First partition is not resizing when deploying an image
@Sebastian-Roth Thanks. I suppose it could be because of the way the image was captured - it was originally created as a kvm virtual machine, captured from there, and deployed to a laptop, but there was a problem and the original image was lost, so after making necessary adjustments it was re-captured from that laptop. I suppose the storage issue could stem from that, since it wasn’t “real” free space on the vm (at least, insofar as the unused space was not actually taking up any space on the physical disk).
The server is at work, I’ll get that output tomorrow and post it here. But something I thought of as I read your reply, the reference laptop I’m now using to build the image, I can just manually resize sda1 on that that and capture it again. Would that solve this whole problem?
-
First partition is not resizing when deploying an image
I see similar problems in several places but every one that I’ve looked at didn’t have any information that I was able to apply to my situation.
This is FOG 1.5.4, running on a CentOS 7 server, trying to deploy a Fedora 28 image (with non-LVM partitioning).
I captured the image and it will deploy and works just fine. But when it deploys, /dev/sda1 (/ on the image) is not resizing at all - it’s almost completely full, with something like 100 mb free (this is actually smaller than was on the machine it captured from). /dev/sda2 (/home) is being resized to take all the remaining space.
What I would like is for one of two things - either /dev/sda1 increases in size proportionately to /dev/sda2, or I would like to give /dev/sda1 a fixed size of say 50GB and have the remainder of available space on /dev/sda2. Either way is fine, whichever can be accomplished most easily.
Currently, on the fog server my d1.fixed_size_partitions file is empty, and the other d1.* files are as follows:
## d1.minimum.partitions label: dos label-id: 0x9f99f7ab device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 43748073, type=83, bootable /dev/sda2 : start= 390707200, size= 4852470, type=83
## d1.original.fstypes /dev/sda1 extfs /dev/sda2 extfs
## d1.partitions label: dos label-id: 0x9f99f7ab device: /dev/sda unit: sectors /dev/sda1 : start= 2048, size= 44439108, type=83, bootable /dev/sda2 : start= 390707200, size= 1562817536, type=83