System Error: LVM related

[Bona_1]

Hello.
I just changed a boot disk, and resynchronised it using the following steps

1) vgcfgrestore â n vg00 /dev/rdsk/cxtxdx
2) vgchange â a y vg00
3) vgsync vg00 (This process went on FOREVER)
4) mkboot â l /dev/rdsk/cxtxdx
5) mkboot â a â hpuxâ


After this, I rebooted the system and tried to boot of the primary. It didnâ t work. I then tried to boot of the mirror disk again (bo alt from BCH). It didnâ t work either. Now I have the complex problem where after synchronization, the formerly good disk isnâ t working anymore. This is the error I get when I try to boot the mirror disk

************* SYSTEM ALERT **************
SYSTEM NAME: smsc1
DATE: 03/05/2004 TIME: 15:42:07
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 ON 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 00006802 050F2A07 - type 11 = Timestamp 03/05/2004 15:42:07
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: smsc1
DATE: 03/05/2004 TIME: 15:42:07
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
OFF FLASH OFF ON ON
LED State: No code is executing. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0xA0E000C01100B000 00000000 000005E9 - type 20 = major change in system state
0x58E008C01100B000 00006802 050F2A07 - type 11 = Timestamp 03/05/2004 15:42:07
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: smsc1
DATE: 03/05/2004 TIME: 15:42:16
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
FLASH FLASH OFF ON ON
LED State: Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0xF8E000301100E000 00000000 0000E000 - type 31 = legacy PA HEX chassis-code
0x58E008301100E000 00006802 050F2A10 - type 11 = Timestamp 03/05/2004 15:42:16
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:a
*****************************************

Any assistance wil

[Sridhar Bhaskarla]

Hi,

Your mkboot commands are not readable. I would run them prior to doing a vgcfgrestore. You missed "lvlnboot" commands tto refresh boot,swap,root and dump lvols.

You didn't mention where the system was failing. I assume it is failing while it is trying to load the kernel.

I would try the following. Boot through primary. Interact with ISL.

ISL>hpux -lq

This should ignore the quorum and boot the system. Once it is in multi user mode, you can fix the issue.

If the above didn't boot, see if you could boot the system through LVM maintenance mode.

ISL>hpux -lm

If it boots in LVM maintenance mode,remove the alternate disk by reducing the mirrors. Make sure your lvlnboot information is correct.

If it is not successful in LVM maintenance mode also, then post with the exact error you are seeing so that further remedies may be suggested.

-Sri

[A. Clay Stephenson]

I suspect because of your Native font or CODEPAGE settings, your commands are garbled. It appears that your are missing the lvlnboot -R command.

Trying booting again and interrupt the boot process.
BOOT ALT
Interact with ISL? Y
When prompted enter "hpux -lq" to override quorum and you should be able to boot.

[Bona_1]

Hi. I don't know why it got jumbled up. these are the commands again:

1) vgcfgrestore -n vg00 /dev/rdsk/cxtxdx
2) vgchange -a y vg00
3) vgsync vg00
4) mkboot -l /dev/rdsk/cxtxdx
5) mkboot -a "hpux"

The server right now hangs just around the boot point... I'll paste an extract here
********************************
Boot
: disk(0/0/2/1.15.0.0.0.0.0;0)/stand/vmunix
6971392 + 901056 + 2882016 start 0x21ab68


alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x7f9ab000.
gate64: sysvec_vaddr = 0xc0002000 for 1 pages
NOTICE: autofs_link(): File system was registered at index 3.
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, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 20480000
ERROR: dump device 64:0x2 cannot be used and will be ignored:
can't get physical volume information of logical volume
WARNING: No dump devices are configured. Dump is disabled.

************* SYSTEM ALERT **************
SYSTEM NAME: smsc1
DATE: 03/05/2004 TIME: 14:59:22
ALERT LEVEL: 12 = Software failure
*******************************************

I actually tried to boot in single user and maintenance mode, but they both didn't work. I don't think it's because of the lack of a dump device, I was able to boot it despite that problem formerly.

[Kevin Wright]

connect to the GSP and run CL to view the console log. They are blocked by the Alert 12 I think.

[Sijesh]

Hi,

Problem might be because, you missed out the lvlnboot comamnds before restarting. Also I doubt the mirroing, as u mentioned vgsync process went on forever.

Try to boot in the maintenance mode frm from both the disks.

Sijesh

[Sanjiv Sharma_1]

Hi Bona,

This may help:

ISL> hpux -lq

After booting:

# lvlnboot -R

Verify that the mirrors were properly created.
# lvlnboot -v (example)
The output of this command is shown in a display like the following:
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c4t5d0 (10/0.5.0) -- Boot Disk
/dev/dsk/c4t6d0 (10/0.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c4t5d0
/dev/dsk/c4t6d0
Root: lvol3 on: /dev/dsk/c4t5d0
/dev/dsk/c4t6d0
Swap: lvol2 on: /dev/dsk/c4t5d0
/dev/dsk/c4t6d0
Dump: lvol2 on: /dev/dsk/c4t6d0, 0

Or, else boot in an lvm maintenance mode and run
# lvlnboot -R
# lvlnboot -v
# reboot

hth.

[Senthil Kumar .A_1]

hello bona,

Ur output of the boot procees suggests that the system is tring to boot from cxt15d0 ( that is, the device with scsi target id set to 15).But i'am unable to find on which hardisk u have performed vgcfgrestore beacuse it is mentioned as cxtxdx ,why don't u mention the exact device file name so it can shed some more light on the probelm u ar facing.I would like to know exactly what u were trying to do.
based on ur response i will try my level best in assisting you...

senthil

[Bona_1]

Hello all,
At the moment I am getting this error on both disks. As a matter of fact, I have tried to boot with "hpux -is", and the mirror disk (c2t15d0) boots hpux -lq by default. I will however try again with the "-lq" switch and let you know what comes out of it.

Thanks all.