topic Re: Software Failure (A500) strange behaviour in Operating System - HP-UX

Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 16:40:40 GMT

System boots normally via

ISL>hpux -is

# init 3

but panics via

ISL> hpux

Any ideas?

Later,
Bill

Re: Software Failure (A500) strange behaviour

Helen French — Wed, 20 Feb 2002 16:43:24 GMT

Hi Bill,

Do you have the error message ? Can you post it ?

HTH,
Shiju

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 16:45:15 GMT

in fact it boots only with hpux -lm, NOT is

System Console is on the Built-In Serial Interface
pci_desc_bus foire 1
WSIO octtldrv initialised.
Logical volume 64, 0x3 configured as ROOT
LVM : Failure in attaching PV (0/0/1/1.15.0) to the root volume group.
Cross device link. The disk is not a LVM disk.
LVM : Activation of root volume group failed
Either no physical volumes are attached or no valid VGDAs were found on the phys
ical volumes.
Quorum not present, or some physical volume(s) are missing

-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Could not configure root VG

| |
-----------------------------------------------------

linkstamp: Tue Jan 29 15:15:41 MET 2002
_release_version: @(#)B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov 5 22:38:19 PS
T 1997
__kern_ci_revision: $Header: kern_sequence.c,v 1.6.106.512 97/11/05 18:01:46 mso
sa Exp $

panic: LVM: Configuration failure

Later,
Bill

Re: Software Failure (A500) strange behaviour

Patrick Wallek — Wed, 20 Feb 2002 16:49:20 GMT

Sounds like you've got a bad boot disk, or disk that is in vg00, at 0/0/1/1.15.0.

Is 0/0/1/1.15.0 your primary or secondary boot disk? If your boot disks are mirrored you probably should be able to get the system boot multi-user by doing a 'hpux -lq' to boot without quorum. From there you can troubleshoot your disk problem.

Re: Software Failure (A500) strange behaviour

Helen French — Wed, 20 Feb 2002 16:53:18 GMT

Hi Bill,

Do you have a root mirror ?

Check this out for some possible solutions:

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=71011f6c171d0f7a57/screen=ckiDisplayDocument?docId=200000058670556

HTH,
Shiju

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 16:55:31 GMT

kibo:root> vgcfgrestore -l -n vg00
Volume Group Configuration information in "/etc/lvmconf/vg00.conf"
VG Name /dev/vg00
---- Physical volumes : 1 ----
/dev/rdsk/c1t15d0 (Bootable)

kibo:root> vgscan -p
vgscan: The physical volume "/dev/dsk/c1t15d0" is already recorded in the "/etc/lvmtab" file.

kibo:root> strings /etc/lvmtab
/dev/vg00
/dev/dsk/c1t15d0

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 16:56:17 GMT

not mirrored..

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 16:57:28 GMT

--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 2500
VGDA 2
PE Size (Mbytes) 4
Total PE 2169
Alloc PE 1872
Free PE 297
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 84
Current LE 21
Allocated PE 21
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 140
Allocated PE 35
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 500
Current LE 125
Allocated PE 125
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 40
Current LE 10
Allocated PE 10
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 500
Allocated PE 500
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 500
Allocated PE 500
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 1700
Current LE 425
Allocated PE 425
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 40
Current LE 10
Allocated PE 10
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 500
Allocated PE 500
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 500
Allocated PE 500
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 1700
Current LE 425
Allocated PE 425
Used PV 1

--- Physical volumes ---
PV Name /dev/dsk/c1t15d0
PV Status available
Total PE 2169
Free PE 297
Autoswitch On

..

(cut and paste so possibly not perfectly cut & paste,,, but just to prove no mirroring)

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 16:58:34 GMT

--- Physical volumes ---
PV Name /dev/dsk/c1t15d0
VG Name /dev/vg00
PV Status available
Allocatable yes
VGDA 2
Cur LV 8
PE Size (Mbytes) 4
Total PE 2169
Free PE 297
Allocated PE 1872
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol1 21 21
/dev/vg00/lvol2 256 256
/dev/vg00/lvol3 35 35
/dev/vg00/lvol4 125 125
/dev/vg00/lvol5 10 10
/dev/vg00/lvol6 500 500
/dev/vg00/lvol7 500 500
/dev/vg00/lvol8 425 425

--- Physical extents ---
PE Status LV LE
0000 current /dev/vg00/lvol1 0000
0001 current /dev/vg00/lvol1 0001
0002 current /dev/vg00/lvol1 0002
0003 current /dev/vg00/lvol1 0003
0004 current /dev/vg00/lvol1 0004
0005 current /dev/vg00/lvol1 0005
0006 current /dev/vg00/lvol1 0006
0007 current /dev/vg00/lvol1 0007
0008 current /dev/vg00/lvol1 0008
0009 current /dev/vg00/lvol1 0009
..
..
..
..
2163 free 0000
2164 free 0000
2165 free 0000
2166 free 0000
2167 free 0000
2168 free 0000

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 16:59:12 GMT

kibo:root> lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t15d0 (0/0/1/1.15.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t15d0
Root: lvol3 on: /dev/dsk/c1t15d0
Swap: lvol2 on: /dev/dsk/c1t15d0
Dump: lvol2 on: /dev/dsk/c1t15d0, 0

Re: Software Failure (A500) strange behaviour

Volker Borowski — Wed, 20 Feb 2002 17:00:24 GMT

Hi Bill,

suspect at least one corrupt lvol.

When your boot -is OK, what happens, if you mount the remaining lvols manually one by one afterwards (may be a manual fsck before the mount will save you another panic ?)

Good luck
Volker

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 17:06:53 GMT

kibo:root> mount -p
/dev/root / vxfs log 0 0
/dev/vg00/lvol8 /var vxfs delaylog,nodatainlog 0 0
/dev/vg00/lvol7 /usr vxfs delaylog,nodatainlog 0 0
/dev/vg00/lvol4 /tmp vxfs delaylog,nodatainlog 0 0
/dev/vg00/lvol1 /stand hfs defaults 0 0
/dev/vg00/lvol6 /opt vxfs delaylog,nodatainlog 0 0
/dev/vg00/lvol5 /home vxfs delaylog,nodatainlog 0 0

after hpux -lm
init 5
the mount looks like above:

etc/fstab=
kibo:root> cat /etc/fstab
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2

Bill

Re: Software Failure (A500) strange behaviour

Helen French — Wed, 20 Feb 2002 17:07:28 GMT

Hi Bill,

Try 'vgcfgrestore' without '-l' option. -l option will only list the config file. Try restoring the VG info.

HTH,
Shiju

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 17:09:51 GMT

I'll tell you tomorrow if it works, it's rebooting and I'm tired!

Later,
Bill

Re: Software Failure (A500) strange behaviour

Bill McNAMARA_1 — Wed, 20 Feb 2002 17:16:23 GMT

http://europe-support.external.hp.com/cki/bin/doc.pl/sid=71011f6c171d0f7a57/screen=ckiDisplayDocument?docId=200000058670556

Thanks Shawn.. here's the link for those in europe..

Later,
Bill

Re: Software Failure (A500) strange behaviour

Helen French — Wed, 20 Feb 2002 17:52:44 GMT

Hi Bill,

Which option worked for u ? vgcfgrestore ? or anything else from the link ?

btw, me Shiju not Shawn =))

Shiju