I'm getting a bit over my head, but it is seeming like there's a problem with creating a new initrd.
When I decrypt (using unmkinitramfs) the initrd.img file, I see that the "good" version has a /main/cryptroot/crypttab file which appears identical to /etc/crypttab. The "bad" version has an empty file there (0 bytes).
Attempting to manually repair (using sudo update-initramfs -u) gives the following error:
cryptsetup: WARNING: target 'tmpData' not found in /etc/crypttab
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set RESUME variable to override this.
The file thus generated has a zero-byte crypttab file as before.
Therefore, I'm thinking the problem is here, in the generation of the initramfs. Anyone have a clue from the above? Should I be posting a new bug report indicating that update-initramfs is failing?
I'm getting a bit over my head, but it is seeming like there's a problem with creating a new initrd.
When I decrypt (using unmkinitramfs) the initrd.img file, I see that the "good" version has a /main/cryptroot /crypttab file which appears identical to /etc/crypttab. The "bad" version has an empty file there (0 bytes).
Attempting to manually repair (using sudo update-initramfs -u) gives the following error: vgubuntu- swap_1)
cryptsetup: WARNING: target 'tmpData' not found in /etc/crypttab
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/
I: Set RESUME variable to override this.
The file thus generated has a zero-byte crypttab file as before.
Therefore, I'm thinking the problem is here, in the generation of the initramfs. Anyone have a clue from the above? Should I be posting a new bug report indicating that update-initramfs is failing?