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.
This seems still flaky even in 17.04.
# cat /etc/crypttab 6b8c-4e19- b612-524ea2a131 ff" none luks,discard img-4.10. 0-24-generic 6b8c-4e19- b612-524ea2a131 ff" 6b8c-4e19- b612-524ea2a131 ff" mdadm.conf defines no arrays.
nvme0n1p3_crypt UUID="20eada6e-
# update-initramfs -k 4.10.0-24-generic -c -b /boot
update-initramfs: Generating /boot/initrd.
cryptsetup: WARNING: Invalid source device UUID="20eada6e-
cryptsetup: WARNING: Invalid source device UUID="20eada6e-
W: mdadm: /etc/mdadm/
# vi /etc/crypttab 6b8c-4e19- b612-524ea2a131 ff none luks,discard img-4.10. 0-24-generic mdadm.conf defines no arrays.
# cat /etc/crypttab
nvme0n1p3_crypt UUID=20eada6e-
# update-initramfs -k 4.10.0-24-generic -c -b /boot
update-initramfs: Generating /boot/initrd.
W: mdadm: /etc/mdadm/
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.