I'm currently going thru the online notes and the official Wiki for upgrading (my production homelab) from PVE 7 to 8. I have a Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz and wondering if someone has any tip for the upgrade. Anything I need to know before starting the process ...
Upgrade from 7 to 8
- Thread starter HPmoss
- Start date
... for example, in the Wiki one of the resolution to fix "Network Fails on Boot Due to NTPSec Hook" is to install chrony.
But when I check my current PVE 7.4-17, chrony is already installed.
But when I check my current PVE 7.4-17, chrony is already installed.
Hi,
Use the
You can also have a look at the release thread, but it is long and most will either already be fixed or added to the Known Issues section in the upgrade guide.
then you shouldn't be affected by that issue
Follow the upgrade guide closely: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
Use the
pve7to8 checker script to detect potential issues early.You can also have a look at the release thread, but it is long and most will either already be fixed or added to the Known Issues section in the upgrade guide.
Couple of observations when I upgraded to 8:
LV volume has problem activating so ...
thin_check_options = [ "-q", "--skip-mappings" ] in /etc/lvm/lvm.conf and running update-initramfs -u afterwards fixed the issue for me. I noticed now it runs on kernel 6.2 so I assume 6.2 is the new LTS kernel?
I guess the upgrade guide needs a bit updating especially regarding LVs.
LV volume has problem activating so ...
thin_check_options = [ "-q", "--skip-mappings" ] in /etc/lvm/lvm.conf and running update-initramfs -u afterwards fixed the issue for me. I noticed now it runs on kernel 6.2 so I assume 6.2 is the new LTS kernel?
I guess the upgrade guide needs a bit updating especially regarding LVs.
That issue affects quite a few people, but it's not specific to the upgrade. There were sporadic reports about it since a while: https://forum.proxmox.com/threads/local-lvm-not-available-after-kernel-update-on-pve-7.97406 and what you did is one of the recommended workarounds: https://forum.proxmox.com/threads/l...fter-kernel-update-on-pve-7.97406/post-430860
We could increase the udev timeout for everybody, but if not even more people are affected, that's better left as a decision for the admin.
The 6.2 will be superseded by the 6.5 kernel in the next point release, i.e. Proxmox VE 8.1.