1833750 Members
2597 Online
110063 Solutions
New Discussion

LVM after Ignite

 
SOLVED
Go to solution
Jeremy Loukinas
Frequent Advisor

LVM after Ignite

I ignited a system today that over 22 VG's. During the ignite creation the vg confs said they were backed up, and the ignite process finished.

Now that I have reignited my machine my lvmtab is blank except for some info about vg00.

I tried running vgscan but I get the following..
The Volume Group /dev/vg01/group was not matched with any Physical Volumes.
The Volume Group /dev/vg02/group was not matched with any Physical Volumes.
The Volume Group /dev/vg03/group was not matched with any Physical Volumes.
The Volume Group /dev/vg04/group was not matched with any Physical Volumes.
The Volume Group /dev/vg05/group was not matched with any Physical Volumes.
The Volume Group /dev/vg06/group was not matched with any Physical Volumes.
The Volume Group /dev/vg07/group was not matched with any Physical Volumes.
The Volume Group /dev/vg08/group was not matched with any Physical Volumes.
The Volume Group /dev/vg09/group was not matched with any Physical Volumes.
The Volume Group /dev/vg10/group was not matched with any Physical Volumes.
The Volume Group /dev/vg11/group was not matched with any Physical Volumes.
The Volume Group /dev/vg12/group was not matched with any Physical Volumes.
The Volume Group /dev/vg13/group was not matched with any Physical Volumes.
The Volume Group /dev/vg14/group was not matched with any Physical Volumes.
The Volume Group /dev/vg15/group was not matched with any Physical Volumes.
The Volume Group /dev/vg16/group was not matched with any Physical Volumes.
The Volume Group /dev/vg17/group was not matched with any Physical Volumes.
The Volume Group /dev/vg18/group was not matched with any Physical Volumes.
The Volume Group /dev/vg19/group was not matched with any Physical Volumes.
The Volume Group /dev/vg20/group was not matched with any Physical Volumes.
The Volume Group /dev/vg21/group was not matched with any Physical Volumes.
The Volume Group /dev/vg22/group was not matched with any Physical Volumes.

Any advice?
6 REPLIES 6
John Poff
Honored Contributor

Re: LVM after Ignite

Hi,

Is the machine you ignited connected to the same disks that the source machine was? Your LVM is probably complaining because those volume groups that were described cannot see the physical volumes assigned to them. If you are connected to your disk storage, it is possible that your controller numbers have changed.

JP
James R. Ferguson
Acclaimed Contributor

Re: LVM after Ignite

Hi:

If you Ignited to the same hardware as that from which you created your Ignite recovery tape, I'd say that the disk device files changed -- not uncommon during a cold-install (which this is).

If you want to use 'vgscan' to deduce what devices belong to what volume groups, make a copy of the current '/etc/lvmtab'; remove it; and run 'vgscan -p -v -a'. Redirect the output to a file for examination and put the 'etc/lvmtab' back in place. Now 'vgimport' your various volume groups using the correct device files.

Regards!

...JRF...
Sridhar Bhaskarla
Honored Contributor
Solution

Re: LVM after Ignite

Hi,

There are couple of options.

One - Move /etc/lvmtab as /etc/lvmtab and run 'vgscan' and find out the disks corresponding to the VGS.

Two - Since you ignited the box from the old image, you will get the configuration files back in /etc/lvmconf with mapfiles. Look at the timestampes of vgxx.conf files. If they are reasonably new (or you are sure you didn't make any changes to the VGs after the dates indicated by the time stamps), you can get the PVs associated with the vgs by doing a 'strings vgxx.conf'. You will also find the map files.

#strings vg01.conf|grep dsk |sed 's/rdsk/dsk/g' > /tmp/vg01.disks
#mkdir /dev/vg01
#mknod /dev/vg01/group 0x010000
#vgimport -v -m /etc/lvmconf/vg01.map -f /tmp/vg01.disks vg01

If it is successful, then you can do a vgchange -a y and get the VG going.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Jeremy Loukinas
Frequent Advisor

Re: LVM after Ignite

Sridhar...


hp40:/dev # vgimport -v -m /etc/lvmconf/vg08.mapfile -f /tmp/vg08.disks
Usage: vgimport
[-p]
[-v]
[-s]
[-m MapFile]
VolumeGroupName PhysicalVolumePath...
or: vgimport [-p] [-v] [-m MapFile] -f InFile VolumeGroupName
More arguments required.
hp40:/dev #

Any suggestions..
Pete Randall
Outstanding Contributor

Re: LVM after Ignite

Jeremy,


You left out the vgname: last argument in Sri's command string (vg01).


Pete



Pete
Jerome Baron
Respected Contributor

Re: LVM after Ignite

Hi,

you forgot vg name.

Regards,
jerome