Deploy image not expanding partitions

[SuperMajestic]

Thanks George. I will talk with the system administrator to update fog and will comment if solved the problem.

[SuperMajestic]

Hello there,

I followed the instructions of @george1421 and updated the client. My version now is Running Version 1.3.5-RC-10.

I have an image with Centos 6.8 with 4TB disk. Obviously in GPT.

FOG generates a file d1.partitions with:

label: gpt
label-id: 56098A51-6A69-44A8-A60C-C4227CC6DD25
device: /dev/sda
unit: sectors
first-lba: 2048
last-lba: 7814037134

/dev/sda1 : start= 2048, size= 168188, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=DA86ED3E-1241-4B9B-8189-7F4985D2EB2F
/dev/sda2 : start= 1026048, size= 16777216, type=0657FD6D-A4AB-43C4-84E5-0933C84B4F4F, uuid=9964DCF0-202A-425C-A9AB-CD60ABA2E7A4
/dev/sda3 : start= 17803264, size= 7796232192, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=FFA8A2C3-AD2E-4795-BC6F-1A24DA5A81BB

And d1.minimum.partitions:

label: gpt
label-id: 56098A51-6A69-44A8-A60C-C4227CC6DD25
device: /dev/sda
unit: sectors
first-lba: 2048
last-lba: 7814037134

/dev/sda1 : start= 2048, size= 168176, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=DA86ED3E-1241-4B9B-8189-7F4985D2EB2F
/dev/sda2 : start= 1026048, size= 16777216, type=0657FD6D-A4AB-43C4-84E5-0933C84B4F4F, uuid=9964DCF0-202A-425C-A9AB-CD60ABA2E7A4
/dev/sda3 : start= 17803264, size= 3448940, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=FFA8A2C3-AD2E-4795-BC6F-1A24DA5A81BB

My image in fog client are setted this:

Operating system: Linux
Image type: Single disk - Resizable
Partition: Everything
Compression: 6
Protected: Not checked
Image enabled: Checked
Replicate?: checked
Image manager: Partclone compressed.

I am trying to deploy the image in the same server with the same disk drive and not resizes.

Which can is the problem? Thank you!

[SuperMajestic]

Additionally, my d1.mbr content:

Disk d1.mbr: 17,5 KiB, 17920 bytes, 35 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Disposit. Inicio Start Final Sectores Size Id Tipo
d1.mbr1 1 4294967295 4294967295 2T ee GPT

[SuperMajestic]

I try to mark sda3 with fixed partitiond and same result. How can I to create fixed partitions, with the size of d1.partitions o d1.minimum.partitions?

When I install centos without gpt I can modify the file d1.minimum.partitions with the size that I want and works fine.

Thanks a lot

[Tom Elliott]

@SuperMajestic When did you update to RC 10?

[SuperMajestic]

@Tom-Elliott Hello, Exactly six days ago. The backup created in home directory fog_web_1.3.5-RC-10.BACKUP.

Thanks

[Tom Elliott]

@SuperMajestic Would you mind re-running the installer?

[Tom Elliott]

A good amount of last week was spent trying to fix issues found in the resize code.

Rerunning the installer should get you the latest inits.

[SuperMajestic]

@Tom-Elliott Bad news,

I installed Centos 7 in disk with GPT and I tryed to capture image and not works. This is the log:

And after of the error, I try to restart my server and for my surprise, I have an error in grub and my fresh installation don’t works. Before of capture task, I entered on my server, for to change password and other things. I restarted my server normally two or three times and starts correctly before of try capture.

What is occurring?

I have posted all information I have. If you want any more, no problem!

Thanks.

[SuperMajestic]

@SuperMajestic New installation of Centos 7. Before of capture, this is the partitions of the installation:

http://pastebin.com/S2245gUG

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