Bug 456909

Summary:	after system update kernel doesnt load. invalid magic number
Product:	[KDE Neon] neon	Reporter:	benjamin <matthias.behrens>
Component:	general	Assignee:	Neon Bugs <neon-bugs-null>
Status:	RESOLVED WAITINGFORINFO
Severity:	critical	CC:	jr, neon-bugs-null, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description benjamin 2022-07-19 11:29:05 UTC

SUMMARY
***
i follow the gui instructions to update and reboot
after reboot and the update routine running through without error,
the screen to chose between kde neon / advanced / uefi apears
when i pick neon i just get the error "invalid magic number"
if i pick advanced and any of my previous kernels, the boot stops with kernel panic
my boot drive is not full
***


STEPS TO REPRODUCE
1. update kde neon
2. reboot

OBSERVED RESULT
system is unusable. boot ends up in "invalid magic number"

EXPECTED RESULT
an updated kde neon

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: latest
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 benjamin 2022-07-23 20:33:35 UTC

the problem stems from a kernel update on a full disk encryption exceding 100mb for the initial ramdisk.
i suspect every system with full disk encryption will be affected by this bug.
i could work arround it by setting modules=dep in the initramdisk tools config file and generate new init ramdisks.
it sounds way easier than it is. it costed me a week to get back into my system.
this bug is critical and should be fixed asap

Comment 2 Carlos De Maine 2025-09-20 09:35:17 UTC

Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!