Bug#727708: systemd status when using multiple block device layers (MD/LVM/dm-crypt) below the root-fs
Christoph Anton Mitterer <calestyo@scientia.net> writes:
> On Tue, 2013-12-31 at 11:15 -0800, Russ Allbery wrote:
>> For whatever it's worth, I've been using systemd on a system with LVM and
>> dm-crypt (with LUKS) for about a month now, in the dm-crypt -> LVM ->
>> filesystem mode, and haven't had any trouble.
> Do you use it on your root-fs? With keyscripts?
I'm probably not using keyscripts since I don't know what that is. The
crypt setup is whatever the wheezy installer does. I have an unencrypted
boot partition, and then everything else is in LVM and encrypted,
including swap.
It's probably a fairly simple setup as these things go, hence the "for
whatever it's worth." Basically, all I can establish is that systemd
doesn't seem to have any trouble with the standard encrypted disk setup
created by the wheezy installer. Given that, per Tollef, it's handled by
initramfs before systemd is started, that's not surprising. :)
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: