Deploy image not expanding partitions
- FOG Version: 1.3.5-RC-3
- OS: Ubuntu
- Service Version:
I have a problem when I deploy a image in my servers. All is correct but not expand the partitions. The image is a Centos 6.8 with GPT.
Initially, I install the centos in a 4TB disk. Now, I try deploy the image in a 500GB disk or 4TB disk but this not expand.
What is the problem? Thanks!
@SuperMajestic Yes please.
I believe the issue was the start point was trying to be shifted around.
The resizing, at least for linux systems, has to try to get the data first. We have to see how far it can be shrunk.
Hello, I downgrade to stable version (Running Version 1.3.4 SVN Revision: 6066) and don’t capture.
The error isn’t in resizing, is in checking.
Do you want I upgrade fog to latest version again?
@SuperMajestic The capture logic hasn’t changed. Would you mind re-running the installer though?
Another dev found that there were two issues accidentally added to the capture. (But have been fixed for a bit).
The start position during our resizing was accidentally being shifted around (which could cause what you’re describing). I’ve tested capturing both gpt and mbr, and all is working from my side. I’ve tested deploying both gpt and mbr now and am fairly sure I’ve fixed the issues with the resizing now too.
So please, re-run the installer and hopefully things will go better.
@Tom-Elliott it’s incredible Now can’t capture nothing. gpt and mbr not works. Nothing :-S. Error in resizing sda1 even in two different hosts.
This is the content of generated d1.partitions
This is the last test. Now fsck is correct but crash in resizing sda2 (/boot).
@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
- 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.
- I created the host on fog client and created the capture task.
- Reboot the server with force pxe.
- were Typed e2fsck -fp /dev/sda1
- I’m waiting your instructions before run “fog” command.
@Tom-Elliott Yes, sorry, sda3 is a swap partition.
for clarity, this was done before FOG ran, but after clean install, right?
@SuperMajestic the sda3 didn’t need to be done, only ext formatted volumes need to be tested.
@Tom-Elliott The new picture have all results of test all partitions.
k -fp /dev/sd1
Hello, I have the result :
@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 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?
@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.
@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).
@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.
@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.