cannot start /stand/vpmon from a specifically virtual partition

[Jdamian]

Hi

My SuperDome partition have 4 disks: 2 ones for a vpartition (vpar1) and 2 for a second vpartition (vpar2).

The vpars run fine but I cannot run /stand/vpmon from the disks of the second vpartitions (vpar2). The error message is:

ISL> hpux /stand/vpmon

Boot
:
disk(6/0/8/1/0/4/1.10.0.0.0.0.0;0)/stand/vpmon
disk(6/0/8/1/0/4/1.10.0.0.0.0.0;0)/stand/vpmon: cannot open, or not executable
Exec failed: No such file or directory

But that is not true because /stand/vpmon exist in the 4 disks and are identical.

Moreover, if I boot using the /stand/vmunix from any boot disk of vpar2, it boots fine.

Any idea?


Thanx in advance

[Vihang.]

Hi Oscar,

Can you go to the HPUX prompt & do an ls from there & check whether the /stand/vpmon exists in that disk. Also, check the permissions of the /stand/vpmon.


Regards,
Vihang.

[Jdamian]

Hi

vpar2:/># ll /stand/vpmon
-r-xr-xr-x 1 bin bin 4036672 Oct 5 2007 /stand/vpmon
vpar2:/># cksum /stand/vpmon
4022538587 4036672 /stand/vpmon
vpar2:/># lvlnboot -v vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c7t10d0 (6/0/9/1/0/4/1.10.0) -- Boot Disk
/dev/dsk/c5t10d0 (6/0/8/1/0/4/1.10.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c7t10d0
/dev/dsk/c5t10d0
Root: lvol3 on: /dev/dsk/c7t10d0
/dev/dsk/c5t10d0
Swap: lvol2 on: /dev/dsk/c7t10d0
/dev/dsk/c5t10d0
Dump: lvol2 on: /dev/dsk/c7t10d0, 0




vpar1://># ll /stand/vpmon
-r-xr-xr-x 1 bin bin 4036672 Oct 5 2007 /stand/vpmon
vpar1://># cksum /stand/vpmon
4022538587 4036672 /stand/vpmon
vpar1://># lvlnboot -v vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t10d0 (6/0/1/1/0/4/0.10.0) -- Boot Disk
/dev/dsk/c2t10d0 (6/0/2/1/0/4/0.10.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t10d0
/dev/dsk/c2t10d0
Root: lvol3 on: /dev/dsk/c0t10d0
/dev/dsk/c2t10d0
Swap: lvol2 on: /dev/dsk/c0t10d0
/dev/dsk/c2t10d0
Dump: lvol2 on: /dev/dsk/c0t10d0, 0

[Nick W]

Oscar,

Check that the filename /stand/vpmon does not contain any spurious (non-printing) characters...

Regards,
Nick 'dubya'

[Vihang.]

Nick is right. Sometimes we use the backspace if we do a typing mistake while typing the hpux /stand/vpmon. Try typing it carefully without using backspace & check the results.

[Jdamian]

Sorry guys but

I maybe mistyped or entered bad chars in one attempt but I don't think so for all the 8 or 10 attempts...

Moreover, /stand/vpmon cannot boot from disk (6/0/8/1/0/4/1.10.0.0.0.0.0;0) nor from (6/0/9/1/0/4/1.10.0.0.0.0.0;0) (= mirror boot disk)

[Nick W]

Oscar,

For now, assume that /stand/vpmon is good...
- maybe some strange interaction with your SAN (perhaps vpmon has very short timeout...?)

Presumably you are able to successfully load the vpmon from the boot disks of vpar1 - try to access the vpar monitor log buffer (run either MON>log or #"vparextract -l") and see if that gives any clues.

Check also /dev/vpmon and /stand/vpdb (are they identical on both vpars?)

You could also try running the vpars-collect.sh script and see if that provides any further clues (not sure if this is part of vpar sw or may need to request it from HP...)

Failing that, I suggest you log a case with HP support who may be able to provide you with some addititional debug tools (eg instrumented vpmon with debug) to help you.

It is advisable to run with recent versions of Vpar software as this is how 'patches' are delivered(ie no patches for vpar product)

Hope this helps,

Regards,
Nick