Files
Blog/content/post/14-proxmox-cluster-upgrade-8-to-9.md
Gitea Actions 739763bc9c
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 7s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 10s
Blog Deployment / Test-Staging (push) Successful in 2s
Blog Deployment / Merge (push) Successful in 7s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Production (push) Successful in 3s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s
Auto-update blog content from Obsidian: 2025-11-01 16:43:01
2025-11-01 16:43:01 +00:00

3.0 KiB

slug, title, description, date, draft, tags, categories
slug title description date draft tags categories
proxmox-cluster-upgrade-8-to-9 Template true

Intro

My Proxmox VE cluster is almost one year old now, and it's been a while since I didn't update my nodes. Now is the time to move forward and bump it to Proxmox VE 9.

I'm mainly interested in the new HA affinity rules, here what this version brings:

  • Debian 13 "Trixie"
  • Snapshots for thick-provisioned LVM shared storage
  • Fabrics feature for the SDN stack
  • Better mobile interface
  • Affinity rules in HA cluster

In this article, I will walk you through the upgrade steps for my Proxmox VE HA cluster supported by Ceph distributed storage.


Prerequisites

  • All odes upgraded to the latest version of Proxmox VE 8.4.

    Ensure your node(s) have correct package repository configuration (web UI, Node -> Repositories) if your pve-manager version isn't at least 8.4.1.

  • Hyper-converged Ceph: upgrade any Ceph Quincy or Ceph Reef cluster to Ceph 19.2 Squid before you start the Proxmox VE upgrade to 9.0.

    Follow the guide Ceph Quincy to Reef and Ceph Reef to Squid, respectively.

  • Reliable access to the node. It's recommended to have access over a host independent channel like IKVM/IPMI or physical access.

    If only SSH is available we recommend testing the upgrade on an identical, but non-production machine first.

    It is also highly recommended to use a terminal multiplexer (for example, tmux or screen) to ensure the upgrade can continue even if the SSH connection gets interrupted.

  • A healthy cluster

  • Valid and tested backup of all VMs and CTs (in case something goes wrong)

  • At least 5 GB free disk space on the root mount point, ideally more than 10 GB.

  • Check known upgrade issues

Checks

Use console if possible, avoid using console from the WebGUI. Use SSH instead

Continuously use the pve8to9 checklist script

A small checklist program named pve8to9 is included in the latest Proxmox VE 8.4 packages. The program will provide hints and warnings about potential issues before, during and after the upgrade process. You can call it by executing:

pve8to9

Move important Virtual Machines and Containers

Upgrade

Update the configured APT repositories

Update Debian Base Repositories to Trixie

Add the Proxmox VE 9 Package Repository

Update the Ceph Package Repository

Refresh Package Index

Upgrade the system to Debian Trixie and Proxmox VE 9.0

Check Result & Reboot Into Updated Kernel

Post-Upgrade Validation

  • Checking cluster communication (pvecm status)

  • Verifying storage mounts and access

  • Testing Ceph cluster health (ceph -s)

  • Confirming VM operations, backups, and HA groups

  • Re-enabling HA and migrating workloads back