Contents
Why are my logical volumes inactive at boot time?
I get volume group not found error after selecting grub (2) option. Inspection from busy box reveals the volumes are not registered with device mapper and that they are inactive. I wasn’t able to mount them after activating, I got file not found error (mount /dev/mapper/all-root /mnt). Any ideas how to proceed or make them active at the boot time?
Why does my LVM volume won’t Mount at boot time?
Why my encrypted LVM volume (LUKS device) won’t mount at boot time? Everything is setup but mounting the encrypted volume fails at boot-time with the error: fsck.ext4: No such file or directory while trying to open /dev/mapper/safe_vault Possibly non-existent device? What I’ve done…
Why is my LV / var inactive at boot time?
Entering with root password and running the commands lvm vgchange -ay and systemctl default I was able to activate my /var LV and boot the system. I haven’t figured out what causes this issue, but my workaround was to include the LV /var in /etc/default/grub as you see below:
Why are logical volumes not activated in ash shell?
The fact that logical volumes had to be activated manually in ash shell after failed boot and possible solution to this problem is covered in my reply below. So I managed to solve this eventually.
How to check Linux Logical volumes at boot time?
$ sudo vgscan [sudo] password for username: Reading all physical volumes. This may take a while… Found volume group “vg02” using metadata type lvm2 Found volume group “vg00” using metadata type lvm2 $ sudo vgchange -ay /dev/vg02 7 logical volume (s) in volume group “vg00” now active
What happens when a volume DISK is lost in LVM?
If the meta data is gone, or severely damaged, then LVM will consider that disk as an “unknown device.” If the volume group contains only one disk, then the volume group and it’s logical volumes will simply be gone. In this case the symptom is the same as if the disk was accidentally removed, with the exception of the device name.
Is there a problem with detecting logical volumes?
There is a problem (bug) with detecting logical volumes, which is some sort of race condition (maybe in my case regarding the fact that this happens inside KVM). This is covered in the following discussion. In my particular case (Debian Squeeze ) the solution is as follows: