Solved Problem with the resize (expanding) on a hard drive

[Sebastian Roth]

@loutrage For some reason FOS (FOG Linux OS) detects both your Windows partitions as non-resizable. Sure you could use a snapin to expand the drive after deployment. But for your very straight forward partition layout we should also be able to find out why it detects it as non-resizable in the first place. Quite possible we can find an fix this so the snapin is not needed.

Please schedule a debug capture task (as a normal capture task but before you click create in the web UI there is a checkbox for debug), boot up the host and hit ENTER twice to get to the shell. There you run parted -s /dev/sda print - take a picture of the output on screen and post here. You don’t need to actually start the capture task after taking the picture. You can cancel the task in the web UI and switch off the host.

My guess is that your drive has some flag set that FOS detects as “problematic”.

[loutrage]

@Sebastian-Roth

Thank you for the answer ! Here is the content of the 3 files :

root@fog:/images/2019-09-23# cat d1.partitions
label: dos
label-id: 0x7d78d5ad
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1124352, type=7, bootable
/dev/sda2 : start=     1126400, size=    82757632, type=7
root@fog:/images/2019-09-23# ls

root@fog:/images/2019-09-23# cat d1.minimum.partitions
label: dos
label-id: 0x7d78d5ad
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1124352, type=7, bootable
/dev/sda2 : start=     1126400, size=    82757632, type=7

root@fog:/images/2019-09-23# cat d1.fixed_size_partitions
:1:1:2

[Sebastian Roth]

@loutrage We need some more information from you. Go to your FOG server’s image directory (/images/2019-09-23), grab the contents of the following text files: d1.partitions, d1.minimum.partiitons and d1.fixed_size_partitions and post here.