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

[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
system boots normally:

$ cat /etc/systemd/system/systemd-cryptsetup at swap.service
[Unit]
Description=Foo
Before=dev-mapper-swap.swap
DefaultDependencies=no
IgnoreOnIsolate=yes

[Service]
Type=oneshot
ExecStart=/usr/sbin/cryptdisks_start %i
ExecStop=/usr/sbin/cryptdisks_stop %i
RemainAfterExit=yes

$ cat /etc/systemd/system/systemd-cryptsetup at tmp.service
[Unit]
Description=Foo
Before=%i.mount
DefaultDependencies=no
IgnoreOnIsolate=yes

[Service]
Type=oneshot
ExecStart=/usr/sbin/cryptdisks_start %i
ExecStop=/usr/sbin/cryptdisks_stop %i
RemainAfterExit=yes

However, I believe this is just a workaround that should not be necessary.

Cheers,

Rene


[1] https://lists.debian.org/debian-user/2015/08/msg00371.html