Problem Update Kernel 6.8.12-4-pve / No Boot

N

NetITx

New Member
Nov 13, 2024
2
0
1
Hello everyone,

I upgraded the system yesterday.

There was a problem with the GRUB configuration and the hard drives.

Code: 
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  proxmox-kernel-6.8.12-1-pve-signed proxmox-kernel-6.8.8-4-pve-signed
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  proxmox-kernel-6.8.12-4-pve-signed
The following packages will be upgraded:
  libmpg123-0 libnss3 proxmox-backup-client proxmox-backup-file-restore
  proxmox-kernel-6.8
5 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 111 MB of archives.
After this operation, 578 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-backup-client amd64 3.2.8-1 [3245 kB]
Get:2 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-backup-file-restore amd64 3.2.8-1 [3236 kB]
Get:3 http://security.debian.org bookworm-security/main amd64 libmpg123-0 amd64 1.31.2-1+deb12u1 [147 kB]
Get:4 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.8.12-4-pve-signed amd64 6.8.12-4 [103 MB]
Get:5 http://security.debian.org bookworm-security/main amd64 libnss3 amd64 2:3.87.1-1+deb12u1 [1331 kB]
Get:6 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.8 all 6.8.12-4 [10.6 kB]
Fetched 111 MB in 2s (56.2 MB/s)                                            
Reading changelogs... Done
(Reading database ... 76892 files and directories currently installed.)
Preparing to unpack .../0-libmpg123-0_1.31.2-1+deb12u1_amd64.deb ...
Unpacking libmpg123-0:amd64 (1.31.2-1+deb12u1) over (1.31.2-1) ...
Preparing to unpack .../1-libnss3_2%3a3.87.1-1+deb12u1_amd64.deb ...
Unpacking libnss3:amd64 (2:3.87.1-1+deb12u1) over (2:3.87.1-1) ...
Preparing to unpack .../2-proxmox-backup-client_3.2.8-1_amd64.deb ...
Unpacking proxmox-backup-client (3.2.8-1) over (3.2.7-1) ...
Preparing to unpack .../3-proxmox-backup-file-restore_3.2.8-1_amd64.deb ...
Unpacking proxmox-backup-file-restore (3.2.8-1) over (3.2.7-1) ...
Selecting previously unselected package proxmox-kernel-6.8.12-4-pve-signed.
Preparing to unpack .../4-proxmox-kernel-6.8.12-4-pve-signed_6.8.12-4_amd64.deb ...
Unpacking proxmox-kernel-6.8.12-4-pve-signed (6.8.12-4) ...
Preparing to unpack .../5-proxmox-kernel-6.8_6.8.12-4_all.deb ...
Unpacking proxmox-kernel-6.8 (6.8.12-4) over (6.8.12-3) ...
Setting up proxmox-backup-file-restore (3.2.8-1) ...
Updating file-restore initramfs...
14134 blocks
Setting up libmpg123-0:amd64 (1.31.2-1+deb12u1) ...
Setting up proxmox-kernel-6.8.12-4-pve-signed (6.8.12-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-4-pve
W: Couldn't identify type of root file system for fsck hook
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/zz-systemd-boot 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-4-pve
Found initrd image: /boot/initrd.img-6.8.12-4-pve
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
Found linux image: /boot/vmlinuz-6.8.12-3-pve
Found initrd image: /boot/initrd.img-6.8.12-3-pve
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
Found linux image: /boot/vmlinuz-6.8.12-2-pve
Found initrd image: /boot/initrd.img-6.8.12-2-pve
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
Found linux image: /boot/vmlinuz-6.8.12-1-pve
Found initrd image: /boot/initrd.img-6.8.12-1-pve
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
Found linux image: /boot/vmlinuz-6.8.8-4-pve
Found initrd image: /boot/initrd.img-6.8.8-4-pve
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
Found linux image: /boot/vmlinuz-6.8.4-2-pve
Found initrd image: /boot/initrd.img-6.8.4-2-pve
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
error: cannot read `/dev/sdb': Input/output error.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda3.  Check your device.map.
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up libnss3:amd64 (2:3.87.1-1+deb12u1) ...
Setting up proxmox-backup-client (3.2.8-1) ...
Setting up proxmox-kernel-6.8 (6.8.12-4) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for libc-bin (2.36-9+deb12u9) ...

Your System is up-to-date

After restarting I get the following error message when booting.

Error Boot PVE.png

Now Proxmox only starts with kernel 6.8.12-3 pve.

How do I get the kernel 6.8.12-4-pve to run now?

Replacing BTRFS Raid SSD or Restore with PBS:
How can I replace the 2nd SSD in the system without much reconfiguration?

Or should I rather restore Proxmox with new hard drives from the backup with PBS?
Do I have to save any onfigurations for this?

Greetings

NetITx
 
@NetITx: As you not mention your hw config I assume you have a btrfs raid1 for pve ? And one (sdb) of the 2 disks is broken now. When you try to boot I mean btrfs is going into readonly if 1 disk is missing ... So I would first try to rebuild your raid1 with a new disk.
After that you can do "apt-get reinstall" to refresh all packages. We just updated and had no problems with 6.8.12-4 on cluster nodes, includes pve only and debian upgraded to pve nodes.
 
  • Like
Reactions: proNET
I am going to Update my host. Lets see if it brakes. I will check in with my friend tomorrow and check his system. I think he is using a mirror for boot.
 
  • Like
Reactions: waltar
@SebiLa
I booted the older kernel 6.8.12-3 pve an pinned it.

@waltar
Yes I have a BTRFS Raid 1 for PVE.
I booted with kernel 6.8.12-3 and there are no signs that it is read-only mounted.
Maybe i have to check deeper.
Where should i start ?
 
Last edited:
NetITx said:
I upgraded the system yesterday.
Click to expand...
May I ask what command you used to upgrade? Your output does not look consistent to what I would expect from the regular apt-get dist-upgrade that Proxmox uses, as shown here. Maybe you did plain apt upgrade ? This should NEVER be done within Proxmox. Maybe I'm missing something. Correct me, if this is the case.
 
gfngfn256 said:
NO! apt upgrade is definitely NOT fine - it will break your system. Example.
Click to expand...
apt upgrade would only break your system if the package dependencies were wrong, which could happen I suppose but is unlikely. Worst case you'd end up with a partially updated system.

The behavior between apt upgrade and apt-get upgrade does not seem to be consistent. See:

apt -s -V upgrade
apt-get -s -V upgrade

Either way, in the output above apt does not report it's skipping any packages.
 
ky41083 said:
which could happen I suppose but is unlikely
Click to expand...
Search these forums!

ky41083 said:
in the output above apt does not report it's skipping any packages.
Click to expand...
True - but I guess the OP has been doing the same in the past - so we don't know how "healthy" his system actually is currently.


NetITx said:
The following packages were automatically installed and are no longer required: proxmox-kernel-6.8.12-1-pve-signed proxmox-kernel-6.8.8-4-pve-signed Use 'apt autoremove' to remove them.
Click to expand...
AFAIK this will never be suggested when doing the correct apt-get dist-upgrade

Either way - I don't think you should be suggesting to users to use plain upgrade .
 
gfngfn256 said:
Search these forums!
Click to expand...
Interesting. I've always read Proxmox was package compatible with Debian. Good to know it's not:
"Proxmox projects use different packaging guarantees than Debian"
https://lore.proxmox.com/pve-devel/20240909102050.40220-1-f.ebner@proxmox.com/
Click to expand...

I still think they are speaking of apt-get upgrade rather than apt upgrade breaking things, but I digress.
apt upgrade:
New packages will be installed if required to satisfy dependencies, but existing packages will never be removed. If an upgrade for a package requires the removal of an installed package the upgrade for this package isn't performed.
https://manpages.debian.org/bookworm/apt/apt.8.en.html

apt-get upgrade:
Packages currently installed with new versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version.
https://manpages.debian.org/bookworm/apt/apt-get.8.en.html
Click to expand...

Edit to add:
gfngfn256 said:
AFAIK this will never be suggested when doing the correct apt-get dist-upgrade
Click to expand...
But it will be if you use the correct apt dist-upgrade

So what are you using OP? ;)
 
Last edited:
You must log in or register to reply here.
Top Bottom