#boot fails after update

5 messages · Page 1 of 1 (latest)

proud helm
#

failed to open kernel path boot() vmlinuz-linux

after an update the boot is broken, this is what i got for gpt. am i on right track?

# 0) Clean slate
swapoff -a
umount -Rl /mnt 2>/dev/null || true
cryptsetup close cryptroot 2>/dev/null || true

# 1) Unlock Omarchy (on nvme0n1)
cryptsetup open /dev/nvme0n1p2 cryptroot

# 2) Mount the REAL root (btrfs subvol @) + EFI
mount -o subvol=@ /dev/mapper/cryptroot /mnt
mount /dev/nvme0n1p1 /mnt/boot

# 3) Bind mounts for chroot
mount --bind /dev  /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys  /mnt/sys
mount --bind /run  /mnt/run

# 4) Verify kernel path (should exist)
ls /mnt/boot/929c10e21a844aa789db0c83eecfc60f8/limine_history/

# 5) Grab UUIDs
ROOT_UUID=$(blkid -s UUID -o value /dev/mapper/cryptroot)
LUKS_UUID=$(blkid -s UUID -o value /dev/nvme0n1p2)

# 6) Set the **exact** UKI file (from your listing)
KUKI="/@/boot/929c10e21a844aa789db0c83eecfc60f8/limine_history/omarchy_linux.efi_sha256_244d05d54379782d2ef2fbf201dbe47a3d5cd41eee09859b45dad1ec6ac985"

# 7) Write Limine config (update both possible locations)
cat > /mnt/boot/EFI/limine/limine.conf <<EOF
:Omarchy
PROTOCOL=linux
KERNEL_PATH=uuid:${ROOT_UUID}:${KUKI}
CMDLINE=cryptdevice=UUID=${LUKS_UUID}:cryptroot root=UUID=${ROOT_UUID} rootflags=subvol=@ rw quiet splash
EOF

# some setups read /boot/limine.conf — mirror it too
cp /mnt/boot/EFI/limine/limine.conf /mnt/boot/limine.conf

# 8) Chroot and rebuild initramfs (safe)
arch-chroot /mnt mkinitcpio -P

# 9) Exit, unmount, reboot
umount -Rl /mnt
reboot

proud helm
#

boot fails after update

proud helm
#

completely overlooked. wow