This smells a lot like bug 953875. To confirm, can you please give me
the output of
cat /etc/crypttab
sudo blkid
Does it boot again if you comment out the cryptswap1 device from
/etc/crypttab?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1443413
Title:
can't boot with systemd
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Booting with systemd fails always at same stage.
Using upstart just works.
grep GRUB_CMDLINE_LINUX /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX="systemd.log_target=kmsg systemd.log_level=debug"
grep debug /boot/grub/grub.cfg
linux /vmlinuz-3.19.0-13-generic root=/dev/mapper/vg-root ro
systemd.log_target=kmsg systemd.log_level=debug
Sadly systemd-debug doesn't reveals more information what fails :-(
lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1443413/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
