Recover from a Failed Linux Kernel Boot | Generated by AI

Home 2026.07

Question: I built a custom Linux kernel, rebooted Fedora on a MacBook Pro, and now it won’t start—what should I do?

Answer:

This usually means the system can’t boot the new kernel (missing boot entry, broken initramfs, or EFI/GRUB issue). Don’t worry—your data is likely still fine. The goal is to boot a rescue environment and fix the bootloader/kernel.


1. First check: is it completely dead or just not booting Linux?

Try these:

If you see:


2. Boot from a Fedora Live USB (most reliable fix)

You will likely need another computer to create a USB:

Boot MacBook:


3. Once inside Live environment: repair system

Open terminal and do:

Find your Linux root partition

lsblk

Look for something like:


Mount system

sudo mount /dev/nvme0n1pX /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo mount --bind /run /mnt/run

Enter system (chroot)

sudo chroot /mnt

4. Fix kernel / boot issue

Option A: reinstall kernel (safe)

dnf reinstall kernel-core kernel-modules kernel

Option B: rebuild initramfs

dracut --regenerate-all --force

5. Reinstall GRUB (important on Mac EFI)

For UEFI systems:

grub2-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=fedora
grub2-mkconfig -o /boot/grub2/grub.cfg

6. Exit and reboot

exit
reboot

Remove USB when rebooting.


7. If you compiled your own kernel (likely cause)

Your build shows:

custom kernel + “built successfully”

But common problems:

Possible failure causes


8. Quick recovery trick (if GRUB still works)

At GRUB menu:

If old kernel works → your custom kernel is broken, not system.


9. Worst case (still fixable)

If nothing works:


If you want next step help

Tell me:

I can give a precise recovery path based on that.


Back Donate