View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001963Kali LinuxGeneral Bugpublic2014-12-27 12:522018-01-29 11:40
Reporterpeterrus Assigned Tog0tmi1k  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionsuspended 
Product Version1.0.9 
Summary0001963: Encrypted LVM fails to boot, volumegroup is searched before encrypted volume mapped
Description

I have installed kali 1.0.9 (and kali-daily, same results) on a HP Stream 11.

I used the live installer as booting in text/gtk installer mode doesn't detect my mmc ssd nor external wireless card (internal wasn't detected in any mode). I think this is a different issue entirely.

After installing the booting fails with a message regarding the kali-root lvm volume group can't be found. I got dropped to the initramfs prompt.

I have seen the following issue: https://bugs.kali.org/view.php?id=443 which might be related. I was however unable to install kali through the dedicated installer boot-mode as this would not detect my mmc ssd nor wireless card, as stated above.

Steps To Reproduce
  • Boot kali 1.0.9 live
  • Run the installer
  • Choose guided whole disk encrypted lvm as partitionscheme
    (This means you get a boot partition and an encrypted partition containing the lvm volumegroup, which contains a root and a swap partition)
  • finish install
  • boot system
Additional Information

Workaround:

manually map the luks container while in the initramfs prompt with:

cryptsetup luksOpen /dev/<partition> <partition>_crypt
vgchange -ay
exit

The boot should now continue normally.

As a sort of permanent workaround I have this:

root@kali:~# cat /etc/initramfs-tools/scripts/local-top/cryptfix
PREREQ=""
prereqs()
{
echo "$PREREQ"
}

case $1 in
prereqs)
     prereqs
     exit 0
     ;;
esac

cryptsetup luksOpen /dev/mmcblk0p3 mmcblk0p3_crypt
lvm vgscan
lvm vgchange -ay

So creating that file, with those contents, and then running 'update-initramfs' should fix booting (in a very hacky way I suppose)

Activities

g0tmi1k

g0tmi1k

2018-01-29 11:40

administrator   ~0008031

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2014-12-27 12:52 peterrus New Issue
2018-01-29 11:40 g0tmi1k Assigned To => g0tmi1k
2018-01-29 11:40 g0tmi1k Status new => closed
2018-01-29 11:40 g0tmi1k Resolution open => suspended
2018-01-29 11:40 g0tmi1k Note Added: 0008031