system crash recovery

[Ying Li_1]

I'm looking for a way to restore some of data (under /home directory) from a system that couldn't reboot. Does sombody can help me?

Thanks,
-Ying

When entering single user mode, We couldn't bring the system up.

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

HPUX> hpux -is
> System Memory = 16351 MB
loading section 0
............................................................... (complete)
loading section 1
................ (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (bootfs) to MFS
.........................
Launching /stand/vmunix
SIZE: Text:32197K + Data:7934K + BSS:5412K = Total:45544K

Console is on a Serial Device
Booting kernel...


Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 16351 MB 16351 MB 16351 MB
Kernel : 16351 MB 16351 MB 16351 MB
User : 15344 MB 15029 MB 13424 MB
-------------------------------------------------------------------------

Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
NOTICE: mod_fs_reg: Cannot retrieve configured loading phase from KRS for module: cifs. Setting to load at INIT

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

System Console is on the Built-In Serial Interface
iether0: INITIALIZING HP AB352-60001 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/1/2/0
iether1: INITIALIZING HP AB352-60001 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/1/2/1
iether4: INITIALIZING HP AD331-60001 PCI/PCI-X 1000Base-T Adapter at hardware path 0/4/2/0
iether3: INITIALIZING HP AD331-60001 PCI/PCI-X 1000Base-T Adapter at hardware path 0/4/1/0
igelan2: INITIALIZING HP A6825-60101 PCI 1000Base-T Adapter at hardware path 0/5/1/0
Logical volume 64, 0x3 configured as ROOT
igelan2: INITIALIZING HP A6825-60101 PCI 1000Base-T Adapter at hardware path 0/5/1/0
Logical volume 64, 0x3 configured as ROOT
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
0xe000000001345000 lv_boothalt+0x110
0xe000000001344a70 lv_bootconf+0x3c0
0xe00000000134c480 lvmconf+0x2e0
0xe000000001352210 im_lvmconf+0x70
0xe0000000017d1890 DoCalllist+0x3a0
End of Stack Trace

linkstamp: Tue Oct 16 14:32:36 MDT 2007
_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.

[Tingli]

boot from cd then mount the disk to /mnt. The files should be still there.

[R.K. #]

Hi.....any backup like ignite?

[yulianto piyut]

Restore from the ignite backup (if you have) to another server.

[Laurent Menase]

Hi Ying,

did you try hpux -lc to boot without the corum?

or in maintenance mode -lm

[Joe Kanakaraj]

Try to boot the system with your old kernel.

At the ISL issue the command:

hpux /stand/vmunix.prev

You should be able to boot up the system and get your /home mounted

[john123]

Try
HPUX> boot vmunix -lq


Regards
John

[vjta]

Hi ying

try to boot withou chorum
by -lq
also u can restore thru Ignite backup

regards
vjta

[OldSchool]

if you've got mirrored root disks, one of them has failed. it *should* have been set up to boot w/o the full quorum of disks, but it appears that it wasn't.

try the -lq switch as described above, then fix the failed drive