Your partitions are not in Check Point standard format

[flachance]

We are trying to upgrade a gateway from R81.10 JHF take 95 to R81.20.

It's a virtual gateway on ESX 7.0. It doesn't want to upgrade with the message:

"Your partitions are not in Check Point standard format, and an upgrade is not possible. Reinstall your system and verify correct partitioning."

I'm looking at sk180769 (Upgrade to R81.20 on a Virtual Machine fails with "Your partitions are not in Check Point standard f...) but none of the scenario applies to us. Anything else I can check before redeploying instead of upgrading?

[the_rock]

Never seen that issue and I deployed before on esxi 7.0 and never had a problem. Lets see if someone else may have an idea...

Andy

[_Val_]

How does the partitioning look in the first place?

[flachance]

# fdisk -l
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/sda: 128.8 GB, 128849018880 bytes, 251658240 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
Disk label type: gpt
Disk identifier: DAFBAA60-977E-41F9-A3FF-C13D035F701D

# Start End Size Type Name
1 34 614433 300M EFI System
2 614434 17386294 8G Linux swap
3 17386295 209715166 91.7G Linux LVM
4 209715167 251658206 20G Linux LVM

[the_rock]

That looks right to me...

Below is from my lab:

[Expert@CP-TEST-FIREWALL:0]# fdisk -l
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/vda: 107.4 GB, 107374182400 bytes, 209715200 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
Disk label type: gpt
Disk identifier: 1B9B573F-DDAF-4FC6-A932-D7A8AC0CF57A

# Start End Size Type Name
1 2048 4095 1M BIOS boot parti
2 4096 618495 300M Microsoft basic
3 618496 17395711 8G Linux swap
4 17395712 209713151 91.7G Linux LVM

Andy

[Mr_Wolf]

Looks like sk180769 to me. This is a not supported partition layout.

[Chris_Atkinson]

Have you already reviewed the output of # blkid or similar?

[flachance]

Thanks I did not even know about blkid

# blkid
/dev/root: UUID="fef8231e-f7ad-4191-9153-45ce793580bd" TYPE="xfs"
/dev/sda1: LABEL="/boot" UUID="4af4cb21-b6d9-4838-9ff5-31789779ca5c" TYPE="ext3" PARTUUID="be21b7b1-d888-4011-b999-b4e65b18bcb3"
/dev/sda2: LABEL="SWAP-sda2" UUID="7d45efe7-cae9-4e1a-a066-82c97882c5f8" TYPE="swap" PARTUUID="7bfc6606-1f8c-4700-aa95-6750f9972364"
/dev/sda3: UUID="9RqVZX-xZIz-XFPW-QLxi-3Km2-Hl5s-DcflX5" TYPE="LVM2_member" PARTUUID="b552d077-13c9-4f7d-9e3f-73f5e86618c3"
/dev/sda4: UUID="onBPh2-bx0Y-kw2E-hxFi-EKJi-80kC-6RZ5fj" TYPE="LVM2_member" PARTUUID="ba2c722a-6961-4d7f-b3d5-7311133342bc"
/dev/mapper/vg_splat-lv_log: UUID="e4aa096e-b601-4397-a4a6-51ad23f7bc19" TYPE="xfs"
/dev/mapper/vg_splat-lv_18juil2023: UUID="1e42058f-67a7-4c19-82a3-b1d17cce1ca1" TYPE="xfs"

[the_rock]

Me neither, good command!

Andy

[archie]

How can we resolve this problem? We have the same issue.

[flachance · Accepted solution]

We redeployed the gateway.

[rafaelsimao · Accepted solution]

For us it was the only solution.

- Disk/partitions were right

- Free space (pvs, lvs and df)

We tried without success:

- Install visible packages from CPUSE 

- Import a base version (clish and web) tgz/tar

Also after redeploy, CPUSE started to fetch the all the packages (not visible before)

[the_rock]

Glad you got it working!

Andy

[archie]

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

I had tried this, the in place upgrade started, but on reboot I had only a grub prompt, so i had to boot grub manually.

But the update had finished.

I wanted to know if this is supported, or only a workaround if you have three partitions.