Upgrade from 3.4 to 4.3

[plittlefield]

Hi Folks,

I am planning an upgrade of a standalone single PVE version 3.4 to the latest PVE version 4.3

I am going to test the upgrade in a VirtualBox on my laptop.

I am reading this page - https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0 - but wondered if I have to go to PVE version 4.0 first and then hop to each version up to the latest 4.3 or whether I can go 3.4 to 4.3 in one go?

What pitfalls am I expecting here and what problems have people encountered that are not in the documentation?

Obviously, I know that each PVE installation is kind of different, but I would rather have 10 browser tabs open ready for the expected than have more downtime and frantically pressing Google Search!?!

Homebrew server, 8 core CPU, 32GB RAM, Software RAID 1 with 3 x 3TB drives, with 8 VMs and no Containers:-

Personalities : [raid1]
md1 : active raid1 sda3[2] sdc3[3](S) sdb3[1]
2929610560 blocks super 1.2 [2/2] [UU]
md0 : active raid1 sda2[2] sdc2[3](S) sdb2[1]
521920 blocks super 1.2 [2/2] [UU]


Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/pve-root ext3 102G 22G 76G 22% /
/dev/mapper/pve-data ext3 2.9T 727G 2.1T 26% /var/lib/vz
/dev/md0 ext3 518M 71M 420M 15% /boot
/dev/fuse fuse 32M 17k 32M 1% /etc/pve
172.16.0.2:/ProxMox nfs 12T 6.1T 5.8T 52% /mnt/pve/nfs1


NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 2.7T 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 510M 0 part
│ └─md0 9:0 0 509.7M 0 raid1 /boot
└─sda3 8:3 0 2.7T 0 part
└─md1 9:1 0 2.7T 0 raid1
├─pve-root (dm-0) 253:0 0 96G 0 lvm /
├─pve-swap (dm-1) 253:1 0 15G 0 lvm [SWAP]
└─pve-data (dm-2) 253:2 0 2.6T 0 lvm /var/lib/vz
sdb 8:16 0 2.7T 0 disk
├─sdb1 8:17 0 1M 0 part
├─sdb2 8:18 0 510M 0 part
│ └─md0 9:0 0 509.7M 0 raid1 /boot
└─sdb3 8:19 0 2.7T 0 part
└─md1 9:1 0 2.7T 0 raid1
├─pve-root (dm-0) 253:0 0 96G 0 lvm /
├─pve-swap (dm-1) 253:1 0 15G 0 lvm [SWAP]
└─pve-data (dm-2) 253:2 0 2.6T 0 lvm /var/lib/vz
sdc 8:32 0 2.7T 0 disk
├─sdc1 8:33 0 1M 0 part
├─sdc2 8:34 0 510M 0 part
│ └─md0 9:0 0 509.7M 0 raid1 /boot
└─sdc3 8:35 0 2.7T 0 part
└─md1 9:1 0 2.7T 0 raid1
├─pve-root (dm-0) 253:0 0 96G 0 lvm /
├─pve-swap (dm-1) 253:1 0 15G 0 lvm [SWAP]
└─pve-data (dm-2) 253:2 0 2.6T 0 lvm /var/lib/vz


proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.4-3
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-32
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1


Thanks.



Paully

 

[apmuthu]

You might want to remove unused kernel first:
pve-kernel-2.6.32-32-pve: 2.6.32-136
and reboot before upgrading.

 

[plittlefield]

You might want to remove unused kernel first:
pve-kernel-2.6.32-32-pve: 2.6.32-136
and reboot before upgrading.

Yes, that is mentioned on the official wiki page, although that is after the upgrade and after the first reboot with the new kernel.

Also, if I follow your instructions and remove the kernel before upgrading, does that not leave me stranded if anything goes wrong?!

Paul

 

[apmuthu]

The first 4 lines of your pveversion -v are:

proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-37-pve: 2.6.32-150

After upgrade and reboot, you are now running the kernel: pve-kernel-2.6.32-37-pve: 2.6.32-150
whilst the old kernel is still available: pve-kernel-2.6.32-32-pve: 2.6.32-136

It is this last unused old kernel that can be removed (and rebooted) without leaving you stranded.

 

[plittlefield]

It is this last unused old kernel that can be removed (and rebooted) without leaving you stranded.

Ah, got it, thank you.

So, I upgrade my current 3.4.x to the latest 3.4.x with...

apt-get update
apt-get dist-upgrade
reboot

Check my version numbers and then remove the old kernel with...

apt-get remove pve-kernel-2.6.X

...where X is not the latest one I am actually running.

yes?

Paully