You are not logged in.
Boot error: A start job is running for dev-mapper-home.device (11min 01s / no limit)
It just hangs here forever. Never makes it past. I'm guessing the "no limit" is one problem. The other being that I can't boot.
I have my home partition encrypted with dm-crypt. Root and boot partitions are not. The home partition is accessible when I do it manually with the commands:
$ cryptsetup open /dev/sda7 home
$ mount /dev/mapper/home /home
Unfortunately, trying to use crypttab and fstab are not working.
My crypttab entry:
home /dev/sda7 none plain
My fstab entry:
/dev/mapper/home /home ext4 defaults 0 0
UPDATE
Tried switching to using LUKS instead of plain. After reformating the partition, and updating the crypttab to state luks instead of plain, gets further, but still not correct. It asks for a password and then gives error about invalid option for systemd-cryptsetup. This happens no matter what password I put in, correct or not.
Last edited by HuckleSmothered (2016-02-20 00:56:19)
Offline
If you have listed your code correctly, then the problem may be this:
mount /dev/mapper/home /home
When installing, you are supposed to use /mnt:
mount /dev/mapper/home /mnt/home
This is so when you use genfstab, it doesn't get confused with the mounted ISO. Have another look at /etc/fstab.
Edit: check you have added "encrypt" to mkinitcpio, and check that your bootloader is correctly configured for encryption.
Last edited by CarlD (2016-02-22 20:32:16)
Offline
I already had the system installed. I was reformatting the /home partition to be encrypted. So I wasn't using genfstab. But I did change my /dev/sdaX to /dev/mapper/home when I reformatted it in fstab.
Offline
Can it be a keymap problem?
Did you use special cipher or hash options when using cryptsetup luksFormat?
Offline