This seems still flaky even in 17.04.
# cat /etc/crypttab
nvme0n1p3_crypt UUID="20eada6e-6b8c-4e19-b612-524ea2a131ff" none luks,discard
# update-initramfs -k 4.10.0-24-generic -c -b /boot
update-initramfs: Generating /boot/initrd.img-4.10.0-24-generic
cryptsetup: WARNING: Invalid source device
UUID="20eada6e-6b8c-4e19-b612-524ea2a131ff"
cryptsetup: WARNING: Invalid source device
UUID="20eada6e-6b8c-4e19-b612-524ea2a131ff"
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
# vi /etc/crypttab
# cat /etc/crypttab
nvme0n1p3_crypt UUID=20eada6e-6b8c-4e19-b612-524ea2a131ff none luks,discard
# update-initramfs -k 4.10.0-24-generic -c -b /boot
update-initramfs: Generating /boot/initrd.img-4.10.0-24-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
In other words, when the UUID is quoted (") it fails. However, the
quoted UUID is exactly what at least one of the other tools in Ubuntu
must use because there was a second line in that file originally (I
removed it to make the example/testcase above clearer) for another drive
and that one uses quotes.
Please review and QA this area properly. Thank you.
** Also affects: cryptsetup
Importance: Undecided
Status: New
** No longer affects: cryptsetup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/332950
Title:
Misleading "cryptsetup: WARNING: invalid line in /etc/crypttab - "
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/332950/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
