I recently switched to systemd and have some issues with a multi-device (raid1) btrfs volume.My fstab contains this line for the volume:/dev/mapper/archive1 /mnt/archive btrfs device=/dev/mapper/archive1,device=/dev/mapper/archive2,device=/dev/mapper/archive3,device=/dev/mapper/archive4,defaults,noatime,nodiratime 0 0As you can see, the volume consits of four LUKS mapper devices, which must all be
[art@julie ~]$ dmesg | grep sr[ 0.000000] Command line: root=/dev/mapper/julie-root2 ro init=/usr/lib/systemd/systemd[ 0.000000] Kernel command line: root=/dev/mapper/julie-root2 ro init=/usr/lib/systemd/systemd[ 1.156018] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray[ 1.156206] sr 3:0:0:0: Attached scsi CD-ROM sr0[
I have an encrypted loopback volume.
I need to mount and umount manually the volume so I use cryptsetup luksOpen and cryptsetup luksClose .
However, When I invoke this command it pops up the /dev/mapper device under all the sessions under gnome/xfce/kde/unity ...
And then it let the user to mount (with password), expulse and unmount the volume.
It's quite annoying in a multi user server (you ar
systemd seems to stuck on mounting an encrypted volume, when I set the init to /usr/sbin/systemd in grub.cfg,
I have one line in /etc/crypttab
secure /dev/sda8 /etc/cb.key
That works with original init program, but when I switched to systemd, it stuck at
[ OK ] Reached target Encrypted Volume
And it got the right device name, right mapper name, but just won't go on.
I have an encrypted loopback volume.
I created an encrypted container via
#!/bin/bash
dd if=/dev/zero of=$1 bs=1 count=0 seek=1G
MAPPER=$(mktemp -up /dev/mapper)
LOOPDEV=$(losetup --find --show dm1)
cryptsetup luksFormat $LOOPDEV
cryptsetup luksOpen $LOOPDEV $(basename $MAPPER)
mkfs.ext3 $MAPPER
cryptsetup luksClose $MAPPER
losetup -d $LOOPDEV
i.e. a file e.g.
Thanks for the prompt response. Ok, the key to my partition is a file based key, which is GPG encrypted. In order to use the key, I need to enter the password to GPG to decrypt the key, so that it can be used by cryptsetup. As far as I know there is no way to get crypttab working in this scenario.
At first I had a problem in which the initramfs didn't map LVM partitions to /dev/vg0/lv, only /dev/mapper/vg0-lv. I changed /dev/vg0/root to /dev/mapper/vg0-root in bootloader configuration as a hacky workaround.Getting closer to a working system, systemd failed boot because my fstab entries are uuids, and for some reason, my LVM volumes aren't showing up in /dev/disk/by-*.
With 11.2 I let it do a default install using LVM+encrypted and all went smoothly. I haven't used LVM before. I've done normal encrypt -cryptsetup LUKS- before and could always boot a rescueCD, run appropriate commands and mount chosen device to do backups or whatever.