Critical: Lost Volume Group

praveen.. — Fri, 26 Jan 2007 01:52:58 GMT

Hi,
I have restart my server and then i am not able find vg01 & vg03.

I have total four VGs (vg00,vg01,vg02 & vg03)
I imported vg02 from another server after restart.

there is no file named "/dev/vg01" and "/dev/vg03".

but...
# vgscan
Reading all physical volumes. This may take a while...
Found volume group "vg01" using metadata type lvm2
Found volume group "vg03" using metadata type lvm2
Found volume group "vg00" using metadata type lvm2
Found volume group "vg02" using metadata type lvm2
#

Please suggest how can i get vg01 & vg03 back
It is very critical, Please suggest

Thanks

Re: Critical: Lost Volume Group

praveen.. — Fri, 26 Jan 2007 02:18:53 GMT

# vgdisplay -v /dev/vg01
Using volume group(s) on command line
Finding volume group "vg01"
--- Volume group ---
VG Name vg01
System ID
Format lvm2
Metadata Areas 3
Metadata Sequence No 9
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 6
Open LV 0
Max PV 0
Cur PV 3
Act PV 3
VG Size 520.00 GB
PE Size 4.00 MB
Total PE 133119
Alloc PE / Size 130560 / 510.00 GB
Free PE / Size 2559 / 10.00 GB
VG UUID 4rqO5y-RUdv-h9fU-cuLc-snjA-kN3m-Yb5xIF

--- Logical volume ---
LV Name /dev/vg01/db2dms
VG Name vg01
LV UUID G9rlJz-t9Od-8r55-EK4r-j5Q1-1tqZ-fqsf25
LV Write Access read/write
LV Status NOT available
LV Size 400.00 GB
Current LE 102400
Segments 2
Allocation inherit
Read ahead sectors 0

--- Logical volume ---
LV Name /dev/vg01/dmsextract
VG Name vg01
LV UUID nUCMdN-NRW5-zlvk-GjpL-1drf-Y4n8-aK5KBF
LV Write Access read/write
LV Status NOT available
LV Size 4.00 GB
Current LE 1024
Segments 1
Allocation inherit
Read ahead sectors 0

--- Logical volume ---
LV Name /dev/vg01/dmsload
VG Name vg01
LV UUID daZnvh-dCmb-RWFb-Z7cU-xdC2-o4hH-A8F6z1
LV Write Access read/write
LV Status NOT available
LV Size 4.00 GB
Current LE 1024
Segments 1
Allocation inherit
Read ahead sectors 0

--- Logical volume ---
LV Name /dev/vg01/dmslog
VG Name vg01
LV UUID uSRhi2-um3X-FGnO-VclX-d0HV-qJBf-8VFp83
LV Write Access read/write
LV Status NOT available
LV Size 1.00 GB
Current LE 256
Segments 1
Allocation inherit
Read ahead sectors 0

--- Logical volume ---
LV Name /dev/vg01/dmscode
VG Name vg01
LV UUID 4J53SB-oBFX-gDn3-49GU-xVKw-wR7H-YTv3X3
LV Write Access read/write
LV Status NOT available
LV Size 1.00 GB
Current LE 256
Segments 1
Allocation inherit
Read ahead sectors 0

--- Logical volume ---
LV Name /dev/vg01/home_dms
VG Name vg01
LV UUID GaXYNq-AxCu-2J30-Ooh2-YLQ5-G8UL-JIXMZq
LV Write Access read/write
LV Status NOT available
LV Size 100.00 GB
Current LE 25600
Segments 1
Allocation inherit
Read ahead sectors 0

--- Physical volumes ---
PV Name /dev/sdc1
PV UUID VOHZ3E-jB9s-RDfo-tQ3S-bE3Q-3QwR-X9wwh2
PV Status allocatable
Total PE / Free PE 51200 / 0

PV Name /dev/sdd1
PV UUID q3BIJ5-1Yk4-zJsp-ZARl-5Udk-LiSH-fS4zJu
PV Status allocatable
Total PE / Free PE 51200 / 0

PV Name /dev/sde
PV UUID JiLGMW-XTVZ-WPc2-hIuT-e17z-ONhV-2rB4sy
PV Status allocatable
Total PE / Free PE 30719 / 2559

# vgdisplay -v /dev/vg03
Using volume group(s) on command line
Finding volume group "vg03"
--- Volume group ---
VG Name vg03
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 0
Max PV 0
Cur PV 2
Act PV 2
VG Size 239.93 GB
PE Size 4.00 MB
Total PE 61422
Alloc PE / Size 51200 / 200.00 GB
Free PE / Size 10222 / 39.93 GB
VG UUID LUdDcO-eFPc-wvuh-ri5r-e3My-O2kd-YWFzyI

--- Logical volume ---
LV Name /dev/vg03/db2dms
VG Name vg03
LV UUID wjwnuh-Mh7j-XRBY-I36J-5grD-ANqk-4oDD04
LV Write Access read/write
LV Status NOT available
LV Size 200.00 GB
Current LE 51200
Segments 2
Allocation inherit
Read ahead sectors 0

--- Physical volumes ---
PV Name /dev/sdb1
PV UUID xMfzZE-qt9X-y62N-aXbP-hfls-So57-EC2ZPa
PV Status allocatable
Total PE / Free PE 30711 / 0

PV Name /dev/sdf1
PV UUID 4VMBhE-Qv81-dKdU-VFzy-u6v5-6VOf-3MJbnB
PV Status allocatable
Total PE / Free PE 30711 / 10222

Re: Critical: Lost Volume Group

Matti_Kurkela — Fri, 26 Jan 2007 02:53:41 GMT

The command you're looking for is

vgscan --mknodes

It will recreate the missing device files automatically.

Re: Critical: Lost Volume Group

praveen.. — Fri, 26 Jan 2007 03:02:40 GMT

# vgscan --mknodes
Reading all physical volumes. This may take a while...
Found volume group "vg01" using metadata type lvm2
Found volume group "vg03" using metadata type lvm2
Found volume group "vg00" using metadata type lvm2
Found volume group "vg02" using metadata type lvm2
#

# cd /dev/vg01
-bash: cd: /dev/vg01: No such file or directory
# cd /dev/vg03
-bash: cd: /dev/vg03: No such file or directory
#

this command did not work

I dont want to lose the data...
and the LV status is NOT available

Please suggets

Re: Critical: Lost Volume Group

praveen.. — Fri, 26 Jan 2007 03:52:18 GMT

I got my VGs using..
# vgchange -ay /dev/vg01
# vgchange -ay /dev/vg03

Thanks everybody

topic Critical: Lost Volume Group in Operating System - Linux

Critical: Lost Volume Group

Re: Critical: Lost Volume Group

Re: Critical: Lost Volume Group

Re: Critical: Lost Volume Group

Re: Critical: Lost Volume Group