> Source: [sk181508](https://support.checkpoint.com/results/sk/sk181508)

# sk181508 - Major upgrade package is not available in CPUSE

| Property | Value |
|----------|-------|
| Solution ID | sk181508 |
| Date Created | 2023-09-26 |
| Last Modified | 2025-04-22 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server, Multi-Domain Security Management Server |
| Versions | R82.10, R82, R81.20, R81.10 (EOS), R82.10, R82, R81.20, R82.10, R81 (EOS), R81.10 (EOS), R81 (EOS), R81 (EOS), R81.10 (EOS), R81.20, R82 |
| OS | Gaia |

## Symptoms

- * In Gaia OS, CPUSE shows only Jumbo Hotfix updates for the current version and does not show an upgrade package for higher available versions.

  For example, in the R81.10 version, CPUSE does not show the upgrade package for the R81.20 version.
* If you import the upgrade package for a higher version manually and start the upgrade, then it fails with this message:

  `The upgrade is supported only on servers with standard Check Point partition formats`

  Example from R81.10 when tried to manually install the R81.20 upgrade package:


  Show / Hide this section  
  > `Upgrade:`  
  > `
  > The following results are not compatible with the package:`  
  > `
  > `  
  > `
  > - Pre-Export Verification found blocking errors. A detailed report is available here or in the 'Package Details' section on the right.`  
  > `
  > `  
  > `
  > This installation package is not supported on Cloud environments.`  
  > `
  > The upgrade is supported only on servers with standard Check Point partition formats.`  
  > `
  > This installation package may not be supported on your appliance model.`  
  > `
  > For the latest software images, see sk166536.`  
  > `
  > Upgrade to R81.20 on Quantum LightSpeed Appliances is only supported for non-hardware-accelerated (Kernel PPAK) Mode. For more information, see sk179432.`  
  > `
  > This installation package may not be supported on your server.`  
  > `
  > In-place upgrade is not supported for CloudGuard IaaS`  
  > `
  > ClusterXL in Load Sharing mode with IPSec VPN blade enabled cannot be upgraded to R81.20. For more information see sk162637.`  
  > `
  > To upgrade management machine from R80.10 and lower, first upgrade to R80.40 and only then upgrade to R81.20.`  
  > `
  > To upgrade gateway machine from R77.20 and lower, first upgrade to R80.40 and only then upgrade to R81.20.`

## Cause

CPUSE examines many parameters before it allows a package installation, including these:

* The number of boot partitions.  
  Gaia OS supports only one boot partition.
* The total number of partitions.  
  Versions R81.20 and higher must have 4 partitions.  
  Versions R81.10 and lower must have 3 partitions.

Possible causes:

1. There are two or more boot partitions on the current Gaia server.

   > Gaia OS supports only one boot partition.
   >
   > In addition, R81.20 and higher versions use GRUB2 that requires specific partition format before these versions can install themselves.
   >
   > Example output of the "*parted -l*" command from a VMware virtual machine with two hard disks:
   >
   > ```
   > [Expert@HostName:0]# parted -l
   > 
   > Model: VMware Virtual disk (scsi)
   > Disk /dev/sda: 215GB
   > Sector size (logical/physical): 512B/512B
   > Partition Table: msdos
   > Disk Flags:
   > 
   > Number  Start   End    Size   Type     File system  Flags
   > 1       32.3kB  313MB  313MB  primary  ext3         boot
   > 2       313MB   215GB  214GB  primary               lvm
   > 
   > Model: VMware Virtual disk (scsi)
   > Disk /dev/sdb: 859GB
   > Sector size (logical/physical): 512B/512B
   > Partition Table: msdos
   > Disk Flags:
   > 
   > Number  Start   End     Size    Type     File system     Flags
   > 1       32.3kB  18.3GB  18.3GB  primary  linux-swap(v1)  boot
   > 2       18.3GB  859GB   841GB   primary                  lvm
   > 
   > 
   > [Expert@HostName:0]#
   > ```

2. Unrecognised disk on the current Gaia server.

   > Example output of the "*parted -l*" command from a VMware virtual machine with two hard disks:
   >
   > ```
   > [Expert@HostName:0]# parted -l
   > 
   > Model: VMware Virtual disk (scsi)
   > Disk /dev/sda: 537GB
   > Sector size (logical/physical): 512B/512B
   > Partition Table: gpt
   > Disk Flags:
   > 
   > Number  Start   End     Size    File system     Name  Flags
   >  1      17.4kB  315MB   315MB   ext3                  boot
   >  2      315MB   34.0GB  33.7GB  linux-swap(v1)
   >  3      34.0GB  537GB   503GB                         lvm
   > 
   > Error: /dev/sdb: unrecognised disk label
   > 
   > Model: VMware Virtual disk (scsi)
   > Disk /dev/sdb: 1074GB
   > Sector size (logical/physical): 512B/512B
   > Partition Table: unknown
   > Disk Flags:
   > 
   > Model: Linux device-mapper (linear) (dm)
   > Disk /dev/mapper/vg_splat-lv_log: 520GB
   > Sector size (logical/physical): 512B/512B
   > Partition Table: loop
   > Disk Flags:
   > 
   > Number  Start  End    Size   File system  Flags
   >  1      0.00B  520GB  520GB  xfs
   > 
   > Model: Linux device-mapper (linear) (dm)
   > Disk /dev/mapper/vg_splat-lv_current: 510GB
   > Sector size (logical/physical): 512B/512B
   > Partition Table: loop
   > Disk Flags:
   > 
   > Number  Start  End    Size   File system  Flags
   >  1      0.00B  510GB  510GB  xfs
   > 
   > [Expert@HostName:0]#
   > ```

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
