LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   volume group not found (https://www.linuxquestions.org/questions/linux-general-1/volume-group-not-found-4175736406/)

MichielvM 04-25-2024 06:07 AM

volume group not found
 
Hi all,

I have an Azure VM running RHEL 8.9

I want to extend de /log volume. I have done this many times before without too much hassle, until now.

lvextend output:
#lvextend -v -r -L 300G /dev/mapper/logvg-loglv
VG name on command line not found in list of VGs: logvg
Volume group "logvg" not found
Cannot process volume group logvg
lsblk -f output:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 256G 0 disk
└─logvg-loglv 253:6 0 256G 0 lvm /log
sdb 8:16 0 512G 0 disk
└─repovg-repolv 253:5 0 512G 0 lvm /repo
sdc 8:32 0 256G 0 disk
├─sdc1 8:33 0 500M 0 part /boot
├─sdc2 8:34 0 63G 0 part
│ ├─rootvg-tmplv 253:0 0 2G 0 lvm /tmp
│ ├─rootvg-usrlv 253:1 0 10G 0 lvm /usr
│ ├─rootvg-homelv 253:2 0 1G 0 lvm /home
│ ├─rootvg-varlv 253:3 0 32G 0 lvm /var
│ └─rootvg-rootlv 253:4 0 2G 0 lvm /
├─sdc14 8:46 0 4M 0 part
└─sdc15 8:47 0 495M 0 part /boot/efi
sdd 8:48 0 8G 0 disk
└─sdd1 8:49 0 8G 0 part /mnt
vgs output:
# vgs
VG #PV #LV #SN Attr VSize VFree
repovg 1 1 0 wz--n- <512.00g 0
rootvg 1 5 0 wz--n- <63.02g <16.02g
vgs output shows no logvg.
And it's clearly right ther.
I'm at a loss.

MadeInGermany 04-27-2024 04:05 AM

Looks like a corruption in a /etc/lvm/ file e.g. /etc/lvm/lvm.conf

Try to restore the lost vg from the last backup:
Code:

vgcfgrestore logvg
See options in the man page

GazL 05-10-2024 06:42 AM

Looking at the date of the post you've probably already solved this by now and I'm a little late to the party, but for anyone passing by, the problem might be how the vg/lv are specified. You don't normally specify the /dev/mapper/* paths on lvm commands:

#lvextend -v -r -L 300G logvg/loglv


Not sure why 'vgs' isn't showing the VG as it as it's clearly there on the lsblk output. Perhaps a vgscan --mknodes or a vgchange -ay logvg will bring it back to life.


All times are GMT -5. The time now is 09:22 AM.