After a software update which completed successfully I was asked to reboot. I am now unable to boot and get the following message: Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(0.0) I have booted with a live DVD and used manjaro-chroot to access the native system. I th…

Hi @barraclm , can you at least boot with kernel 5.15 as it seems you have it intact, meaning you have linux515-x86_64.kver vmlinuxz-5.15-x86_64 initramfs-5.15-x86_64-fallback.img initramfs-5.15-x86_64.img extramodules-5.15-MANJARO When you reboot keep pressing ESC button ( I think its that button …

[image] barraclm: ===>ERROR: specified kernel image does not exist: ‘/boot/vmlinuxz-5.19-x86_64’ That kernel has already been EOL for ages. [image] barraclm: ===>Using configuration file: ‘/etc/mkinitcpio.conf’ → -k /boot/vmlinuxz-6.2-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.2…

Kernels v5.19 and v6.2 are no longer supported I suggest check installed kernels sudo mhwd-kernel -li and remove any that are not listed in latest stable update announcement, or marked End Of Life sudo mhwd-kernel -r linux519 Manjaro Kernels - Manjaro

Hi, [image] barraclm: I have booted with a live DVD and used manjaro-chroot to access the native system If its possible do it again, and uninstall both of those kernels, and instal 6.1 LTS, than reboot and see if it works. @Aragorn , @nikgnomic this should be possible ??..

If the missing kernel is the only problem, then yes. But I suspect there’s more going on than that. :thinking:

Well… according to the OP initial post it seems so. Anyhow its good to uninstall EOL kernels and go with LTS…

What more details would you like? My system is updated regularly , if nor daily, at least weekly. I upgraded to 6.2 within the last week and that was from 6.x, not 5.x. I am as puzzled as you as to why it is referring to 5.19 and I am also puzzled why I was offered 6.2 when I now see that that is no…

[image] barraclm: I am also puzzled why I was offered 6.2 when I now see that that is not a supported kernel. Your database was probably not up to date. Run this in the chroot environment… :arrow_down: sudo pacman-mirrors -f && sudo pacman -Fy && sudo pacman -Syyu [image] barraclm: Wha…

Thank you. I will do that as soon as I have figured out how to get the result of the machine. Meanwhile, this is what I have in /boot and /lib/modules /boot linux515-x86_64.kver linux61-x86_64.kver linux62-x86_64.kver vmlinuxz-5.15-x86_64 vmlinuxz-6.1-x86_64 vmlinuxz-6.2-x86_64 initramfs-5.1…

Please forgive my ignorance, but how do I get network access in the chroot environment? I do have network access in the live cd booted environment that I am chrooting from but the pacman command is failing because of no network.

[image] barraclm: I do have network access in the live cd booted environment that I am chrooting from but the pacman command is failing because of no network. If you have network access in the live environment, then you should also have it in the chroot environment. Something’s not right the…

Can't boot after software update

Support

Aragorn 21 September 2023 17:34 11

If you have network access in the live environment, then you should also have it in the chroot environment.

Something’s not right there.

Try going over the steps in this tutorial below…