Crash on kernel upgrade

Q

qvex

New Member
Feb 11, 2025
4
0
1
I am running currently on kernel: "proxmox-kernel-6.8.12-4" and wanted to upgrade. Using a console I ran:

apt update && apt dist-upgrade

The output:

Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
15 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
libtasn1-6 proxmox-kernel-6.8 proxmox-kernel-6.8.12-8-pve-signed proxmox-widget-toolkit pve-container pve-i18n pve-manager
python3-pkg-resources python3-setuptools python3-urllib3 spl ssh zfs-initramfs zfs-zed zfsutils-linux
15 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/106 MB of archives.
After this operation, 577 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading changelogs... Done
(Reading database ... 82452 files and directories currently installed.)
Preparing to unpack .../proxmox-kernel-6.8.12-8-pve-signed_6.8.12-8_amd64.deb ...
Unpacking proxmox-kernel-6.8.12-8-pve-signed (6.8.12-8) over (6.8.12-8) ...

After that I got a progress bar which ended after some percent and the computer switched off (crashed) without finishing.

I am lost how to solve this.
 
Hi,
please check the system journal around the time of the crash. Please also provide some details about your host's hardware, e.g. CPU model, storage/disks for root filesystem.
 
Hi,

How can I have a look on the system journal, where do I find it. Also it is not much time I have to say, from the time I hit y for yes till the crash are just a few seconds but I will have a look.

I have a "MINIS FORUM NPB7 Mini-PC 32" with "Intel Core i7-13700H" and 32G RAM. The root is on the ssd and has 94G size, with 9.1G used, and 81G available (i.e. 11% used). The biggest usage is the "efivarfs" mounted to "/sys/firmware/efi/efivars" (192K - 113K used - 75k avail. (60%)). Which hardware details are missing you like to know?

I have some older kernel versions available to start with. I tried these as well but with the same result.

Kind regards,
Dirk
 
Hi,

it is not possible to update the microcode because the update depends on the pending kernel update:

root@bark:~# apt install intel-microcode
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
iucode-tool proxmox-kernel-6.8.12-8-pve-signed
The following NEW packages will be installed:
intel-microcode iucode-tool
The following packages will be upgraded:
proxmox-kernel-6.8.12-8-pve-signed
1 upgraded, 2 newly installed, 0 to remove and 14 not upgraded.
1 not fully installed or removed.
Need to get 7,165 kB/110 MB of archives.
After this operation, 591 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian bookworm/main amd64 iucode-tool amd64 2.3.1-3 [56.1 kB]
Get:2 http://deb.debian.org/debian bookworm/non-free-firmware amd64 intel-microcode amd64 3.20241112.1~deb12u1 [7,109 kB]
Fetched 7,165 kB in 1s (9,000 kB/s)
Reading changelogs... Done
(Reading database ... 82452 files and directories currently installed.)
Preparing to unpack .../proxmox-kernel-6.8.12-8-pve-signed_6.8.12-8_amd64.deb ...
Unpacking proxmox-kernel-6.8.12-8-pve-signed (6.8.12-8) over (6.8.12-8) ...

Progress: [ 8%] [##############.................................................................................................................................
Click to expand...

And then it crashed and the computer switched off.

I got no entry in the "System Log" around the crash. I guess it is too fast - I hit "y" and the next moment it crashes already. Can I find a journal log or something else on the system somewhere. Using the shell e.g.?
 
You can try to monitor the system log from another machine, i.e. connect to the Proxmox VE node from there via SSH and run journalctl -f, and hope to get a crash log then.

Does it also crash when you do other IO intensive operations?

You could also try to do a BIOS upgrade directly instead of installing the microcode package.
 
Unfortunately, no log entry created with journalctrl -f

I don't think is has something to do with file system (access). Could it be the running kernel is "killed" by the unpacking of the new kernel? That the upgrade progress and the kernel don't work together somehow?
 
If there is no logs, it could be some hardware-related issue or hard kernel crash. During unpacking there might be more IO/CPU load which could be a trigger.
 
You must log in or register to reply here.
Top Bottom