/boot/vmlinuz-6.12-x86_64 not found

[StephanieNight]

Hey i am on my phone and honestly not if i am posting correctly, but i got a issue, i installed the updates and rebooted, and came back to this

Not exactly sure what is going on here, but is my kernel missing?

Help would be greatly appreciated.

[TheFreed]

The update may have been corrupted somehow. If you have a Manjaro USB stick this can be fixed

Error file boot vmlinuz not found

[StephanieNight]

That looks like it is indeed the case, i have gotten a little progress with a reinstall of a older kernel, but that looks to not work with plasma.

Continuing the hunt

it is working now, had to reinstall a kernel 612 with headers and plasma-desktop.

i have added kernel 618 as a backup.

think i was on 6.12.77 when this happened, has that been removed or depricated ?

[Teo]

6.12 is an lts kernel, it is supported.

[andreas85]

once in a while this happens

The direct cause is that the kernel and the initramdisk are missing.

To understand this, you need to know how an update proceeds:

1. All necessary components are downloaded to the local machine.
2. The files and the required disk space are verified.
3. The actual update is performed.

Steps 1 and 2 are unproblematic.

It is perfectly safe to interrupt the process at this stage.

Step 3, however, should run uninterrupted

—and, above all, to completion. Otherwise, the computer will no longer be bootable.

Step 3:

• The kernel and initramdisk are deleted.
• The update of all (standard) packages runs to completion.
• The kernel and modules are replaced with the new versions (this happens while the old kernel is still running).
• An initramdisk—containing references to the current programs (which have already been updated) and kernel modules—is generated and saved.
• The boot files for GRUB are updated.

If the process is terminated prematurely, the kernel and initramdisk will be missing from the hard drive (or SSD). However, the computer will still be running on the old kernel, which remains loaded in RAM.

If you fail to notice this

and attempt to reboot, you will find yourself in a real mess.

If you do notice it before rebooting,

you can simply run the update again. In most cases, everything will be back to normal afterward. Then you can (and should) reboot

[Aragorn]

• [HowTo] Recovering from an interrupted update/upgrade