[RHEL7] some cryptsetup related service is not started at boot
Issue
-
When configuring LUKS devices, the journal shows the following messages during boot
systemd[1]: Found ordering cycle on cryptsetup.target/start systemd[1]: Found dependency on systemd-cryptsetup@SDB1.service/start systemd[1]: Found dependency on opt.mount/start systemd[1]: Found dependency on systemd-fsck@dev-mapper-data\x2dkey.service/start systemd[1]: Found dependency on local-fs-pre.target/start systemd[1]: Found dependency on lvm2-monitor.service/start systemd[1]: Found dependency on lvm2-activation.service/start systemd[1]: Found dependency on cryptsetup.target/start systemd[1]: Breaking ordering cycle by deleting job systemd-cryptsetup@XXX.service/start
-
Some LUKS device is not set up after booting (example below), or other error happens, such as LVM fails to activate a volume group
# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT ... sdb 8:16 0 20G 0 disk ├─sdb1 8:17 0 1G 0 part ├─sdb2 8:18 0 1G 0 part │ └─LUKS2 253:3 0 1022M 0 crypt ├─sdb3 8:19 0 1G 0 part │ └─LUKS3 253:4 0 1022M 0 crypt └─sdb4 8:20 0 1K 0 part
LUKS devices LUKS1 (hosted on sdb1) and LUKS4 (hosted on sdb4) were not opened automatically.
Environment
- Red Hat Enterprise Linux 7
- cryptsetup
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.