Hi,I was pretty sure I had made it so that /boot was mounted on /dev/nvme0n1p1, that's how I mount it in archiso, but running `df /boot` shows that it's on /dev/nvme0n1p2, which is where everything else is installed to as well. I noticed as well that /boot seemed very empty, but after mounting it correctly it seems to be all good now. Fingers crossed that it all works properly going forwards, and thank you all so much for the replies! :3
On 4/22/26 2:36 AM, Jan Alexander Steffens (heftig) wrote:
On Wed, Apr 22, 2026 at 12:24 AM Lucie Scarlet <[email protected]> wrote:Hi, Whenever I upgrade my Linux kernel, my computer never properly boots. I have to boot into archiso and reinstall the kernel in chroot before I can get it booting again. Not very sure where to begin looking, but it's an issue that has been bugging me for a good while now. The fix for it is easy enough which is why I've put off mentioning it before now.A common issue is that a split /boot partition isn't mounted, which causes the kernel upgrade to place new kernels and initrds in the root partition's /boot directory instead. Compare the mounts you do in the archiso with those made when your system boots.
OpenPGP_0x257D35EF5E938593.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
publickey - [email protected] - 0x4C91F9E3.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
