topic Re: kernel info inconsistent with /etc/lvmtab in Operating System - HP-UX

kernel info inconsistent with /etc/lvmtab

shahbaz_3 — Tue, 07 Mar 2006 04:01:49 GMT

I got my one internal disk faulty on rx4640 having root volume group vg00 my os is 11:23.

i reduce logical volumes and replace disks as mentioned in doc " when good disks goes bad"
every thing work fine except that in my system Act PV or not same as Cur PV.
I have tried creating new lvmtab in normal boot and also by booting in maintanance mode and follow the procedure of recreating vg00.
nothing helps
when i tried to create new lvmtab it couldn't get defination of vg00 at all.

remember that the disk which was failed was the first disk of lvm mirror.
please help it is urgent

Re: kernel info inconsistent with /etc/lvmtab

Senthil Kumar .A_1 — Tue, 07 Mar 2006 05:17:54 GMT

Hi Shahbaz,

First to fix the issue related to "ACT PV" mismatch with "CUR PV" , run the following command..

vgreduce -f /dev/vg00

verify whether it has rectified or not.

vgdisplay /dev/vg00

Secondly, the issue of VG00 not appearing in /etc/lvmtab, after fixing the first issue, now move the /etc/lvmtab file to some place else.Now recreate the lvmtab file by running vgscan.

mv /etc/lvmtab /tmp
vgscan -a -v

Verify the lvmtab file,

strings /etc/lvmtab

Regards,
Senthil Kumar .A

Re: kernel info inconsistent with /etc/lvmtab

shahbaz_3 — Tue, 07 Mar 2006 05:38:03 GMT

vgreduce -f /dev/vg00
didn't rectify the problem

i have always use vgscan -v
do you think using vgscan -v -a will help ?

Re: kernel info inconsistent with /etc/lvmtab

Senthil Kumar .A_1 — Tue, 07 Mar 2006 07:00:41 GMT

Hi Shahbaz,

Any to be on safer side, copy the /etc/lvmtab file to safer side, before u run with "-a" option. When vgscan is run with this option, it will Scan all controller device paths for all disks.

In case it hasn't rectified, you can revert back the change by copying back your earlier copy of lvmtab file.

Regards,
Senthil Kumar .A

Re: kernel info inconsistent with /etc/lvmtab

Chauhan Amit — Wed, 08 Mar 2006 01:11:06 GMT

This procedure can be used when vgreduce fails to reduce a physical volume that can no longer be queried by the system. If executing the following procedure on the root volume group, usually vg00, you must
first boot into LVM maintenance mode (** For steps see below).

1. Get the /dev/vg_name/group minor number and physical volumes
belonging to the volume group.

Use: ll /dev/vg00/group to get 0x###### minor number.
vgdisplay -v /dev/vg_name to get physical volumes.

2. vgchange -a n /dev/vg_name
NOTE: Skip this step if booting maintanence mode for root volume
group.

3. vgexport -m /mapfile /dev/vg_name

4. mkdir /dev/vg_name

5. mknod /dev/vg_name/group c 64 0x0#0000
Re-use minor number obtained from step 1.

6. vgimport -m /mapfile /dev/vg_name pv_name [pv_name ...]

NOTE: Specify all the physical volumes obtained from step 1. Do not
include the physical volume that you are trying to remove or
that couldn't be queried.

** Steps to boot into maintenance mode and active. :
1. shutdown -hy now
2. interrupt boot sequence
3. boot from primary boot path and interact with ISL

-Amit

Re: kernel info inconsistent with /etc/lvmtab

gigiz — Wed, 08 Mar 2006 09:08:00 GMT

You can try to mv /etc/lvmtab /etc/lvmtab.backup
then
vgscan to recreate lvmtab ....

Re: kernel info inconsistent with /etc/lvmtab

shahbaz_3 — Wed, 08 Mar 2006 09:23:31 GMT

Thanks for all of your efforts.
I logged case with hp and the steps hp support person follows was these.
after checking status.
boot system in lvm maintanence mode
use vgcfgrestore -o /dev/vg00 -l /dev/dsk/c31d0s2 /dev/dsk/c2t0d0s2
and then reboot normal
system was seeing actpv and curpv same
and then we use vgsync.
Note: parameter of vgcfgrestore may be differrent i didn't exactly remember and doc is with customer at the moment. but this was the step done.