Problem with volume group not loading in

[james gould]

Trying to mount a volume group that would not
come up - mount -a on HPUX 11.0.

Volume would not mount. Disk drives look ok
and ioscan can see them that comprise the
volume group. Was told to perform the following
below.

a. Boot in single user mode with quorum override:

hpux -is -lq (;2)/hp-ux

b. Move the out-of-date lvmtab file:

mv /etc/lvmtab /etc/lvmtab.saved

c. Use vgscan to build a new one:

vgscan -v

Ran the command and still had problems. Also
noticed that it stated to do run vgimport of
the two drives. Ran the command and it stated
it was not a block device when using rdsk and
dsk in the command for vgimport.

Anything else to check or run??

Thanks

[Patrick Wallek]

I'm somewhat confused as to youru problem. I'll try to give it a shot though.

Is the volume group with the LVs you are trying to mount active? Does it get activated by default when the machine boots up?

What happens if you do:

# vgchange -a y /dev/vg??

for the suspect VG?

[Rita C Workman]

If your doing a mount -a...than I might ask:
Is this volume group mentioned in your /etc/fstab?

or

Are you running MC/SG? and is this volume group supposed to be part of that mount control?

Just a couple thoughts,
Rita

[Sanjay_6]

Hi James,

Try "vgchange -a y /dev/vg_name" for the volume groups you are trying to mount. Do "vgchange -a e /dev/vg_name" if you are using a SG volume group.

Hope this helps.

Regds

[Sridhar Bhaskarla]

Hi James,

Did you check your /etc/lvmrc file?. See if it has these volume groups configured as not to be activated during the bootup time. Some users edit this file on the systems with MC/Service Guard.

You can also try vgchange -a y volume_group to see if it is getting activated.

-Sri

[james gould]

Yes the volume group should mount on boot
but does not. Get and error with vgchange

- no physical volumes for the volume group
- also gives a cross link error

Yes we are running Service Guard but it is not
used in Service Guard

[james gould]

Correction - We are running 10.20 on server
with Service Guard. Output of vgchange -a
e volume group:

vgchange:Warning Couldnt attach to the volume
group physical volume "/dev/dks/c5t3d1"
Cross link device link

same thing happens for the other drive

[Christopher McCray_1]

Did you by chance just have a disk replaced? I have had this happen before where the hardware engineer(third party, not hp) has replaced a disk, but it was the wrong one, resulting in the cross-link error. have you tried to run vgcfgrestore on vg in question?

Hope this helps.

Chris

[Rita C Workman]

Just a thought,

Stop your package.
1.Make sure you have edited your package ~.run file (or whatever you call the Package Control Script file) properly and added the new volume group and fs information correctly.
2. Now release control of vg from lvm and give it to your cluster..
vgchange -a n /dev/vgname
vgchange -c y /dev/vgname
3. Now restart your package and see if everything mounts ok now..

Like I said just a thought,
Rita

[james gould]

System was at single user mode when vgchange
run. Also the disk drives are fine ioscan
can see them and the autoraid can see them.

[Sanjay_6]

Hi James,

try,

For non-SG volumes,
vgchange -a y -q n /dev/vg_name

for SG volumes,
vgchange -a e -q n /dev/vg_name

Hope this helps.

regds

[Sanjay_6]

Hi James,

If it is the root disk, simply use,

vgchange -q n /dev/vg00

Then boot into multiuser mode,

init 2
or
init 3


Hope this helps.

regds