Failed upgrade from 7 to 8

JBHorne

New Member
Jan 6, 2024
1
1
3
Hello - I've been running Proxmox 7.x in my home lab for a while without issue. I attempted an upgrade to 8 and can no longer boot. I get the error:

end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Attempting to fix this myself, I used Grub advanced to boot into 5.15.158-1-pve, and this kernel loads. I can access the 8.2.4 UI.

Now trying to fix this issue I read to try and run apt install proxmox-kernel-helper, however as you can see below this gives errors as well.

Without having a deep understanding of how GRUB works with multiple kernel versions, I'm at a loss as to how to get 6.8.8.4 functioning.

Any assistance is greatly appreciated!


Bash:
root@pve:~# apt install proxmox-kernel-helper
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
proxmox-kernel-helper is already the newest version (8.1.0).
proxmox-kernel-helper set to manually installed.
The following packages were automatically installed and are no longer required:
  dctrl-tools g++-10 glib-networking glib-networking-common glib-networking-services libatk1.0-data
  libllvm11 libproxy1v5 librest-0.7-0 libsoup-gnome2.4-1 libsoup2.4-1 libsoup2.4-common
  libstdc++-10-dev libtiff5 libwebp6 libxnvctrl0 pve-headers pve-headers-5.15.149-1-pve
  pve-headers-5.15.158-1-pve pve-kernel-5.15.131-1-pve pve-kernel-5.15.131-2-pve telnet
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up proxmox-kernel-6.8.8-4-pve-signed (6.8.8-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.8.8-4-pve /boot/vmlinuz-6.8.8-4-pve
dkms: running auto installation service for kernel 6.8.8-4-pve.
Sign command: /lib/modules/6.8.8-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
applying patch linux-2.6.34-dev_pm_info-runtime_auto.patch...patching file conftest.sh

applying patch 0009-backport-pci-dma-changes-from-470.129.06.patch...patching file nvidia/nv.c

applying patch bashisms.patch...patching file conftest.sh

applying patch use-kbuild-compiler.patch...patching file Makefile

applying patch use-kbuild-flags.patch...patching file Kbuild
patching file nvidia/nvidia.Kbuild
patching file Makefile
patching file nvidia-modeset/nvidia-modeset.Kbuild

applying patch conftest-verbose.patch...patching file Kbuild

applying patch cc_version_check-gcc5.patch...patching file conftest.sh

applying patch nvidia-use-ARCH.o_binary.patch...patching file nvidia/nvidia.Kbuild

applying patch nvidia-modeset-use-ARCH.o_binary.patch...patching file nvidia-modeset/nvidia-modeset.Kbuild

applying patch conftest-prefer-arch-headers.patch...patching file conftest.sh


Building module:
Cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j40 modules KERNEL_UNAME=6.8.8-4-pve.......(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.8.8-4-pve (x86_64)
Consult /var/lib/dkms/nvidia-current/470.141.03/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.8.8-4-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.8-4-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.8-4-pve-signed (--configure):
 installed proxmox-kernel-6.8.8-4-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
 proxmox-kernel-6.8 depends on proxmox-kernel-6.8.8-4-pve-signed | proxmox-kernel-6.8.8-4-pve; however:
  Package proxmox-kernel-6.8.8-4-pve-signed is not configured yet.
  Package proxmox-kernel-6.8.8-4-pve is not installed.
  Package proxmox-kernel-6.8.8-4-pve-signed which provides proxmox-kernel-6.8.8-4-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.8 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.8; however:
  Package proxmox-kernel-6.8 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.8.8-4-pve-signed
 proxmox-kernel-6.8
 proxmox-default-kernel
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)



EDIT: If this helps any...

Bash:
root@pve:~# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.8-4-pve
Found initrd image: /boot/initrd.img-6.8.8-4-pve
Found linux image: /boot/vmlinuz-5.15.158-2-pve
Found initrd image: /boot/initrd.img-5.15.158-2-pve
Found linux image: /boot/vmlinuz-5.15.158-1-pve
Found initrd image: /boot/initrd.img-5.15.158-1-pve
Found linux image: /boot/vmlinuz-5.15.149-1-pve
Found initrd image: /boot/initrd.img-5.15.149-1-pve
Found linux image: /boot/vmlinuz-5.15.131-2-pve
Found initrd image: /boot/initrd.img-5.15.131-2-pve
Found linux image: /boot/vmlinuz-5.15.131-1-pve
Found initrd image: /boot/initrd.img-5.15.131-1-pve
Found linux image: /boot/vmlinuz-5.15.74-1-pve
Found initrd image: /boot/initrd.img-5.15.74-1-pve
Found memtest86+x64 image: /boot/memtest86+x64.bin


Bash:
root@pve:~# pve7to8 --full
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =

Checking for package updates..
PASS: all packages up-to-date

Checking proxmox-ve package version..
PASS: already upgraded to Proxmox VE 8

Checking running kernel version..
WARN: unexpected running and installed kernel '5.15.158-1-pve'.

= CHECKING CLUSTER HEALTH/SETTINGS =

PASS: systemd unit 'pve-cluster.service' is in state 'active'
PASS: systemd unit 'corosync.service' is in state 'active'
PASS: Cluster Filesystem is quorate.

Analzying quorum settings and state..
WARN: non-default quorum_votes distribution detected!
FAIL: 1 nodes are offline!
INFO: configured votes - nodes: 3
INFO: configured votes - qdevice: 0
INFO: current expected votes: 3
INFO: current total votes: 2
WARN: total votes < expected votes: 2/3!
WARN: cluster consists of less than three quorum-providing nodes!

Checking nodelist entries..
PASS: nodelist settings OK

Checking totem settings..
PASS: totem settings OK

INFO: run 'pvecm status' to get detailed cluster status..

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

PASS: storage 'hdd-data2' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'pbs' enabled and active.
SKIP: storage 'pve2-ssd-data1' disabled.
SKIP: storage 'pve2-ssd-data2' disabled.
PASS: storage 'ssd-data1' enabled and active.
PASS: storage 'ssd-data2' enabled and active.
PASS: storage 'ssd-data3' enabled and active.
PASS: storage 'ssd-data4' enabled and active.
PASS: storage 'synology-entertainment' enabled and active.
PASS: storage 'synology-proxmox' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
PASS: no storage re-uses a directory for multiple content types.

= MISCELLANEOUS CHECKS =

INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvescheduler.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for supported & active NTP service..
PASS: Detected active time synchronisation unit 'chrony.service'
INFO: Checking for running guests..
WARN: 22 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if the local node's hostname 'pve' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '192.168.3.3' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048)
INFO: Checking backup retention settings..
PASS: no backup retention problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking permission system changes..
INFO: Checking custom role IDs for clashes with new 'PVE' namespace..
PASS: no custom roles defined, so no clash with 'PVE' role ID namespace enforced in Proxmox VE 8
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
PASS: systems seems to be upgraded and LXCFS is running with FUSE 3 library
INFO: Checking node and guest description/note length..
PASS: All node config descriptions fit in the new limit of 64 KiB
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking if the suite for the Debian security repository is correct..
NOTICE: found unusual suites that are neither old 'bullseye' nor new 'bookworm':
    found suite / at in /etc/apt/sources.list.d/nvidia-container-runtime.list:1
    found suite / at in /etc/apt/sources.list.d/nvidia-container-runtime.list:3
  Please ensure these repositories are shipping compatible packages for the upgrade!
NOTICE: found no suite mismatches, but found at least one strange suite
INFO: Checking for existence of NVIDIA vGPU Manager..
PASS: No NVIDIA vGPU Service found.
INFO: Checking bootloader configuration...
SKIP: System booted in legacy-mode - no need for additional packages
INFO: Check for dkms modules...
/sbin/dkms: line 2497: echo: write error: Broken pipe
WARN: dkms modules found, this might cause issues during upgrade.

= SUMMARY =

TOTAL:    47
PASSED:   34
SKIPPED:  4
WARNINGS: 6
FAILURES: 1

ATTENTION: Please check the output for detailed information!
Try to solve the problems one at a time and then run this checklist tool again.
root@pve:~#
 
Last edited:
  • Like
Reactions: Shaaarnir
Hi,
sounds like your Nvidia DMKS module might not be compatible with the new kernel version.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!