Kernel Panic after update

Help
1

Moin,

after an update, I’m getting a kernel panic. It asks for the passphrase first, then:
VFS: Unable to mount root fs on unknown-block(0,0).

The GRUB menu seems to have been completely rewritten; there is no trace of older entries or kernels. The GRUB options are:

setparams ‘KDE neon GNU/Linux’

recordfail
load_video
gfxmode $linux_gfx_mode
insmod gfxio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio;
insmod part_gpt
insmod cryptodisk
insmod luks
insmod gcry_rijndael
insmod gcry_rijndael
insmod gcry_sha256
insmod ext2
cryptomount -u 5c855e81-8479-42c6-bcff-7ec7689b638c
set root=‘cryptouuid/5c855e818479426bcff7ec7689b638c’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint=cryptouuid/5c855e81
else
search --no-floppy --fs-uuid --set=root ba4a4fa2-b540-460a-b88e
fi
linux /boot/vmlinuz-7.0.0-28-generic root=/dev/mapper/luks

I can mount the partition using a rescue system, so nothing is actually broken. It’s just GRUB that’s having issues.

Kernel panics are thankfully very rare—but that’s why I lack experience with them. What can I do to fix my system?
Grateful for any pointers.

2

This isn’t an kernel panic, but a configuration error causing an unbootable system.

This isn’t specific to neon, they are guides online for this, I picked one, but your guess is as good as mine.
https://slimbook.com/en/blog/guides-2/post/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-00-517

Since you don’t an entry working, you will need to do it from a live image (usb boot) and use chroot to modify the system on disk.

It asks for the passphrase first

This might make things more complicated.

Those kinds of issues are very hard for newcomers to fix, so I am very sad this still happens.
This would need to be prevented, but it is probably very hard to fix for most devs.
It shouldn’t have anything to do withe KDE or neon, the kernel and low-level systems are maintained by the parent distro ubuntu lts here.

3

Hi Meven,

Thanks for your reply and the link. I was hoping it was a known bug in the update.

I’ve been able to narrow down the problem and am making progress with fixing it.

Micha