Hello UM friends!
I was pretty sure that I had already posted about this problem back at the beginning of this year but I seem unable to locate my post. Also, being on a time constrain then, I sadly ended up reinstalling both systems so I could resume my activities. But today I am yet again facing this issue.
So the problem that I am facing is that after installing the latest batch of updates (kernel included), I am now unable to boot onto my encryption partition on a Dell XPS13 laptop. The error I have is "WARNING: sda5_crypt: lvm is not available".
At boot/GRUB, I can either select "4.18.0-13-generic" or "4.18.0-15-generic". When I select either one I am then prompted for my partition password, which I key in, and then then get greeted by the initramfs prompt.
Here are the last couple of lines of when booting in recovery mode (from either versions) and that displayed immediately after that I got the "lvm is not available" error.
random: 7 urandom warning(s) missed due to rate limiting
Begin: waiting for suspend/resume device ... Begin: Running /scripts/local-block ... done.
Gave up waiting for suspend/resume device
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Gave up waiting for root file system device. Common problems:
<2 lines of generic examples removed here>
ALERT! /dev/mapper/ubuntu--mate--vg-root does not exist. Dropping to a shell!
As I remember posting back then: I feel challenged when facing the initramfs prompt hence there are so many things that I can think of doing in such situations. Off those ones I did tried and can confirm that:
- I see my drive listed @ /dev/disk/by-id (It is a M.2 drive, if that matters?);
- lsblk being not available I am unable to provide more detail;
- /etc/fstab is not present (most possibly missing mount/irrelevant).
So that's where I am right now.
Any ideas and/or anybody else having this issue?