Bug#801342: systemd: plain dm-crypt volumes not brought up on boot

2017-04-19 Thread Jamesc Netvalue
I can confirm this bug is still present. My /etc/crypttab is correct, verified with 'cryptdisks_start bobfred' My /etc/fstab is correct, can mount /dev/mapper/bobfred on /bobfred On boot systemd handles my LUKS root partition correctly. bobfred is where systemd gets stuck. It prompts for a pass

Bug#801342: systemd: plain dm-crypt volumes not brought up on boot

2015-10-11 Thread René Wagner
Dear maintainers, it turns out that other users are affected by this, too. Over on debian-user@ Arno Schuring suggested [1] to add service files that override the default ones and call cryptdisks_start/stop as a workaround. I can confirm that with the following service files for swap and tmp my

Bug#801342: systemd: plain dm-crypt volumes not brought up on boot

2015-10-08 Thread René Wagner
Package: systemd Version: 215-17+deb8u2 Severity: normal [This was originally meant as a followup to #712439 which has been archived.] Dear maintainers, I upgraded a laptop from wheezy to jessie last weekend using dist-upgrade which installed systemd as the init system. Since the upgrade plai