Primary disk failed + related problems

[H2K]

1. As far i know, we only can reset via console with GSM. How about reset it remotely?

2. Would a primary mirror boot disk failed trigger the Attn light? Sytem is up & running on secondary boot disk.

3. If a primary book disk failed caused the make_recovery backup failed? My make_recovery is failed since pri disk failed.

[RAC_1]

1. You reset remotely as long as you can logonto GSP.

2. Yes it may trigger flashing attn light. As boot disk was mirrored system would continue running.

3. Yes ignite will fail.

[H2K]

Need more detail..
1. Beside install terminal server for remote console, what else can i do to reset the light?

2. Was told by Hp and confirmed with onsite visual checking, the primary disk failed not 'bad' enough to trigger the Attn light. Any command to check the health of the boot disk or any other visual contact ?

3. How it caused my make_recovey failed?

[RAC_1]

Need more detail..
1. Beside install terminal server for remote console, what else can i do to reset the light?

2. Was told by Hp and confirmed with onsite visual checking, the primary disk failed not 'bad' enough to trigger the Attn light. Any command to check the health of the boot disk or any other visual contact ?

3. How it caused my make_recovey failed?

Ans.

1. reset light? what light you are talking abt. explain.
2. What caused the attn light to flash? Login onto gsp, sl command and checkfor errors. Health check of boot disk.
lvlnboot -v
lifcp /dev/rdsk/xxx:AUTO - --> shows boot string.

lifls -l /dev/rdsk/c1t15d0 --> lists lif area conetnts
Sureshot method-->Use setboot to change primary boot path. Shutdown the system replace failed disk and boot from secondary.
Once up on secondary disk, vgcfgrestore, on replaced disk, vgsync.


3. Not very sure. But ignite do looks for boot disk, if that has failed ignite may fail.

[RAC_1]

Detailed procedure for replacing failed boot disk.

Rebuilding a Mirrored OS Disk

Once you have located the OS disk that has failed:

· Verify that this disk is not on EMC or AutoRaid
These disks are Hot Swappable and will need little interaction, the system will remain running during the full process.
1. Call HP, Swap disk
2. See step 10-14 below

· If this disk is internal or on Jbod do the following:
1. Identify the device file (/dev/dsk/c0t3d0 ) and hardware path (8/0.3.0 )
of the faulty disk. ioscan -fnCdisk
2. Identify disk type (If Possible) diskinfo /dev/rdsk/c0t3d0
3. Call HP to come out.
4. Identify volume group name ( vg00 ) pvdisplay /dev/dsk/c0t3d0
5. Identify the device file and hardware path of the remaining good mirrored disk. vgdisplay -v vg00|more & ioscan -fnCdisk
6. Save off a copy the correct file in /etc/lvmconf/vg00.conf to a safe place.
7. Change primary boot path to the good mirror copy setboot -p 8/0.6.0
8. Identify run level more /etc/inittab init: (3) = run level three
9. You need to override quorum. This is done after Hp has swapped out the disk.
v Stop the system at reboot, bo pri and interact with ISL
v Bring the system up without quorum in single user mode.
ISL> hpux -is -lq (;0)/stand/vmunix
10. Restore the LVM configuration headers. After system has been shutdown and the disk is replaced and quorum is off. vgcfgrestore -n /dev/vg00 /dev/rdsk/c0t3d0
11. Activate the volume group. vgchange -a y /dev/vg00
12. Start the Mirror synchronize process. vgsync /dev/vg00
13. Mount /usr to enable the mkboot commands. mount /usr
14. Place the boot utilities in the boot area.
mkboot /dev/rdsk/c0t3d0
mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/c0t3d0
15. Place the diagnostic info in the lif.
If the server is 11.x, first determine if it is 32 or 64 bit:
getconf KERNEL_BITS
If the server is 10.20 or 11.x 32 bit:
mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c0t3d0
If the server is 11.x 64 bit:
mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c0t3d0

16. Update LIF's Table File with information contained in the BDRA (Boot Data Reserved Area) lvlnboot -Rv /dev/vg00
17. You are still in single user mode at the prompt type init 3 (step 8) this brings the system the rest of the way up.
18. Change back the primary boot path setboot -p 8/0.3.0


Don't attempt to lvreduce the mirrors. Or vgreduce out the disk. These will both hang because of the faulty disk. Over riding quorum with vgchange will also han

[H2K]

Attn Light . Can we see the GSP log with out using CTRl-B at console?


If Primary boot disk ( internal disk) failure could not trigger the Attn light, is there a way to perform health check on the disk?

[Con O'Kelly]

Hi

I believe you can only clear the Attn Light by viewing the GSP logs at the GSP prompt (ie 'SL' option).

As far as I'm aware with HP there is no good way of checking a disks health & predicting when it will fail. The important thing is to monitor the disks, so that you are aware a disk has failed. Obviously its also important to have setup redundancy (mirrors, RAID etc) so that the impact of disk failures is minimised.

With EMC disks, I believe EMC monitor the number of read/write errors and replace the disks once a certain number of errors have occured. In this way they try to reduce the number of actual disk failures.

Cheers
Con