R81.20 Partition Layout?

[VikingsFan]

Figure I post here as responses are amazingly fast.  I do have a case open and waiting response from TAC but... in the middle of a server rebuild due to a failed upgrade.  Ended up running the 81.10 ISO and installing fresh, patched to Take 66 to match my backup (did a migrate export) and then restored (migrate import) into the server.  So far so good but not seeing R81.20 listed available and if I manually upload I get a 'your partitions are not in Check Point standard'.

This is a clean Dell R730/81.10 install so not really sure why it would be complaining.  Reading the release notes I don't see anything about partition requirements except one part that mentions it should be a 110GB root which mine is 100GB.  Would that be it?

See screenshots.

[Amir_Senn · Accepted solution]

It's not the partitions that causes an issue, I think it's multiple hard disks. See the following SK, it might be related:

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

This is the same machines as was previously installed? Did you change something in the RAID definitions?

[VikingsFan]

Correct.  Same exact hardware.  RAID configuration was not touched.  See screenshots.

[VikingsFan]

KB says multiple disks are not supported?  It's been on the three virtual disks even before the crash and it did allow an upgrade to R81.20 before it blew up.  During the R81.10 install wizard, I see three drives sda, sdb, sdc and we chose sda for the main install and it says something about using all the drives.

[VikingsFan]

Just a final answer but I blew out the RAID and the three virtual disks and successfully installed R81.10 and then upgraded to R81.20.  Might want to notate in that doc that it also impacts Open Server and not just VMware.

Thanks!

[Chris_Atkinson]

Though not for specifically Open Server scenarios sk180769 may provide some clues.

With that said what does the output of each of the following look like on this machine currently?

blkid

parted -l

[VikingsFan]

Posted parted -l above.  blkid:

/dev/sda1: LABEL="/boot" UUID="fed19dba-294a-4efa-accc-760bedfbc5a4" TYPE="ext3" PARTUUID="19348317-d6fb-4f3f-b56e-2bb8a1155cd1"
/dev/sda2: UUID="CpxlsR-TbrE-yRh1-GNnv-RrN0-baCw-mhqucU" TYPE="LVM2_member" PARTUUID="04dfc68e-5b81-41a1-908c-32692ea950c2"
/dev/sdb1: LABEL="SWAP-sdb1" UUID="9ed0730e-0c4d-46ce-92e5-711f44a20596" TYPE="swap" PARTUUID="575526f1-ca96-4030-9356-e387f64b814c"
/dev/sdb2: UUID="26h4is-ROrX-uoiV-9dJN-sEh8-OZar-7CyOQK" TYPE="LVM2_member" PARTUUID="4123173d-012c-4a24-93d7-46a8a39e8373"
/dev/sdc1: UUID="sU08c9-jEXH-JevF-h1PZ-xB7u-SP4m-bQchGI" TYPE="LVM2_member" PARTUUID="3a9cee4d-cd00-4ea4-9d74-2bc983a89e58"
/dev/mapper/vg_splat-lv_current: UUID="a29e5669-6273-41c2-9414-69befe78662c" TYPE="xfs"
/dev/mapper/vg_splat-lv_log: UUID="6c73b663-3f80-42ca-8d3d-fff4543804b2" TYPE="xfs"
/dev/mapper/vg_splat-lv_Pre_81_10_T139: UUID="a3dfa497-db33-457b-b748-60ec46698cc4" TYPE="xfs"
/dev/root: UUID="a29e5669-6273-41c2-9414-69befe78662c" TYPE="xfs"

[VikingsFan]

Think you guys might be onto something.  Checked a different open server that we upgraded recently and it has a single virtual disk.  Not sure why or how the Web GUI allowed me to verify/upgrade the current one from R81.10 to R81.20 with the three virtual disks but maybe that's why it bombed out in the end and corrupted things.