Ubuntu
systemd package

  1. Bug #1453912
  2. Comment #2

Comment 2 for bug 1453912

Revision history for this message
Martin Pitt (pitti) wrote : Re: systemd does not allow to boot with /home on dm-crypt

> 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!