Arch Linux

quiknug

Member

Registered: 2025-02-21

Posts: 3

[FIXED] Kernal Panic after updating while ignoring icu

So I fully understand this was an ignorant thing to do, but I was unable to update the packages how I would normally do so (i.e. ``sudo pacman -Syu``) since updating icu would break a dependency in another package (I forget the name of the package). So I did the following command ``sudo pacman -Syu --ignore icu`` which allowed me to update the packages but now my build is broken. Upon restart, I don't get to the LUKS screen and I get a blue screen showing some kind of kernal panic.  I get a few messages but the most important ones seem to be the following:

/dev/root: Can't open blockdev
VFS: Cannot open root device "/dev/mapper/volgroup0-lv_root" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:
List of all bdev filesystems:
fuseblk

Kernal panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)

So I was able to boot from a live disk and did the following:

After unlocking the partition

sudo cryptsetup luksOpen /dev/nvme0n1p3 pv_home

activating the physical volume

vgchange -ay

and mounting it (tbc I omitted the creating of directories in this reconstruction as well as the connecting of the internet)

mount /dev/mapper/volgroup0-lv_root /mnt/root
mount /dev/mapper/volgroup0-lv_home /mnt/home
mount -t proc /proc /mnt/proc/
mount -t sysfs /sys /mnt/sys/
mount --rbind /dev /mnt/dev/

I was able to uninstall electron and install icu

pacman --root=/mnt/root -Rns electron
pacman --root=/mnt/root -Syu icu

then I unmounted everything with umount and attempted to reboot but I still get the same kernal panic. Is there something else I should be doing?

EDIT:

I should also note that the initial installation where I ignored installing icu also upgraded linux

Last edited by quiknug (2025-02-23 00:53:45)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,119

Re: [FIXED] Kernal Panic after updating while ignoring icu

After the fixing update you need to regenerate your initramfs with

mkinitcpio -P

from a chroot with all partitions properly mounted.

quiknug

Member

Registered: 2025-02-21

Posts: 3

Re: [FIXED] Kernal Panic after updating while ignoring icu

So I'll go through the stuff I did:

I made a directory root within /mnt and then did the following:

mount /dev/mapper/volgroup0-lv_root /mnt/root

From within /mnt/root I mounted the home, sys, proc and dev folders. I only have two logical volumes lv_root and lv_home

After which I arch-chrooted into /mnt/root and did mkinitcpio -P

which gave me

 specified kernal image does not exist

I then tried reinstalling linux and linux-lts with pacman and re-did mkinitcpio -P. The process seems to have gone smoothly but I still have the kernal panic.

I also reinstalled Linux-firmware and that didn't help the kernal panic. I'm unsure of what to do next at this point

Last edited by quiknug (2025-02-22 21:08:07)

seth

Member

Registered: 2012-09-03

Posts: 61,639

Re: [FIXED] Kernal Panic after updating while ignoring icu

specified kernal image does not exist

Most certainly not, there's no "a" in "kernel".
However, did you simply forget to mount the boot partition?
Re-installing the kernel into the wrong location (/boot mountpoint) would then oc. not help either.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

quiknug

Member

Registered: 2025-02-21

Posts: 3

Re: [FIXED] Kernal Panic after updating while ignoring icu

That turned out to be the issue. Thank you so much. Will also remember the "e" in Kernel for next time!