touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #70871
[Bug 1443413] Re: boot fails on cryptsetup random swap partition with "invalid argument"
Hang on, I think there's something wedged here. You already have a
/dev/mapper/vg-swap but this is *not* being created by crypttab as that
obviously fails. This is also what confused me at first in comment 5. If
you already have an LV which is called vg-swap, you can't additionally
define a cryptswap target with the same name. I. e. you are trying to
have /dev/mapper/vg-swap being the underlying encrypted device for the
to-be-created /dev/mapper/vg-swap encrypted device.
Can you please rename vg-swap in /etc/crypttab and /etc/fstab to
something else, like "cryptswap1"?
--
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:
boot fails on cryptsetup random swap partition with "invalid argument"
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
References