1.4 KiB
1.4 KiB
| id | type | title | tags | importance | confidence | created | updated | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| f79b6b07-a0ec-4baa-9e1b-4732d104056a | solution | Proxmox 7 to 8 upgrade completed successfully |
|
0.9 | 0.8 | 2026-02-19T17:05:30.467207+00:00 | 2026-02-19T17:05:30.467207+00:00 |
Proxmox PVE 7.4-20 to 8.4.16 Upgrade (2026-02-19)
Successfully upgraded Proxmox from PVE 7.4-20 (kernel 5.13.19) to PVE 8.4.16 (kernel 6.8.12-18-pve).
Procedure
- Backed up all 13 production guests to TrueNAS (home-truenas PVE storage at /mnt/pve/home-truenas)
- Ran pve7to8 --full (23 passed, 0 failures)
- Switched local DNS to 1.1.1.1/8.8.8.8 (Pi-holes on Proxmox guests)
- Shut down all guests (some needed --forceStop)
- Backed up /etc/apt/sources.list and sources.list.d/
- Changed repos: bullseye -> bookworm
- DEBIAN_FRONTEND=noninteractive apt dist-upgrade -y -o Dpkg::Options::='--force-confnew'
- Rebooted (~4 min to come back)
- Started guests in dependency order
- Validated all services
Key Issues
- I/O storm: all guests booting simultaneously caused ~50% I/O delay for minutes
- Pi-hole 1 Docker container needed restart (UDP DNS failed, TCP worked)
- Home Assistant got new DHCP IP (10.10.0.215 instead of previous)
- VMs 105/112 ignored ACPI shutdown, needed --forceStop
- Several guests had onboot=1, auto-started before manual ordering