failed alt boot disk

[singis]

Hello all,
I have a failed alternative mirrored boot disk. I shutdown the server hard way and pulled out the bad disk, I donot have a disk this to replace the failed disk can I start the system with out this alt boot disk.
Thanks,
Singis.

[Pete Randall]

Yes, that is the whole point of mirroring. If you did not alter your boot string to "hpux -lq" to ignore quorums, you will need to interrupt the boot process so you can manually enter the "hpux -lq".


Pete

[Devender Khatana]

Hi,

If the boot strings is set to "hpux -lq" in AUTO file then the system will come up without alternate disk after giving failed disk warning.

If the strings is not set then you need to halt at ISL prompt and select interact with IPL,at IPL prompt give "hpux -lq"

Then it should boot normally but will take some more time as it will wait for timing out failed disk.

HTH,
Devender

[Luk Vandenbussche]

It also a good idea to remove the mirror after you bootup with the option -lq, otherwise you have to boot always with the option -lq

lvreduce -m 0 -k /dev/vg00/lvolx /dev/dsk/cxtydz

[Geoff Wild]

Only if you have it set to no quoron...

hpux -lq

Check with:

lifcp /dev/rdsk/cXtXdX:AUTO -

Rgds...Geoff

[Morcos]

Hi,

yes you can start the system without the alt boot disk. If the primary boot disk was set to "hp-ux lq" start with low quorum, the system will start automatically, if not on the PDC type sea, boot from the primary path, interact with IPL -->yes, then type hpux -lq, so it will start with low quorum.

Good luck,
Ziad

[Devender Khatana]

Hi,

For booting normally after once booting through "hpux -lq" option rather than reducing lv's and vg's I would suggest to put the default option to "hpux -lq" in AUTO file. For root mirrored system infact I always put it that way alongwith mirroring itself so in the scenarios like this you are not required to supply option manually.

To see current setting
#lifcp /dev/rdsk/c1t2d0:AUTO -

To set the same to "hpux -lq"
#mkboot -a "hpux -lq" /dev/rdsk/cxtydz
(Where /dev/rdsk/cxtydz is your working boot disk.)

HTH,
Devender

[singis]

Hello all,
Thanks for your help.
I tried to restart my server but for some reason it is not booting, can any one tell me what the problem might be. On the server panel it show me init ### cnsl ptr and it is stuck there none of my disks drives have any lights on them and nth is coming up on the console screen.
can you guys help me.
Thanks,
Singis.

[MarkSyder]

Are you able to interrupt the boot or does it not get that far? If not, where does it stop?

I wouldn't worry too much about disc drive lights not coming on. When I called an engineer out to a faulty disc a few months ago, I confidently pointed to the disc without an activity light and said that was the faulty disc. The engineer pointed out to me that the "activity" light was actually an error light and it was the other disc that was faulty!

Mark Syder (like the drink but spelt different)

[Bill Hassell]

Very important: when you created the mirror disk the first time, did you use pvcreate -B and run mkboot and mkboot -a on the additional disk? If not, all you have are the mirrored logical volumes (still intact) but no way to bootup because there is no boot code on the mirror.

[Torsten.]

Hi Singis,

"On the server panel it show me init ### cnsl ptr "

sounds like it is a D- or K-Class Server. Until there is no menu at all, the display is the only source for information.
What kind of server you have?

[singis]

Hello Terston,
It is a K380 server. It is not booting, I cannot see anything on the console. The information I gave you was on the server panel.
Thanks,
Singis.

[Torsten. · Accepted solution]

Try to reset the console first by switching off, holding the "D" Key pressed while switching on. Now turn the key switch on the server to position "service" an restart. Now you should see some codes at the bottom of the screen. Watch for any warning or fault massages.

[singis]

Hello all,
That worked Torsten, I could see the error in my console.
It should me the primary boot path, the alt boot path
it said CPU 0
It gave me a warning: Memory has been intialized, but not tested as a result of FAST BOAT being enabled. TO test may use
FASTBOAT command in the config menu and reboat the system.
Can any one help me with this.
Thanks,
Singis.

[Torsten.]

The fastboot message is a warning only. With fastboot disabled, there will be no warning about this and the memory will be tested more intensive.

How about booting?

Try to do a search command

SEA IPL

[singis]

Hello Torsten,
I did the sea, but it is stuck there forever.
THanks,
Singis.

[Torsten.]

Are you sure about the bad disk?

Perhaps you removed the good one and the failed is still inside.

[singis]

Hey buddy,
I had the same qus so I put the removed disk again in and tried to boat but there was no luck.
Thanks,
Singis

[Q4you]

I assume you are using the JBOD. Pl check the JBOD is powered up (!). If you have a JBOD, each disk slot has hardcoded, SCSI ID. Insert the original disk from where you removed. hope you labeled the disks /slots before removing them.


To boot your system again, the "search" command at Console Menu must list the bootable devices on the system. If you don't see your disk's correct HW PATH address with SCSI ID, there is problem at the HW level ( may be introduced one) you will not be able to boot.

-Q

[Bill Hassell]

Did you replace a disk inside the K380? If so, was the disk the special FWD HighVoltage SCSI disk required in the K-class computers? If you used any old SCSI disk, it will fail and lockup all devices on the SCSI bus. FWD HighVoltage is completely incompatible with any other SCSI disk. You will also have to match the jumpers on the new disk with the ones on the old disk.