Deploy image not expanding partitions

[Tom Elliott]

@SuperMajestic Can you show us the contents of both the d1.partitions and d1.minimum.partitions files in regards to this?

It’s starting to sound more and more like the problem is specific to the 4tb disk, like it’s not liking the math on such large numbers. The integers appear to be fine from a purely mathematical standpoint but I don’t know.

As far as why it’s not picking up the disk? I don’t know. I have now tried replicating the specific problem with both mbr and gpt partitioned disks and can’t seem to get the repeat of the issue. This almost sounds like there’s an issue with the partition layout itself?

I was made aware of an upload issue which was corrected for. That said, most of the work I did yesterday was trying to figure out the MBR layout for extended partitions. From what I can see this is working as expected now. I didn’t get a chance to re-test the GPT upload and deploy, but the majority of the work was in dealing with extended and logical partitions. It’s most likely still got some things to work out. That said, GPT should work.

If you can start whatever tasking it is but for the host in the tasking add the ‘host kernel args’ of:
ismajordebug=1 isdebug=yes and start the client?

This will drop the system into a terminal. This is a debug sessions, and should step you through the process of what’s going on waiting for you to prompt for information.

With ismajordebug on it will also display before/after information about what’s being applied to the disk in regards to sizing. This will be the most important bits of information we need.

[SuperMajestic]

@Tom-Elliott Can’t show content files because not generated. I believe that are not generated by the error in capture.

How I use these options (ismajordebug=1 isdebug=yes)?. When I create the capture task only see option “Schedule task as a debug task”.

[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.