You are not logged in.
SOLUTION: add "plain," in front of "cipher=..." in your /etc/crypttab
Hi all fine arch people!
I haven't updated my system for 6 months (yes very sorry :)), and today after -Syyu it doesn't accept my passphrase anymore to decrypt /home and obviously refuses to continue booting.
This line fails during startup, and then also when entered manually:
/usr/lib/systemd/systemd-cryptsetup attach home /dev/sda4 none cipher=aes-xts-essiv:sha256,size=256
crypt_load() failed on device /dev/sda4
Failed to activate: Invalid argument
I enter the same line ^ in a LiveCD (2015.01) - mounts just fine to mapper. So passphrase is correct and no data corruption anywhere, whew! `,:)
My /etc/crypttab entry:
home /dev/sda4 none cipher=aes-xts-essiv:sha256,size=256
modprobe xts didn't help, neither downgrading cryptsetup nor libgcrypt one release down (to that of February 2015). diff on lsmod livecd vs today' update didn't yield anything suspicious, and all removed modules i have modprobed - still no dice.
Also added hash=none as per https://wiki.archlinux.org/index.php/Dm … n#crypttab - nothing.
Is it something about kernel module, or initramfs hooks? Haven't done anything special for those when setting everything up, and system worked flawlessly for half a year.
Pls tell me what announcement I have missed :)
Cheers,
sledge
Last edited by sledge (2015-08-15 09:39:46)
Offline
downgraded systemd from 224 back to 218 - everything works again (
Offline
Here's the culprit, waiting for a fix... https://github.com/systemd/systemd/issues/442
Offline
adding "plain," in front of "cipher=..." solves the problem. GitHub issue is for those who don't know about the neccessity of such explicit specifier
Offline