[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
** Changed in: cryptsetup Assignee: TJ (tj) => (unassigned) ** Changed in: cryptsetup (Ubuntu) Assignee: TJ (tj) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
I can't make any sense of it. I have similar setups here; the systems get installed (with 18.04 as well as Disco) with nvme#n#p#_crypt devices, and those load properly. Anything else you can add about the specifics of your system? Seems like you used guided partitioning, just enabling disk encryption? Is there any way you can reproduce this on another system, or the same system, using a recent 18.04 image or a Disco image? What flavour of Ubuntu were you installing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
** Description changed:
I worked with "TJ-" on Ubuntu IRC (#ubuntu) on April 27th in order to
debug this. On a new Ubuntu 18.04 installation, it is not possible to
decrypt the volume when it's installed on an NVMe device with the
encryption selected. Changing the device-mapper name to the luks-$UUID
format apparently did something to correct it, but there's still
something else going on.
+
+ --- update from Tj ---
+
+ Dylan repeatedly installed 18.04 Desktop setting up F.D.E. with
+ (originally) a complex passphrase but later also a simple (all ASCII)
+ phrase.
+
+ At boot-time the installed system fails to unlock the device during
+ initial ramdisk processing, getting stuck in a loop and seemingly never
+ dropping to the shell for user diagnosis and correction.
+
+ Original messages (copied from the attached photo):
+
+ Please unlock disk nvme0n1p3_crypt: <--- types passphrase
+ Volume group "ubuntu-vg" not found
+ Cannot process volume group ubuntu-vg
+ device-mapper: reload ioctl on failed: invalid argument <--- note
multiple space gap
+ Failed to setup dm-crypt key mapping for device
/dev/disk/by-uuid/4bdade98-fdbe-4a9e-b287-283b4c52c1a0.
+ Check that kernel supports aes-xts-plain64 cipher (check syslog for more
info).
+
+ The volume is accessible from the Try Ubuntu session (unlocks
+ correctly).
+
+ My [Tj] suspicion was a keyboard mapping issue or initrd.img missing
+ required kernel modules for cryptographic functions.
+
+ We used a chroot environment to investigate and added "set -x" to the
+ start of /usr/share/initamfs-tools/hooks/cryptroot to capture the
+ initrd.img build using
+
+ update-initramfs -uv |& tee /tmp/uir.log
+
+ The resulting log (see attached 'broken' log) shows the warning in the
+ title of this bug twice and the root device ignored as far as
+ configuring the initrd.img goes:
+
+ WARNING: invalid line in /etc/crypttab
+
+ Analysing the log of the shell commands shows an awk command failing to
+ recognise the sole crypttab entry because it is expecting the device-
+ mapper name format to be "luks-${UUID)" not "nvme0n1p3_crypt".
+
+ Dylan made a back-up then changed the entry to use the seemingly correct
+ name format and rebuilt the initrfd.img (see attached 'working' log).
+ There is no warning now and the cryptroot hook goes ahead and adds
+ kernel modules and tooling to the initrd.img.
+
+ The system still fails to boot but with different messages:
+
+ Please unlock device luks-98c2ce02-6cb1-4a2d-a086-1e8cf78a3c58 <--- types
passphrase
+ [ timestamp ] device-mapper: table: 253:0: crypt: unknown target type
+ device-mapper: reload ioctol on failed: Invalid argument
+ Failed to setup dm-crypt key mapping for device
/dev/disk/by-uuid/98c2ce02-6cb1-4a2d-a086-1e8cf78a3c58.
+ Check that kernel supports aes-xts-plain64 cipher (check syslog for more
info).
+ cryptsetup (luks-98c2ce02-6cb1-4a2d-a086-1e8cf78a3c58): cryptsetup failed,
bad password or options?
** Description changed:
I worked with "TJ-" on Ubuntu IRC (#ubuntu) on April 27th in order to
debug this. On a new Ubuntu 18.04 installation, it is not possible to
decrypt the volume when it's installed on an NVMe device with the
encryption selected. Changing the device-mapper name to the luks-$UUID
format apparently did something to correct it, but there's still
something else going on.
--- update from Tj ---
Dylan repeatedly installed 18.04 Desktop setting up F.D.E. with
(originally) a complex passphrase but later also a simple (all ASCII)
phrase.
At boot-time the installed system fails to unlock the device during
initial ramdisk processing, getting stuck in a loop and seemingly never
dropping to the shell for user diagnosis and correction.
Original messages (copied from the attached photo):
Please unlock disk nvme0n1p3_crypt: <--- types passphrase
- Volume group "ubuntu-vg" not found
- Cannot process volume group ubuntu-vg
+ Volume group "ubuntu-vg" not found
+ Cannot process volume group ubuntu-vg
device-mapper: reload ioctl on failed: invalid argument <--- note
multiple space gap
Failed to setup dm-crypt key mapping for device
/dev/disk/by-uuid/4bdade98-fdbe-4a9e-b287-283b4c52c1a0.
Check that kernel supports aes-xts-plain64 cipher (check syslog for more
info).
The volume is accessible from the Try Ubuntu session (unlocks
correctly).
My [Tj] suspicion was a keyboard mapping issue or initrd.img missing
required kernel modules for cryptographic functions.
We used a chroot environment to investigate and added "set -x" to the
start of /usr/share/initamfs-tools/hooks/cryptroot to capture the
initrd.img build using
update-initramfs -uv |& tee /tmp/uir.log
The resulting log (see attached 'broken' log) shows the warning in the
title of this bug twice and the root device ignored as far as
configuring the initrd.img goes:
WARNING: invalid line in /etc/crypttab
Analysing the l
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
Dylan: I've updated the bug description to describe the situation as we
left it.
There is a test I'd like you to do which involves forcing a break in
initrd processing and dropping to the shell before the cryptsetup
prompt.
Once there I'd like you to verify the NVME device is visible along with
the UUIDs. I'm wondering if the scripts are so dumb that they don't
check for the presence of the underlying block device (with UUID
98c2ce02-6cb1-4a2d-a086-1e8cf78a3c58 a.k.a. partition #3) before
prompting you for the passphrase.
At boot-time interrupt GRUB by tapping the Esc key to get the GRUB boot
menu. There, highlight the default (top) entry and press 'e' to edit it.
Navigate down to the line beginning "linux ..." (the kernel command-
line) and add to it "break=premount" then press Ctrl+X (or F10) to boot
with that change.
That should lead to an initramfs busybox shell command-line.
Note: other possible break=XXX values are:
$ grep maybe_break /usr/share/initramfs-tools/init
maybe_break top
maybe_break modules
maybe_break premount
maybe_break mount
maybe_break mountroot
maybe_break bottom
maybe_break init
Once in the shell check the device is known with some or all of these
commands and any others you can think of (busybox is limited and
additional tools you'd expect in the full install won't be available):
blkid
ls -l /dev/disk/by-*/
ls -l /dev/mapper/
You can also attempt to manually unlock using:
cryptsetup open --type=luks /dev/nvme0n1p3 luks-
98c2ce02-6cb1-4a2d-a086-1e8cf78a3c58
(set the /dev/nvme0n1p3 underlying device path to whatever your
exploration has found, including possibly "/dev/disk/by-
uuid/98c2ce02-6cb1-4a2d-a086-1e8cf78a3c58" )
If that works (or fails) the resulting messages might be important so be
prepared to photograph them.
If it works, then you will see the new node ("luks-
98c2ce02-6cb1-4a2d-a086-1e8cf78a3c58") with
ls -l /dev/mapper/
And now, if this hasn't already happened automatically via udev, you
should be able to force LVM discovery of ubuntu-vg with
vgchange -ay
At this point if "ls -l /dev/mapper/" now does show a luks-
98c2ce02-6cb1-4a2d-a086-1e8cf78a3c58 node you can try to continue the
boot by pressing Ctrl+D or typing "exit". If those don't help then re-
running the entire script might be possible instead using
exec /init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767527
Title:
[18.04] Installation boot failure. WARNING: invalid line in
/etc/crypttab
To manage notifications about this bug go to:
https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
Correct to the final instruction of my last comment: At this point if "ls -l /dev/mapper/" now does show the LVM ** ubuntu --vg-root ** node for the root file-system you can try to continue the boot by pressing Ctrl+D or typing "exit". If those don't help then re- running the entire script might be possible instead using exec /init -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
** Attachment added: "blkid and lsblk" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1767527/+attachment/5129208/+files/blkid_lsblk.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
** Attachment added: "fstab" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1767527/+attachment/5129209/+files/fstab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
Once I was into the system, I ran "sudo apt clean all; sudo apt update; sudo apt -y full-upgrade", which completed successfully. Upon reboot, everything still worked. It seems to be part of the setup process itself that is broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
TJ, some new information - this is a regression. Trying the EXACT same install path with the "complex" passphrase I usually use on an old bionic "daily" build worked perfectly. I was able to boot into the system and setup my applications. I'd rather not wipe it right now, but something broke between the official 18.04 build and this one: dtaylor@dylantaylor-pc:~/Downloads$ md5sum bionic-desktop-amd64.iso 9cf2ab79a6cb8fd3cdefc34e7d1a9841 bionic-desktop-amd64.iso dtaylor@dylantaylor-pc:~/Downloads$ stat bionic-desktop-amd64.iso File: bionic-desktop-amd64.iso Size: 1829273600 Blocks: 3572816IO Block: 4096 regular file Device: fd02h/64770dInode: 19008339Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ dtaylor) Gid: ( 1000/ dtaylor) Access: 2018-04-27 19:52:52.751664153 -0400 Modify: 2018-04-04 14:37:45.311616468 -0400 Change: 2018-04-25 13:51:20.865647567 -0400 Birth: - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
It is unclear to me what the cause of this bug is. It appears to be a mismatch between the device name as encoded in /etc/crypttab, and the actual device name used at runtime by the installer, preventing the cryptsetup initramfs hook from probing and detecting the correct device (and therefore the correct kernel modules) at initramfs generation time. If that's the case, it seems more like an installer bug than a cryptsetup bug, because why should /etc/crypttab have a different name for a device than the one shown by the kernel? What is the cryptsetup config as inserted into the initramfs, in the case where things are broken? (unmkinitramfs /boot/initrd.img-$(uname -r) /tmp/unpack; cat /tmp/unpack/main/conf/conf.d/cryptroot) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
** Tags added: id-5bb295aa6470a80a24501f0f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
How was the system installed? Did this use d-i (the alternate installer image), or ubiquity? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
Information was requested in October to help us reproduce this. We would like to have this solved for 18.04.2 but need more information. ** Changed in: cryptsetup (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
Comment 11 mentions bionic-desktop images, so I'm assuming ubiquity without more information to go on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
This system was installed with Ubiquiti. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
