Encrypted Archlinux Installation fails to boot

  • Maybe you could try to remove the "quiet" flag from the bootloader entry. Not sure if it does something, but maybe it lets the boot process talk a bit:)

    i never used it :)

    systemd-boot is an EFI bootloader, but netcup doesn't support EFI firmwares yet.

    Netcup's VMs need to boot with MBR. Try GRUB instead of systemd-boot.

    thanks, i did not know this - will try and report back.

  • ok, i achieved the next step. grub boots into a password prompt.

    A password is required to access the cryptroot volume:
    Enter passphrase for /dev/sda3:

    after i enter the passphrase the boot runs into an error. apparently the encrypted volume does not exist.

    Scanning for Btrfs filesystems
    Waiting 10 seconds for device /dev/mapper/btrfs-system ...
    ERROR device /dev/mapper/btrfs-system not found. Skipping fsck.

    after that i am dropped into the grub emergency shell.

    maybe somebody can shed some light on this with the following informations:

    root@archiso ~ # lsblk -o name,uuid
    NAME             UUID
    |-sda2           7E46-BADF
    `-sda3           8cae1a86-a479-4889-9d2b-da0c7e2d3402
      `-btrfs-system e59d11f1-8b57-4120-acb9-1f6cd689aae3
    sr0              2019-07-01-15-06-24-00