SOLVED Resizable partition is not expanding

[Hongyun]

Re: Hard drive resize is not expanding##### Server

• FOG Version: 1.3.5 RC 10
• OS: Red Hat Enterprise 6.8

Client

• Service Version:
• OS: Ubuntu 16 & Windows 7 dual boot

Description

Re: Hard drive resize is not expanding

Today I’m trying to download an image created with FOG 1.3.2 to another computer, and then I discovered the resizable partitions are not expanding. So I update the server to the latest dev version. Still get the same problem, then I upload a new image with the FOG 1.3.5, then downloaded it again, still get the same problem, but better, this time Windows partition seems expanded, but the Linux partiton is still only 22GB.

Here are the current partition table on the problem computer:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 519291975 52261960 24.9G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris

Here is the partition table on the computer I’m taking the image (they both have the same size hard drive):
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 765794303 298764288 142.5G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris

Here is the d1.partition (this used to be called d1.original.partitions under FOG 1.3.2) file on the FOG server:

cat d1.partitions

label: dos
label-id: 0x242a986c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 466823168, type=7
/dev/sda3 : start= 467030016, size= 298764288, type=83
/dev/sda4 : start= 765794304, size= 15626240, type=82

Here is the d1.original.partitions file created under FOG 1.3.2 on FOG server:

cat d1.original.partitions

partition table of /dev/sda

unit: sectors

/dev/sda1 : start= 2048, size= 204800, Id= 7, bootable
/dev/sda2 : start= 206848, size=466823168, Id= 7
/dev/sda3 : start=467030016, size=298764288, Id=83
/dev/sda4 : start=765794304, size= 15626240, Id=82

And I’m sure the resizable partition works perfectly under FOG 1.3.2.

Thanks,
Hongyun

[Hongyun]

@Tom-Elliott OK, I just downloaded the image to another computer, and it works. Thanks!

[Hongyun]

@Tom-Elliott I reinstalled FOG, and then uploaded an image, but it looks like the d1.partitions and d1.minimum partitions are still the same:

[root@foggy henn205u16win7]# more d1.partitions
label: dos
label-id: 0x242a986c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 466823168, type=7
/dev/sda3 : start= 467030016, size= 491393024, type=83
/dev/sda4 : start= 958423040, size= 18350080, type=82

[root@foggy henn205u16win7]# more d1.minimum.partitions
label: dos
label-id: 0x242a986c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 466823168, type=7
/dev/sda3 : start= 467030016, size= 49760206, type=83
/dev/sda4 : start= 958423040, size= 18350080, type=82

[Tom Elliott]

@Hongyun I really do appreciate it and I’ve ensured the files are fixed now.

[Hongyun]

@Tom-Elliott You are right, the two files are identical. I will try again. but will let you know the result tomorrow, I’m afraid I don’t have enough time to finish both upload and download before I leave for today. Thanks!

[Tom Elliott]

@Hongyun I hate to ask you to do this all again, but apparently something was awry from earlier.

Can you please re-run the installer and perform the same tasks again?

I know I keep asking, and I’m sorry. Just know I’m trying to get to the bottom of it. I’ll bet, currently, your d1.partitions and d1.minimum.partitions files are identical again/still.

[Hongyun]

@Tom-Elliott Yes, I already did this. Updated FOG, then changed the image from non-resizable to resizable, then upload the image, and downloaded to another computer. All works perfectly. Thanks again!

[Tom Elliott]

Want to give a shot on both upload and deploy (or did you already do this?)

[Hongyun]

@Tom-Elliott Yeah! It’s resized properly this time. Thank you so much for your quick response and quick fix!!!

[Tom Elliott]

Please re-run the installer and try again?

I know it’s a lot of back and forth, but it should work (hopefully).

At least the original and new sizes appear to be expanding on the same originating disk, I have not yet had the chance to test orig < smaller drive and orig > larger drive yet. Just same size disk for now. All appears to be working atleast in that regard.

[Hongyun]

@Tom-Elliott No, I didn’t change any partition settings, I only installed some updates, and then started the upload process. And this is a newly created image, I might have changed it to non-resizable, and then changed back to resizable, but these changes are on FOG WebGUI, before I issue the upload task.

[Tom Elliott]

Did you mess with the partition layouts before having fog capture it? It looks, to me, like this is the case. The d1.partitions should be different from the d1.minimum.partitions files. d1.partitions is the “original” layout, so if they are the exactly the same, then you will have some issues.

[Hongyun]

@Tom-Elliott previous numbers I gave you are all the result of fdisk command

$ cat d1.partitions
label: dos
label-id: 0x242a986c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 466823168, type=7
/dev/sda3 : start= 467030016, size= 49330360, type=83
/dev/sda4 : start= 765794304, size= 15626240, type=82

$ cat d1.minimum.partitions
label: dos
label-id: 0x242a986c
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 204800, type=7, bootable
/dev/sda2 : start= 206848, size= 466823168, type=7
/dev/sda3 : start= 467030016, size= 48807402, type=83
/dev/sda4 : start= 765794304, size= 15626240, type=82

[Tom Elliott]

@Hongyun What’s the contents of the new image’s:

d1.partitions and d1.minimum.partitions

[Hongyun]

@Tom-Elliott then in this case, it didn’t reapply the original partition table, I have to use gparted to resize the partition.

[Tom Elliott]

@Hongyun It does make changes, but it should reapply the original partition table.

[Hongyun]

@Tom-Elliott The first one is the original, the second one is the original after I upload image, upload shouldn’t make any changes on the partition, right?

[Tom Elliott]

@Hongyun said in Resizable partition is not expanding:

Here is the partition table before upload the image:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 765794303 298764288 142.5G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris
Here is the partition table on the base image computer after upload the image:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 516360375 49330360 23.5G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris
Here is the partition table on the new computer:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 383646 381599 186.3M 7 HPFS/NTFS/exFAT
/dev/sda2 383647 870205150 869821504 414.8G 7 HPFS/NTFS/exFAT
/dev/sda3 870205152 961146436 90941285 43.4G 83 Linux
/dev/sda4 961146438 976772677 15626240 7.5G 82 Linux swap / Solaris

I’m seeing changes on all three.

First one is the “original”
Second one is the shrunken state.
Third one is the “expanded” form. Linux looks expanded, and NTFS looks expanded. Is this not happening?

[Hongyun]

@Tom-Elliott There is something wrong. After I reinstalled FOG, uploaded a resizable partition, then downloaded the image to another computer. Both the base image computer and the new computer’s partition table got changed.

Here is the partition table before upload the image:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 765794303 298764288 142.5G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris

Here is the partition table on the base image computer after upload the image:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 467030015 466823168 222.6G 7 HPFS/NTFS/exFAT
/dev/sda3 467030016 516360375 49330360 23.5G 83 Linux
/dev/sda4 765794304 781420543 15626240 7.5G 82 Linux swap / Solaris

Here is the partition table on the new computer:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 383646 381599 186.3M 7 HPFS/NTFS/exFAT
/dev/sda2 383647 870205150 869821504 414.8G 7 HPFS/NTFS/exFAT
/dev/sda3 870205152 961146436 90941285 43.4G 83 Linux
/dev/sda4 961146438 976772677 15626240 7.5G 82 Linux swap / Solaris

When I define the image, I used Linux as the Operating System, but it looks like the partition table changes are only affecting the Linux partitions, should I choose a different Operating System for the image?

Now I feel regret, I should have upload a non-resizable image first, I didn’t expect it will change the partition table when uploading an image…

[Hongyun]

This post is deleted!