6

I've been running 17.04 for a while now, and other versions before that. A couple of days ago, I tried to install 18.04 (a new install, not an upgrade). I selected to erase and encrypt the drive. After the install finishes (apparently without error), and reboots, it reports

Failed to connect to lvmetad. Falling back to device scanning.

and repeats this error several times before dropping me into the initramfs shell. It never asks for the encryption passphrase.

On a whim, I tried installing LVM without encryption. That didn't work either, it seems to lock up solid before even beginning to print boot messages.

This is on a ThinkPad W530.

solsTiCe
  • 9,231
Norm
  • 171
  • 1
  • 1
  • 4
  • Please see if these answers solve your problem and let us know: https://askubuntu.com/questions/693683/how-to-fix-the-error-warning-failed-to-connect-to-lvmetad-falling-back-to-intern?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa – WinEunuuchs2Unix Apr 30 '18 at 01:43
  • I have tested ubuntu-18.04-desktop-amd64.iso (in legacy mode), and ubuntu-18.04-desktop-amd64.iso (in legacy and uefi mode), I can't reproduce your problem. Can you please tell me which version of the iso did you use? Can you also add the output of sha256sum yourimage.iso to your question? – pim May 01 '18 at 11:03
  • As I noted in the followup answer, my problem turned out to be related to unetbootin. Nothing to do with Ubuntu at all. But thanks for trying to help! – Norm May 02 '18 at 14:51

4 Answers4

2

This recovery method seems to be the best one I found so far, and the only one that works every time:

At the initramfs prompt, type 

fsck /dev/mapper/ubuntu--vg-root -y

(Although you may have to substitute your particular root file depending on the "flavor" of Ubuntu you have. For example, I have Ubuntu Studio, so my root file is actually ubuntu--studio--vg-root. You can ls your /dev/mapper directory to verify the root file name.)

This should scan and auto-fix the root file issues. Once it is done and you are back at the prompt, type reboot and it should now boot normally. If you get the Ubuntu version list after you reboot, just select Ubuntu.

Also, keep a copy of the 18.04 ISO handy, either on burned disc or USB stick. If this does not fix your issue, then you will have to recover using that.

You are definitely not the only one with this issue. This seems to be a persistent bug with 18.04, as I have been dumped into initramfs many times now, even with consistent updates and no other version before this has dumped me to initramfs, only 18.04. Hopefully 18.10 will fix this root file corruption issue.

Zanna
  • 70,465
user833874
  • 21
1

I decided to give up on Ubuntu 18.04 and give Debian Stable a try. The Debian installer warned me that I'd used unetbootin to create my USB stick and that that was believed to be problematic.

I went back and created the Ubuntu 18.04 installer stick by just 'dd'ing the ISO onto the stick. And it all installed just fine.

The culprit, in my case at least, appears to have been some quirk of unetbootin. I've now got some sort of display driver issue but this is a laptop running Linux, so of course I do.

Norm
  • 171
  • 1
  • 1
  • 4
0

I just installed today and ran into a few error....all kind...well nothing was working properly. I just booted again from the flash and started all over....eliminating all partitions and starting fresh clean. I used the LVM option under encrypt options ( I did not use the encrypt option). When finished I removed the flash drive and restarted. This last time I tried the ubuntu first then from the desktop I ran the installation. I hope this works for you. Also I set the bootable flash on fat32 instead of NTFS.

JavierNCC
  • 1
  • 1
0

I had this same problem upgrading from 16.04 on my xubuntu desktop. After displaying this message, it asked me if I wanted to log into the maintenance terminal. I tried another solution (add noresume to linux startup line), but it did not work.

I finally did this:

login to maintenance terminal
apt clean
apt autoclean
apt autoremove
apt update
apt upgrade
shutdown now

After this, I powered-up the machine and it worked and I was able to continue upgrading to 19.04.

sudojose
  • 1