You are not logged in.

#1 2020-03-23 14:18:44

Registered: 2016-12-05
Posts: 10

Fresh install with 2 encrypted drives does not boot

I am trying to install arch linux on a x220i laptop with two encrypted drives. So far, everything works fine when booting via the live usb and mounting everything manually. However, when I try booting into the new system regularly, I am presented the boot menu, listing the two drives, but selecting either one of them does not result in anything (the screen seems to be reloaded, but that's it).

I prepared the two drives according to … VM_on_LUKS, with the modification that boot (unencrypted), root and swap are on one drive, home on the other. Here is my partition layout:

lsblk -f
NAME             FSTYPE      FSVER    LABEL       UUID                                   FSAVAIL FSUSE% MOUNTPOINT
loop0            squashfs    4.0                                                                        
`-sda1           crypto_LUKS 2                    7d773fff-cf2d-4792-bc6c-f5b0974c5a03                  
  `-pvdat        LVM2_member LVM2 001             uCq66w-VrFd-DEar-Box3-UH5t-3kEj-gqbky8                
    `-vgdat-home ext4        1.0                  4ad6e708-0fbb-4fa8-82ff-332dd2898116    277.4G     0% /home
|-sdb1           ext4        1.0      boot        2ee0e6d4-eda3-4ffb-a509-15b9c2202608    404.2M    10% /boot
`-sdb2           crypto_LUKS 2                    714a6ded-f62a-499c-a5be-4676ed786a6c                  
  `-pvsys        LVM2_member LVM2 001             2F8dq2-UGHy-mMYE-xGRf-1yXJ-B5TQ-yHDsuJ                
    |-vgsys-swap swap        1        swap        fe533e6d-9ca0-4b31-be79-841e50647f6c                  
    `-vgsys-root ext4        1.0                  c967f9d9-d8fa-4a67-98dc-e8b715b9b6c9     51.5G     4% /
sdc              iso9660              ARCH_202002 2020-02-01-06-56-28-00                                
|-sdc1           iso9660              ARCH_202002 2020-02-01-06-56-28-00                                
`-sdc2           vfat        FAT16    ARCHISO_EFI 0F01-CE05  

For the rest of the installation I followed the installation guide and edited mkinitcpio.conf, syslinux.cfg, fstab and crypttab the following way:


HOOKS=(base udev autodetect keyboard keymap consolefont modconf block encrypt lvm2 filesystems fsck)


PROMPT 0        # Set to 1 if you always want to display the boot: prompt
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl

# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32

# Refer to
MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std

LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/vgsys/root cryptdevice=UUID=714a6ded-f62a-499c-a5be-4676ed786a6c:pvsys rw
    INITRD ../initramfs-linux.img

LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/vgsys/root cryptdevice=UUID=714a6ded-f62a-499c-a5be-4676ed786a6c:pvsys rw
    INITRD ../initramfs-linux-fallback.img

        MENU LABEL HDT (Hardware Detection Tool)
        COM32 hdt.c32

LABEL reboot
        MENU LABEL Reboot
        COM32 reboot.c32

LABEL poweroff
        MENU LABEL Poweroff
        COM32 poweroff.c32


# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/vgsys-root
UUID=c967f9d9-d8fa-4a67-98dc-e8b715b9b6c9	/         	ext4      	rw,relatime	0 1

# /dev/mapper/vgdat-home
UUID=4ad6e708-0fbb-4fa8-82ff-332dd2898116	/home     	ext4      	rw,relatime	0 2

# /dev/sdb1 LABEL=boot
UUID=2ee0e6d4-eda3-4ffb-a509-15b9c2202608	/boot     	ext4      	rw,relatime	0 2

# /dev/mapper/vgsys-swap LABEL=swap
UUID=fe533e6d-9ca0-4b31-be79-841e50647f6c	none      	swap      	defaults  	0 0


# <name>       <device>                                     <password>              <options>
home	       /dev/vgdat/home 				    /root/keyfile

Any hints/ideas why the system does not boot or things to do to find out?


#2 2020-03-24 23:53:44

Registered: 2012-12-16
Posts: 88

Re: Fresh install with 2 encrypted drives does not boot

Are you sure you do not need any modules besides ext4 in your mkinitcpio.conf? For instance any particular ciphers or hashing algorithms you use? (Some time ago, it was also required to include dm_crypt and dm_mod and I still do that as it does not do any harm. But since the manual doesn't mention it, I guess that may no longer be required.)

You are saying, the boot menu lists two "drives"? Do you mean that it lists two boot options (regular and fallback would be typical. these are not drives), or do you mean actual drives (which would be very unconventional)? In the latter case, what are these drives or how do you know they are drives?

Also, can you tell us a bit more about how the device does not boot (how selecting any of the two options does not result in anything)? Does it get to the point where it queries for the passphrase? Does it show any errors? Does your boot loader show any output at all (If not, you may be able to change that, e.g. if you have grub, you can remove the quiet option from GRUB_CMDLINE_LINUX_DEFAULT in the grub config /etc/default/grub)?

Last edited by gay (2020-03-25 00:03:21)

We are exactly the people our parents always warned us about.


Board footer

Powered by FluxBB