Arch Linux

Fort

Member

Registered: 2024-12-15

Posts: 2

Struggling to boot Arch with FDE

Hey y'all!

I've been running Ubuntu for a while now, but Arch has always been attractive to me. Recently, the Windows instance I was dual booting got borked, and so I decided that I would just go all in on Linux, including swapping to Arch. I did a bit of research, set it up a few times in a VM just to be safe, and the other day installed it directly on my computer. I mainly followed this guide, with a few small tweaks to things like repositories and locales. It all worked fine until I got to the reboot your machine bit.

Systemd didn't register itself with my UEFI firmware, but that was an easy fix with efibootmgr, but then it wouldn't detect arch like the guide said it would automatically. After some more digging, and reading the wiki, I setup an arch.conf file that looks like this:

title   Arch Linux
efi     /EFI/Arch/arch-linux.efi
options cryptdevice=UUID=e4232a6f-d3a7-425b-88f7-edc69a0351c4:archroot root=/dev/mapper/archroot rw

That worked to make the Arch install show up, but upon booting it, it flashes the splash screen, then promptly goes to an error screen:
https://i.imgur.com/RvG0Z3i.jpeg

I've triple-checked that the UUID is right, so I'm fairly sure that isn't the problem.

/dev/nvme0n1p2: UUID="e4232a6f-d3a7-425b-88f7-edc69a0351c4" TYPE="crypto_LUKS" PARTLABEL="Linux filesystem" PARTUUID="3c2a2239-e9f5-47b2-902e-0c8a90da61e8"

I've got 3 partitions on the machine: an unencrypted FAT32 EFI partition, an unencrypted Ubuntu partition, and the new Luks2 encrypted Arch partition. The sd-encryption hook does exist in the mkinitcpio.conf file, and I've regenerated the file multiple times. Not really sure how to proceed any further, hoping somebody with a bit more experience than me can figure out what's going on.

Thanks in advance!
Fort

Mod edit: Replaced oversized image with link -- V1del

Last edited by V1del (2024-12-16 16:52:30)

twelveeighty

Member

Registered: 2011-09-04

Posts: 1,451

Re: Struggling to boot Arch with FDE

1: please don't embed giant screencaps, use a MUCH smaller image, or use an image hosting service.

2: we do not support installation guides other than the official Arch Installation Guide. This was clearly stated when you signed up for the forums. Start over using that installation guide.

Fort

Member

Registered: 2024-12-15

Posts: 2

Re: Struggling to boot Arch with FDE

Okay, thanks

Last edited by Fort (2024-12-16 07:54:39)

nl6720

The Evil Wiki Admin

Registered: 2016-07-02

Posts: 714

Re: Struggling to boot Arch with FDE

options cryptdevice=UUID=e4232a6f-d3a7-425b-88f7-edc69a0351c4:archroot root=/dev/mapper/archroot rw

The sd-encryption hook does exist in the mkinitcpio.conf file, and I've regenerated the file multiple times.

"cryptdevice" is not the correct parameter for the sd-encrypt hook, you need rd.luks.name instead. See https://wiki.archlinux.org/title/dm-cry … -generator.

Edit:
I don't know why you're placing the UKI in "/EFI/Arch/" on the ESP. Only UKIs in /EFI/Linux/ will be autodetected by systemd-boot.

Last edited by nl6720 (2024-12-16 09:52:07)