> crypt /dev/mapper/main-cryptstore none luks,noearly,discard
This looks really curious -- the source device is "none", so how is that
finding out where the underlying encrypted device is? This should
usually be something like UUID=12345, or /dev/sdb3 or whatever.
Can you please boot with the systemd once, then again with upstart, and
attach /var/log/syslog here? Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453912
Title:
systemd does not allow to boot with /home on dm-crypt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
