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

[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 password, gets that right and can see the filesystem then
loops infinitely with 'a start job' nonsense - it doesn't know what to do
next.

Please abandon systemd, if that is not an option a bugfix would be nice.

Thanks
James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170419/75fdbc19/attachment.html>