I fetched the debug log using the debug console, however it's contents
do not look suspicious to me...
systemd seems to try to start the cryptsetup service, the only question
probably is where the password prompt does end up...
** Attachment added: systemd jounal fetched using debug console.
Gunter,
sorry about the none comment #2, that was obviously bogus, I mis-
looked.
Can you please follow /usr/share/doc/systemd/README.Debian to boot with
a debug shell, then switch to it once it stalls, run journalctl -ab
/root/journal.txt, reboot, and attach /root/journal.txt here?
--
You
@Anders: There is no syslog for a systemd boot. Can you please do the
same exercise as in comment #9, attach the journal, and additioally
/etc/crypttab and /etc/fstab? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Requested syslog attached (for real).
** Attachment added: Syslog for two consecutive boots (systemd,upstart)
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412564/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch
Requested syslog attached.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1453912
Title:
systemd does not allow to boot with /home on dm-crypt
Status in systemd package
When I boot using systemd, nothing is logged at all - maybe booting
stalls even before rsyslogd is started?
If I boot using upstart, the syslog is as follows - note the massive
delay before activation of org.freedesktop.UDisks2 which causes the
boot process to take quite long - Kubuntu 14.10 had
I have a very similar issue. Upstart works but systemd does not. Lucs
encrypted logical volume on a work computer. It has worked flawless with
boot for many versions of Ubuntu (even before upstart I think). I can
produce the syslog with two boots tomorrow. Also have taken a picture of
the actual
Some setup info as previous post:
sda5_crypt UUID=acdea251-1e21-4612-afce-4101e364d6c6 none luks
cryptswap1 /dev/dm-1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
mount -l with upstart
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc
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
none is the key file:
crypttab(5):
The third field, key file, describes the file to use as a key for
decrypting the data of the source device. Note that the entire key file
will be used as the passphrase; the passphrase must not be followed by a
newline character.
However I'll try booting with
10 matches
Mail list logo
