Hi John, Am 13.12.2015 um 19:27 schrieb John Talbut: > OK, so it seems that his may be a problem with cryptsetup. Is this a > known problem? Is there a workaround?
apparently, something is wrong with your lvm processing during initramfs stage. Obviously, you have an LVM volume group 'dk' on top of the encrypted luks device /dev/sda2. > I have tried a boot with debug on. Trace attached. For some reason, the volume group is not activated by the cryptroot script during initramfs stage. From the debug log it looks like sda2_crypt is not unlocked. Is this correct or are you asked for a passphrase during initramfs? > Is there anything else I can do to help diagnose the problem? In the initramfs emergency shell that starts, please run the following commands and send us the result: # ls -al /dev/mapper/ # dmsetup table and # sed -i -e 's#/bin/sh#/bin/sh -x#g' /scripts/local-top/cryptroot # /scripts/local-top/cryptroot> Cheers jonas
signature.asc
Description: OpenPGP digital signature
