LVM Error and System dump after power failure

[inukoti]

Hi Profi's,
after the power failure system got booted and hanged at LVM and crashing with out coming up.
Log was placed at the below.
I tried recovery using the HPUX MEDIA /recovery inorder to repair the LVM but failed . Same as usual .

Thanks for your Help !!!



========================================================
Loading.: HP-UX Primary Boot: 0/1/1/0.0.0.2.0
Starting: HP-UX Primary Boot: 0/1/1/0.0.0.2.0

(C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.029

Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix
Seconds left till autoboot - 7
Type 'help' for help

HPUX> boot vmunixBK -lq -is
> System Memory = 32747 MB
loading section 0
...............................................................
(complete)
loading section 1
................ (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....Launching /stand/vmunixBK
SIZE: Text:31767K + Data:7931K + BSS:5363K = Total:45062K

Console is on a Serial Device
Booting kernel...


Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 32747 MB 32747 MB 32747 MB

Kernel : 32747 MB 32747 MB 32747 MB

User : 31002 MB 27019 MB 27124 MB

-------------------------------------------------------------------------

Loaded ACPI revision 2.0 tables.
krs_read_mfs: The config.krs file was not found.
krs_read_mfs: The config.krs.lkg file was not found.
kc_init: Error opening Modules sub-tree.
Could not initialize static modules list
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
NOTICE: USB device attached. Identification String:
Devices/Device/USB/Standard/hp/Multibay/0_a1
<2.1.3.10.1008.294.161>
NOTICE: USB device attached. Identification String:
Devices/MassStorage-SCSI/USB/BulkOnly/hp/Multibay/0_a1
<2.310.3.150.1008.294.161>
NOTICE: USB device attached. Identification String:
Devices/ScsiControllerAdaptor/USB/BulkOnly/hp/Multibay
<2.1000.3.150.1008.294>
Boot device's HP-UX HW path is: 0/1/1/0.0.0.1.0

System Console is on the Built-In Serial Interface
igelan0: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at
hardware path 0/1/2/0
igelan1: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at
hardware path 0/1/2/1
WCalling function e000000001187d00 for Shutdown State 8 type 0x2

Stored message buffer up to panic:
Found adjacent data tr. Growing size. 0x3302000 -> 0x7302000.
Pinned PDK malloc pool: base: 0xe000000100cfe000 size=117768K
Loaded ACPI revision 2.0 tables.
MMIO on this platform supports Write Coalescing.

MFS is defined: base= 0xe000000100cfe000 size= 16 KB
krs_read_mfs: The config.krs file was not found.
krs_read_mfs: The config.krs.lkg file was not found.
kc_init: Error opening Modules sub-tree.
Could not initialize static modules list


Unpinned PDK malloc pool: base: 0xe000000110000000 size=524288K
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
0 sba
0/0 lba
0/0/1/0 rmp3f01
0/0/1/1 rmp3f01
0/0/1/2 asio0
0/0/2/0 UsbOhci
0/0/2/1 UsbOhci
NOTICE: USB device attached. Identification String:
Devices/Device/USB/Standard/hp/Multibay/0_a1
<2.1.3.10.1008.294.161>
0/0/2/1.0 UsbMiniBus
NOTICE: USB device attached. Identification String:
Devices/MassStorage-SCSI/USB/BulkOnly/hp/Multibay/0_a1
<2.310.3.150.1008.294.161>
0/0/2/1.0.0 UsbBulkOnlyMS
NOTICE: USB device attached. Identification String:
Devices/ScsiControllerAdaptor/USB/BulkOnly/hp/Multibay
<2.1000.3.150.1008.294>
0/0/2/1.0.16 UsbScsiAdaptor
0/0/2/1.0.16.0 tgt
0/0/2/1.0.16.0.0 sdisk
0/0/2/1.0.16.7 tgt
0/0/2/1.0.16.7.0 sctl
0/0/2/2 UsbEhci
0/0/3/0 gvid_core
0/1 lba
sasd: Claimed HP PCI/PCI-X SAS MPT adapter at hardware path 0/1/1/0
0/1/1/0 sasd
0/1/2/0 igelan
0/1/2/1 igelan
0/2 lba
fcd: Claimed HP AB378-60101 4Gb Fibre Channel port at hardware
path 0/2/1/0 (FC Port 1 on HBA)
0/2/1/0 fcd
0/3 lba
0/4 lba
fcd: Claimed HP AB378-60101 4Gb Fibre Channel port at hardware
path 0/4/1/0 (FC Port 1 on HBA)
0/4/1/0 fcd
120 processor
121 processor
122 processor
123 processor
250 pdh
250/0 ipmi
250/1 asio0
250/2 acpi_node
0/2/1/0.3 fcd_fcp
0/2/1/0.3.8.0.0 fcd_vbus
0/2/1/0.3.8.255.0 fcd_vbus
0/2/1/0.3.10.0.0 fcd_vbus
0/2/1/0.3.10.255.0 fcd_vbus
0/2/1/0.3.8.0.0.0 tgt
0/2/1/0.3.8.255.0.0 tgt
0/2/1/0.3.8.0.0.0.0 sdisk
0/2/1/0.3.8.255.0.0.0 sctl
0/2/1/0.3.10.0.0.0 tgt
0/2/1/0.3.10.255.0.0 tgt
0/2/1/0.3.10.0.0.0.0 sdisk
0/2/1/0.3.10.255.0.0.0 sctl
0/2/1/0.3.8.0.0.0.1 sdisk
0/2/1/0.3.10.0.0.0.1 sdisk
0/4/1/0.3 fcd_fcp
0/4/1/0.3.8.0.0 fcd_vbus
0/4/1/0.3.8.255.0 fcd_vbus
0/4/1/0.3.10.0.0 fcd_vbus
0/4/1/0.3.10.255.0 fcd_vbus
0/4/1/0.3.8.0.0.0 tgt
0/4/1/0.3.8.255.0.0 tgt
0/4/1/0.3.8.0.0.0.0 sdisk
0/4/1/0.3.8.255.0.0.0 sctl
0/4/1/0.3.8.0.0.0.1 sdisk
0/4/1/0.3.10.0.0.0 tgt
0/4/1/0.3.10.255.0.0 tgt
0/4/1/0.3.10.0.0.0.0 sdisk
0/4/1/0.3.10.255.0.0.0 sctl
0/4/1/0.3.10.0.0.0.1 sdisk
0/1/1/0.0.0 sasd_vbus
0/1/1/0.0.0.0 tgt
0/1/1/0.0.0.0.0 sdisk
0/1/1/0.0.0.1 tgt
0/1/1/0.0.0.1.0 sdisk
Boot device's HP-UX HW path is: 0/1/1/0.0.0.1.0

System Console is on the Built-In Serial Interface
igelan0: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at
hardware path 0/1/2/0
igelan1: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at
hardware path 0/1/2/1
WARNING: ROOT device 0x1f091002 is a non-LVM partition,
disallowed on LVM disk.
WARNING: ROOT device 0x1f091002 has been deconfigured (set to
0xffffffff).


-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Non-lvm root on LVM disk
| |
-----------------------------------------------------


System Panic:

panic: LVM: Configuration failure
Stack Trace:
IP Function Name
0xe0000000012d5380 lv_boothalt+0x110
0xe0000000012dc920 lv_check_boot+0x60
0xe0000000012dc810 lvmconf+0x2f0
0xe0000000012e2590 im_lvmconf+0x70
0xe000000001762d10 DoCalllist+0x3a0
End of Stack Trace

linkstamp: Mon Nov 03 18:46:07 MEZ 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.

[Steven E. Protter]

Shalom,

Your system suffered hardware damage when power was lost.

This is why we recommend backup power, to at least deal with short outages.

Probably a disk or controller took the damage, but it looks like a hardware call will be needed to fix it.

SEP

[inukoti]

Thanks for your reply. I already opened a case and HP Support told its a problem of SW not HW and we dont have SW support .

[Albert Smith_1]

Since you were able to boot via the media it's not a hardware issue unless there was a physical disk failure. Which it doesn't seem like you have. However it more leads to the fact that you have some corruption in /stand/current as it can open the config.krs

does the /stand/current/krs directory exist?

can you boot in maint mode?

http://www.docs.hp.com/en/B2355-60105/krsd.1M.html

[shanmuhanandam]

Hi,
can you please check the boot paths...
there is some diifrence in the boot paths,,


Loading.: HP-UX Primary Boot: 0/1/1/0.0.0.2.0
Starting: HP-UX Primary Boot: 0/1/1/0.0.0.2.0

Boot device's HP-UX HW path is: 0/1/1/0.0.0.1.0

System Console is on the Built-In Serial Interface
igelan0: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at
hardware path 0/1/2/0


Thanks,
Shanmugam.B

[sujit kumar singh]

hi


go to the EFI shell and try booting system in LVM maintenance mode.

in the EFI screen, choose built-in EFi shell.

SHELL> fs0:
fs0:> cd efi\hpux

there give command boot hpux -lm

check if you can get the system booted in lm that is LVM Maintenance Mode.

regards
sujit

[inukoti]

Thanks for your replies
@ singh i have tried before posting here but same result.

so I have installed new os on a disk and sucessfully repaired the LVM and imported.

Thanks once again for your help