vpar Boot issue

[Azaru]

Hi everyone. We are unis SD32B itanium superdome server. In one vpar while booting we are facing issue as follows


Logical volume 64, 0x3 configured as ROOT
LVM : Failure in attaching PV (1/0/13/1/1.0.0) to the root volume group.
Cross device link. The disk is not a LVM disk.
LVM: VG 64 0x000000: Quorum check failed!
LVM : Activation of root volume group failed
Quorum not present, or some physical volume(s) are missing


-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Could not configure root VG
If new kernel, HPUX> boot /stand/vmunix -lm ; pvck -y /dev/rdsk/....
| |
-----------------------------------------------------


System Panic:

panic: LVM: Configuration failure
Stack Trace:
IP Function Name
0xe000000001e51680 lv_boothalt+0x110
0xe000000001e510f0 lv_bootconf+0x3c0
0xe000000001e58b80 lvmconf_body+0x2e0
0xe000000001309170 lvmconf+0x30
0xe000000001287750 im_lvmconf+0x70
0xe0000000016ee4d0 DoCalllist+0x3a0
End of Stack Trace

linkstamp: Thu Apr 17 08:19:35 IST 2008
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $

sync'ing disks (0 buffers to flush): (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty

*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

ERROR: Your system crashed before I/O and dump configuration was complete.
This system does not support a crash dump under these circumstances.
Contact your HP support representative for assistance.



I hope ur answers will help me a lot.

[Mridul Shrivastava · Accepted solution]

Try booting vpar in maintenance mode using vparboot or vparload using -o "-lm" and try repairing the LVM structure.

Else try booting after disabling quorum using -o "-lq".

[Azaru]

Will this affect other vpars in the npar?

azaru

[Rasheed Tamton]

Hi,

If you use the correct options - no.

to boot a vpar in Single user mode.
- from Vpar Monitor prompt,

Mention the correct vpar name after -p option
# vparload -p vPar3 -o "-is"
- from shell prompt of other Vpars,

# vparboot -p vPar3 -o "-is"
or
# vparboot -p vPar3 -o "-lq"
vparstatus will show the boot flags


Boot the virtual partition called Oslo:

vparboot -p Oslo Boot the virtual partition Bergen specifying an alternate kernel:

vparboot -p Bergen -b /stand/vmunix_debug

Rgds.

[Azaru]

Now i have tried the command

vparload -p misapp3 -o "-lm"

Now the error is

Load of 1/0/1/1/1.0.0.0.0.0 failed.


azaru.

[Mridul Shrivastava]

what about the other options?? Have you tries quorum disable or single user mode ??

Try booting from the alternate disk if you had mirroring in place.

[Azaru]

I tried bit nothing has been found. Any other way to boot the vpar?

[Rasheed Tamton]

>LVM : Failure in attaching PV (1/0/13/1/1.0.0) to the root volume group.
Cross device link. The disk is not a LVM disk.
LVM: VG 64 0x000000: Quorum check failed!
LVM : Activation of root volume group failed
Quorum not present, or some physical volume(s) are missing

>boot /stand/vmunix -lm ; pvck -y /dev/rdsk/

-The system already tried pvck command and it examines and repairs LVM data structures on a raw disk (pv-path) in a volume

-Did you check the disks.

vparboot -p misapp3 -o "-lq"
vparboot -p misapp3


To set the primary boot path:

If you have a mirror disk, try setting the boot path and boot again

misapp1111111# vparcreate -p misapp3 -a io:0.8.0.0.5.0:BOOT

[Rasheed Tamton]

Try from the other vpar the below cmd:

misapp1111111# vparstatus -p misapp3 -v

[Azaru]

Primary boot path not found.
Internal error in setting up vPars variables.
"misapp3" load failed.

Now the error is coming like this.