You are not logged in.

#1 2018-07-04 17:46:29

Registered: 2018-07-04
Posts: 3

Boot problem using bootctl, systemd on an encrypted system

Hello all, it’s been a long time for me out of archlinux, but I’m happy to be back.
As I hope so here I’ve my first problem.

Trying to boot after an installation with a partial encryption of an SSD, UEFI system, this is what I get in return:

Timed out waiting for device dev-mapper-hellvolgroup\x2droot.device
Dependecy failed for initrd root device
Dependecy failed for /sysroot
Dependecy failed for Initrd root file system...

Here are some useful files


 # /dev/mapper/hellvolgroup-root
UUID=53a5e548-ce14-436a-b1fc-96d7b6c5a93b	/         	ext4      	rw,noatime,data=ordered	0 1

# /dev/sdb1
UUID=E180-7C0B      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/mapper/hellvolgroup-home
UUID=945a0a20-8485-484d-a09c-9de8c539a8bb	/home     	ext4      	rw,noatime,data=ordered	0 2

# /dev/mapper/hellvolgroup-swap
UUID=a0db69f7-6818-4731-8fd7-f737122d08aa	none      	swap      	defaults,pri=-2	0 0


title ArchLinux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options luks.uuid=53a5e548-ce14-436a-b1fc-96d7b6c5a93b root=/dev/mapper/hellvolgroup-root rw 


loop0                     7:0    0 460.7M  1 loop  /run/archiso/sfs/airootfs
sda                       8:0    0 931.5G  0 disk  
└─sda1                    8:1    0 931.5G  0 part  
sdb                       8:16   0 232.9G  0 disk  
├─sdb1                    8:17   0   549M  0 part  /mnt/boot
└─sdb2                    8:18   0 104.5G  0 part  
  └─hellkitch           254:0    0 104.5G  0 crypt 
    ├─hellvolgroup-swap 254:1    0     8G  0 lvm   
    ├─hellvolgroup-root 254:2    0    35G  0 lvm   /mnt
    └─hellvolgroup-home 254:3    0  61.5G  0 lvm   
sdc                       8:32   1   7.5G  0 disk  /run/archiso/bootmnt
├─sdc1                    8:33   1   571M  0 part  
└─sdc2                    8:34   1    64M  0 part  

mkinitcpio.conf Hooks

HOOKS=(base systemd sd-encrypt autodetect keyboard sd-vconsole modconf block sd-lvm2 filesystems fsck)


#2 2018-07-05 10:20:48

Registered: 2018-07-04
Posts: 3

Re: Boot problem using bootctl, systemd on an encrypted system

I think that the error is in the hooks order or in the bootctl conf, I’m not sure if I’m recalling correctly the root partition, any suggest?


#3 2018-07-05 10:56:59

Forum Moderator
Registered: 2012-10-16
Posts: 5,450

Re: Boot problem using bootctl, systemd on an encrypted system … _with_LUKS (or the relevant lvm on luks or luks on lvm subheading)

If you use


the follow up mapper would have to be


if I'm interpreting … .luks.uuid correctly. Use instead.

And make sure that that UUID is actually the correct one you have to use the one of the container not the particular subvolume in the bootloader conf. That said, you are right the hook order is incorrect as well, according to the linked wiki snippet, which instructions are you following?

Last edited by V1del (2018-07-05 11:12:28)


#4 2018-07-05 11:29:47

Registered: 2018-07-04
Posts: 3

Re: Boot problem using bootctl, systemd on an encrypted system

Changed as per guide instruction, same problem as before

A start job is running for dev-disk-by\x2duuid-53a5e548\x2dce14\x2d436a\x2db1fc\x2d96d7b6c5a93b.device ... ... Usb 1-1: device descriptor read/64, error -110

(I copied it by hand, don’t know where I can  get this error once I booted by Usb installation)

My option line in /boot/loader/entries/arch.conf

options root=/dev/mapper/hellvolgroup-root

Is that right? I notice some difference in the name, nor the uuid, hellkitch is the name I assigned when I used: cryptsetup open /dev/sdb2 hellkitch ; /dev/mapper/hellvolgroup-root is the name where I found the partition; do I write them correct in the option line?

Last edited by hellkitchen (2018-07-05 14:28:32)


#5 2018-07-06 15:45:31

Wiki Maintainer
Registered: 2016-07-02
Posts: 93

Re: Boot problem using bootctl, systemd on an encrypted system

hellkitchen wrote:

UUID=53a5e548-ce14-436a-b1fc-96d7b6c5a93b    /             ext4          rw,noatime,data=ordered    0 1

hellkitchen wrote:

options root=/dev/mapper/hellvolgroup-root

rd.luks=... specifies the UUID of the encrypted volume, root fs UUID in fstab specifies the UUID of unencrypted filesystem residing in hellvolgroup-root. These UUIDs cannot be identical, one of them is wrong,

Post the output of:


The UUID in the line with TYPE="crypto_LUKS" is the one you need to put in the rd.luks line, and the UUID in the line with "/dev/mapper/hellvolgroup-root" goes in the fstab.


Board footer

Powered by FluxBB