FREE ADVICE: HP-UX 11.31 How to change minor number for vg00

[VK2COT]

Hello,

Several people asked this question in the past
and earlier today, one of my valuable students
and myself tried the procedure to change minor
numbers for vg00.

Here is the procedure in full. She tested it on
vg00 running VG version 1.0, while I confirmed
the success with vg00 running VG version 2.2.

Here are the details of my procedure (very
similar to hers):

a) Check current LVM setup:

# lvmadm -l
--- Version 2.2 volume groups ---
VG Name /dev/vg00
PV Name /dev/disk/disk6_p2

# setboot -v

Primary bootpath : 0/1/1/1.0x2.0x0 (/dev/rdisk/disk6)
HA Alternate bootpath :
Alternate bootpath : 0/1/1/0.0x1.0x0 (/dev/rdisk/disk4)

Autoboot is ON (enabled)
TEST CURRENT DEFAULT
---- ------- -------
all on on
SELFTESTS on on
early_cpu on on
late_cpu on on
FASTBOOT on on
Platform on on
Full_memory on on
Memory_init on on
IO_HW on on
Chipset on on

# lvlnboot -v

Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk6_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk6_p2
Root: lvol3 on: /dev/disk/disk6_p2
Swap: lvol2 on: /dev/disk/disk6_p2
Dump: lvol2 on: /dev/disk/disk6_p2, 0

b) Check the current DSFs:

# ll /dev/vg00
total 0
crw-r----- 1 root sys 128 0x000000 Mar 31 2010 group
brw-r----- 1 root sys 128 0x000001 Mar 31 2010 lvol1
brw-r----- 1 root sys 128 0x00000a Mar 31 2010 lvol10
brw-r----- 1 root sys 128 0x000002 Mar 31 2010 lvol2
...

c) Reboot into LVM maintenance mode:

HPUX> boot vmunix -lm

d) Run LVM commands and set new minor number
that is not in use currently:

# vgexport -s -m /vg00.map /dev/vg00

vgexport: Volume group "/dev/vg00" has been
successfully removed.

# mkdir /dev/vg00

# mknod vg00/group c 128 0x010000

e) Run one of these two commands (whichever is
easier for admins):

# vgimport -N -s -m /vg00.map vg00

vgimport: Volume group "/dev/vg00" has been
successfully created.
Warning: A backup of this volume group may not
exist on this machine.
Please remember to take a backup using the
vgcfgbackup command after activating the volume
group.

or

# vgimport -m /vg00.map vg00 /dev/disk/disk6_p2

vgimport: Volume group "/dev/vg00" has been successfully created.
Warning: A backup of this volume group may not
exist on this machine.
Please remember to take a backup using the
vgcfgbackup command after activating the volume
group.

f) Re-activate the volume group:

# vgchange -a y vg00

Activated volume group.
Volume group "vg00" has been successfully
changed.

g) Remove old LVM structures:

# lvlnboot -R vg00

Warning: Logical Volume number "-2147483645"
found on physical volume not found in "vg00".
Volume Group configuration for /dev/vg00 has
been saved in /etc/lvmconf/vg00.conf

# lvrmboot -r vg00

Volume Group configuration for /dev/vg00 has
been saved in /etc/lvmconf/vg00.conf

h) Set up the new LVM structures:

# lvlnboot -v

lvlnboot: The Boot Data Area is empty.

# lvlnboot -b /dev/vg00/lvol1

Volume Group configuration for /dev/vg00 has
been saved in /etc/lvmconf/vg00.conf

# lvlnboot -r /dev/vg00/lvol3

Volume Group configuration for /dev/vg00 has
been saved in /etc/lvmconf/vg00.conf

# lvlnboot -s /dev/vg00/lvol2

Volume Group configuration for /dev/vg00 has
been saved in /etc/lvmconf/vg00.conf

# lvlnboot -d /dev/vg00/lvol2

Volume Group configuration for /dev/vg00 has
been saved in /etc/lvmconf/vg00.conf

# lvlnboot -v

Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk6_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk6_p2
Root: lvol3 on: /dev/disk/disk6_p2
Swap: lvol2 on: /dev/disk/disk6_p2
Dump: lvol2 on: /dev/disk/disk6_p2, 0

# lvlnboot -R vg00

Volume Group configuration for /dev/vg00 has
been saved in /etc/lvmconf/vg00.conf

A final reboot and it all worked.

Cheers,

VK2COT

[VK2COT]

It was simply a notification for the Forum
members.

No replies were expected.