View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004435Kali LinuxGeneral Bugpublic2017-12-21 16:502018-09-11 16:50
Reportergilm0079 Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionsuspended 
Product Version2017.3 
Summary0004435: boot doesn't find encrypted volume group
Description

This is the 2nd time now in 1 week that my Kali install no longer works. I followed the instructions on installing Kali both as a dual boot (grub loader is first) and on an encrypted LVM partition. The install works fine for a few days then it will stop booting. It starts with the error in boot failed to connect to lvmetad. failing back to device scanning... Does that for a while then gives up. At the end of the attempts if errors with alert. /dev/disk/by-uuid/<uuid> does not exist. I can confirm what it is looking for for the UUID does not exist there, but a different UUID formatted item in that directory does. Can someone give me pointers on where to look next to track down this problem. the /etc/fstab file is empty. there is no /etc/crypttab file. not sure if initfsram requires an update to fix.

Thanks in advance. I know enough in linux to get around, but nothing advanced.

Steps To Reproduce

Once it starts it will happen on every boot. something gets trashed.

Activities

rhertzog

rhertzog

2017-12-22 08:32

administrator   ~0007735

You should really try to pin-point what trashes your installation. As you use Kali as the root user, it's easy to make mistakes that will brick your system.

The "Failed to connect to lvmetad" error is harmless. You get it in a working boot too. An empty /etc/fstab does not look good however, but is this on your root filesystem or in the initrd ?

What devices are detected ? Where do the dev/disk/by-uuid/* entries point to ? Do they correspond to encrypted partitions ?

In any case, I doubt that we can help you fix this issue. We're not having such a problem.
g0tmi1k

g0tmi1k

2018-09-11 16:50

administrator   ~0009666

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x/2017.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
2017-12-21 16:50 gilm0079 New Issue
2017-12-22 08:32 rhertzog Assigned To => rhertzog
2017-12-22 08:32 rhertzog Status new => feedback
2017-12-22 08:32 rhertzog Note Added: 0007735
2018-06-08 15:34 g0tmi1k Priority high => normal
2018-06-08 16:02 g0tmi1k Severity major => minor
2018-09-11 16:50 g0tmi1k Assigned To rhertzog =>
2018-09-11 16:50 g0tmi1k Status feedback => closed
2018-09-11 16:50 g0tmi1k Resolution open => suspended
2018-09-11 16:50 g0tmi1k Note Added: 0009666