Volume group "ubuntu-vg" not found . . . Cannot process volume group ubuntu-vg
Recently I definitely left Windows 10 and now, I'm trying my first steps in Linux
This is my very first issue, wich came a few days ago.
. . . Starting PC and after decrypting SSD system drive
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
WARNING: Failed to connect to lvmetad. Falling back to device scanning
Reading all physical volumes. This may take a while ...
Found volume group "ubuntu-vg" using metadata type lvm2
WARNING: Failed to connect to lvmetad. Falling back to device scanning
2 logical volume(s) in volume group "ubuntu-vg" now active
I have no more info besides what was previously described. Normal PC operation, with no config changes.
- Ubuntu 18.04.3
- CPU Ryzen 5 3600
- RAM 2x8 GB G.Skill Flarex 3200 MHz CL16
- MB MSI MPG X570
- SSD NVMe M.2 Samsung 970 EVO Plus 500 GB
- GPU Nvidia GTX 1050 Ti
Solution 1:
FYI: This answer comes from my first-hand experience with Debian and Ubuntu encrypted systems (mostly Debian Unstable and testing Lubuntu 19.04/19.10 during devel cycles), but this is normal if the system is encrypted and requires an on-boot password.
While I do not know the exact reason this happens, from what I can tell when you have an encrypted partition, it can't read the partition with lvmetad and such while its encrypted. Once it's decrypted, it's able to use and recognize the volume group. Why this is the case I do not know, but I'm fairly sure we can consider this behavior you're observing "Normal Behavior" as I have reproduced this on Ubuntu 18.04, 19.04, 19.10, and Debian Unstable.
Since my 2019 post, I have confirmed this is Standard Behavior for any full disk encryption configuration.
You probably should have installed using Encrypted home directory and not full disk encryption - full disk encryption will prevent boot until you put in the disk encryption passphrase. No way around it, as it's doing what it's designed to do - prevent unauthorized access to the disk.