I found a bug in the cryptroot script run by update-initramfs. On line 523 it tests for a return value from add_device(), and prints an error message.
if ! modules=$(add_device "$dev"); then ...
This statement will never be true, therefore the user is never notified of the error.
I did receive a warning message, indicating that there's no valid entry for my volume group in /etc/crypttab. However, I can't see why it's even necessary to have anything in crypttab, because by the time the rootfs is accessible, and thus /etc/crypttab, the crypt has already been opened.
I found a bug in the cryptroot script run by update-initramfs. On line 523 it tests for a return value from add_device(), and prints an error message.
if ! modules= $(add_device "$dev"); then ...
This statement will never be true, therefore the user is never notified of the error.
I did receive a warning message, indicating that there's no valid entry for my volume group in /etc/crypttab. However, I can't see why it's even necessary to have anything in crypttab, because by the time the rootfs is accessible, and thus /etc/crypttab, the crypt has already been opened.
However, this page says that an entry is required in /etc/crypttab. Why? /help.ubuntu. com/community/ EncryptedFilesy stemLVMHowto
https:/