System Panic during boot process

[kdawg]

Trying to increase the size of vg00(new disk c1t2d0) without success. What am I missing that causes the system to panic so early in the process.
The lvlnboot looks good before I try to reboot. What other options do I have other than make_tape_recovery? It appears lvol3 is corrupt even when I try to boot into hpux -lm mode. Any suggestions would be greatly appreciated.


ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux -lq

Boot
: disk(0/0/1/1.2.0.0.0.0.0;0)/stand/vmunix
7319552 + 1096640 + 4651072 start 0x21ad68


alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x7f9a8000.
gate64: sysvec_vaddr = 0xc0002000 for 1 pages
NOTICE: autofs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 5.
TSCTTL: installing...
TSCTTL: init called
TSCTTL: initiated successfully
TSCTTL: installed successfully

System Console is on the Built-In Serial Interface
Logical volume 64, 0x20003 configured as ROOT
Logical volume 64, 0x20002 configured as SWAP
Logical volume 64, 0x20002 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x20002; start = 0, size = 3792896

************* SYSTEM ALERT **************
SYSTEM NAME: smsc4-gsp
DATE: 11/05/2005 TIME: 18:36:10
ALERT LEVEL: 12 = Software failure

REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF OFF ON
LED State: Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 0000690A 0512240A - type 11 = Timestamp 11/05/2005 18:36:10
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:a
*****************************************

************* SYSTEM ALERT **************
SYSTEM NAME: smsc4-gsp
DATE: 11/05/2005 TIME: 18:36:10
ALERT LEVEL: 12 = Software failure

REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
ON FLASH FLASH OFF ON
LED State: System Running. Unexpected Reboot. Non-critical Error Detected.
Check Chassis and Console Logs for error messages.

0xA0E000C01100B000 00000000 000005E9 - type 20 = major change in system state
0x58E008C01100B000 0000690A 0512240A - type 11 = Timestamp 11/05/2005 18:36:10
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:a
*****************************************

************* SYSTEM ALERT **************
SYSTEM NAME: smsc4-gsp
DATE: 11/05/2005 TIME: 18:36:18
ALERT LEVEL: 3 = System blocked waiting for operator input

REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
ON FLASH FLASH OFF ON
LED State: System Running. Unexpected Reboot. Non-critical Error Detected.
Check Chassis and Console Logs for error messages.

0xF8E000301100E000 00000000 0000E000 - type 31 = legacy PA HEX chassis-code
0x58E008301100E000 0000690A 05122412 - type 11 = Timestamp 11/05/2005 18:36:18
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:a


Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t2d0
Root: lvol3 on: /dev/dsk/c2t2d0
Swap: lvol2 on: /dev/dsk/c2t2d0
Dump: lvol2 on: /dev/dsk/c2t2d0, 0

Boot Definitions for Volume Group /dev/vgroot:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
Swap: lvol2 on: /dev/dsk/c1t2d0
Dump: lvol2 on: /dev/dsk/c1t2d0, 0

[Steven E. Protter]

/dev/vg00/lvol3 131072 79983 48528 62% /


Is root.

If it is corrupt the system will probably have to be recovered via make_tape_recovery

First though boot into single user mode and see if fsck can fix it.

fsck -F vsfs -o {options}

Answer all questions yes.

You'll probably need to boot off of the Core OS cd.

SEP

[Howard Marshall]

Based just on what you have posted, I assume you are replacing the existing boot disk.

How did you get the data over to the new disk?

Have you checked to see if there are any patches you need to build into the kernel in order for it to boot from this new disk?

Just my personal experience with this kind of thing. The make recovery tape is by far the way to go and on the same machine if possible.

Trying to do things differently than that inevitably leads to some sort of complication or other. I understand that its not always an option, just expect issues if you have to shirk around it.

I know that doesn't help much, score this one a 0 on helpfulness, just tossing out some ideas.

H