Hi John,
Am 17.12.2015 um 17:02 schrieb John Talbut:
> On 17/12/15 11:22, Jonas Meurer wrote:
>>> 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
Hi Jonas
On 17/12/15 11:22, Jonas Meurer wrote:
Hi John,
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?
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
Attached.
+ readonly=y
+ [ -z ]
+ BOOT=local
+ [ -n ]
+ resume=/dev/mapper/dk-sw
+ maybe_break top
+ [ = top ]
+ run_scripts /scripts/init-top
+ initdir=/scripts/init-top
+ [ ! -d /scripts/init-top ]
+ shift
+ . /scripts/init-top/ORDER
+ /scripts/init-top/all_generic_ide
+ [ -e
OK, so it seems that his may be a problem with cryptsetup. Is this a
known problem? Is there a workaround?
I have tried a boot with debug on. Trace attached.
Is there anything else I can do to help diagnose the problem?
John
initramfs debug.odt
Description:
Hi John,
On Sun, 13 Dec 2015 at 18:27:33 +, John Talbut wrote:
> OK, so it seems that his may be a problem with cryptsetup. Is this a known
> problem? Is there a workaround?
AFAIK not.
> I have tried a boot with debug on. Trace attached.
Could you attach a text file instead, along with
6 matches
Mail list logo
