Not enough un-partitioned space for upgrading to R81.20 on SMS

[networksteamIMS]

Hi all,

I am trying to upgrade my Azure based SMS from R81.10 Take 179 to R81.20 but got Not enough un-partitioned space error when verifying upgrade on gaia web gui.

So I added a new disk on Azure to the SMS VM, reboot, and it showed as /dev/sdc

But when I check on LVM again, it's not showing as "unallocated space"

Any ideas mates......? Thanks in advanced

Regards,

Bill.

[Amir_Senn]

Use this SK:

https://support.checkpoint.com/results/sk/sk156552

[networksteamIMS]

Thanks for your link which I had read previously. Looks like it doesnt mention about "un-partitioned space" which is used for upgrade.

Regards,

Bill.

[Amir_Senn]

Did you do "rm /etc/autogrow"?

[networksteamIMS]

ah.... i didnt

[Nir_Shamir]

you need to remove that file before shutting down the machine and adding more storage , otherwise it's going to the VOID

[networksteamIMS]

oh i see. is it safe for me to delete the new disk which i just added?

[Amir_Senn]

I'm not sure but I think that the order doesn't matter. Once you will reboot and login to maintenance mode it should be fine IMO.

[networksteamIMS]

i powered off it, detached the new disk

powered on again, new disk disappeared, rm /etc/autogrow , powered off

added another new disk (with new name different size), powered on

still the same

but just one thing i didnt do these in maintenance mode, curious which step(s) need to be done in maintenance mode?

Regards,

Bill.

[Nir_Shamir]

you have two options:

1) 

How to increase the disk size of a CloudGuard VM for Azure, AWS, GCP, and OCI

<https://support.checkpoint.com/results/sk/sk156552>

2) 

How to add a new hard disk to Gaia running on Azure, AWS or GCP

<https://support.checkpoint.com/results/sk/sk169153>

follow the instructions there exactly.
this will just add more free storage to your VM.
then you need to go into maintenance mode and use lvm_manager utility to add that free storage to your root or log partitions

[networksteamIMS]

I guess the error I got is asking me to add space for "un-partitioned space" instead of any partitions like root or logs?

Should the upgrade process needs enough "un-partitioned space"?

[Amir_Senn]

I don't know the code but I'm assuming that every time you boot, autogrow is created from new, adding all added disks to unallocated space, or if deleted will remove them from it (assuming you didn't allocate it to a specific partition).

So every time you add/remove - delete autogrow and check in maintenance mode in lvm_manager.

As Nir said, I suggest to start from new and follow the SK.

[networksteamIMS]

I followed https://support.checkpoint.com/results/sk/sk156552 to extend the disk on Azure for another 40GB but this 40GB free space is not shown on lvm_manager

I found an interesting point for the parted -l result. The partition "3" does not end with the disk size

[Amir_Senn]

Could be because you added and deleted another disk. Initial size is 100 GB, how big is the current disk you added in Azure? Interesting edge case.

Anyhow, do you have enough disk space to perform the upgrade now correct?

[networksteamIMS]

The disk I added few days back was 40GB, it was recognized as a new disk /dev/sdc (but not showing as "un-partitioned space" on lvm_manager

I powered if off, deleted it from Azure and now /dev/sdc is gone

So I followed the SK to rm /etc/autogrow, powered off, expanded the current disk from 120GB to 160GB, powered it on

And now it is like what I post earlier...

as the "un-partitioned space" is still 8GB (even I added disk or expanded disk), the upgrade verification still throws me same error "not enough un-partitioned space"

[Amir_Senn]

Try to allocate to upgrade reserved partition

[networksteamIMS · Accepted solution]

Ended up redeploying a new machine with bigger disk, restored config.

Thanks all