Deploy image not expanding partitions

[Tom Elliott]

@SuperMajestic Directly on the Host edit page, Host general.

There’s a text field called “Host kernel arguments”

[SuperMajestic]

@Tom-Elliott Perfect, I saw the option. Now, I installed Ubuntu 16.04 with GPT now. I’m going to test capture with this OS.

[SuperMajestic]

@Tom-Elliott Okey, I have in the debug mode.

The console waiting for me.

Before print this text:

osid=50
osname=Linux
mbrfile=
type=up
storage=******:/images/dev/
img=ubuntu1604
imgType=n
imgFormat=0
imgPartitionType=all
disks=/dev/sda
hd=/dev/sda

• press [Enter] key to continue

[Tom Elliott]

@SuperMajestic Press enter.

Press enter again.

Type:
fog

When you see the Disk information (after it starts shrinking) please take a pic and post here?

[SuperMajestic]

@Tom-Elliott


Other time, error

[Tom Elliott]

@SuperMajestic I don’t understand.

I see the pic, and it appears to be working.

[SuperMajestic]

@Tom-Elliott said in Deploy image not expanding partitions:

I don’t understand.
I see the pic, and it appears to be working.

In first pic. To the end show “Resizing… Failed”.

[Tom Elliott]

@SuperMajestic Yes, but this is before FOG has even started collecting the information.

We run e2fsck on each partition before it tries to resize it. So if there’s a problem on the disk, it will break things.

[SuperMajestic]

@Tom-Elliott Then… is problem of the disk? I don’t believe. In normal installations (by iso) I can install without problems.

Now, I going to change the disk drive by a 500GB and install a OS and test capture.

[Tom Elliott]

@SuperMajestic I don’t know what the issue is, I just know “of” the issue.

I have installed CentOS 7 MBR and GPT and can upload/deploy them just fine (though most of my work yesterday was around expanding extended partitions).

[SuperMajestic]

@Tom-Elliott Ok, then I have a important problem. Can’t use fog. I don’t understand because before I could capture a os and now not :-S

I changed de disk drive and deploy an image to test capture.

[Tom Elliott]

@SuperMajestic What do you mean?

I need information.

For example, deploy, boot into system.

Before running fog, as we know it will likely fail on the checking the partition area, run:

e2fsck -fp /dev/sd1

What does it show?

[SuperMajestic]

@Tom-Elliott The problem is in capture, not in deploy. Since yesterday any capture works with GPT.

Now, I going to install centos manually, without intervention of fog. And after, I try to capture again.

[SuperMajestic]

@Tom-Elliott said in Deploy image not expanding partitions:

k -fp /dev/sd1

Hello, I have the result :

http://imgh.us/result_6.jpg

[SuperMajestic]

@Tom-Elliott The new picture have all results of test all partitions.

[Tom Elliott]

@SuperMajestic the sda3 didn’t need to be done, only ext formatted volumes need to be tested.

[Tom Elliott]

for clarity, this was done before FOG ran, but after clean install, right?

[SuperMajestic]

@Tom-Elliott Yes, sorry, sda3 is a swap partition.

[SuperMajestic]

@Tom-Elliott

Yes.

1. Without fog, I installed fresh installation of Centos 7. I see that it works. The installation is finished correctly, and I see the root login.
2. I created the host on fog client and created the capture task.
3. Reboot the server with force pxe.
4. were Typed e2fsck -fp /dev/sda1
5. I’m waiting your instructions before run “fog” command.

[SuperMajestic]

@Tom-Elliott More info, I print fdisk result:

/dev/sda1 is a necessary partition to bios with GPT, type “BIOS boot”.
/dev/sda2 is a boot partition
/dev/sda3 swap
/dev/sda4 /