Can't boot to HP10.20

[juno2]

My HPUX is running 10.20 , When I boot it , it pop up the below the below message,

Primary Boot Path
Alternative Boot Path
Console Path
Keyboard Path

Main Menu
Command
boot
PA
Search
Configure
Infracture
Service
Display
Help
Reset
Main Menu : Enter Command >

I tried to boot to different path eg. harddisk 0/1/2 , but all still failure, How can I fix it ? thx.

[Balaji N]

Hi,
I think autoboot is set to off. First try enabling autoboot from the config menu.

and regarding your problem. is the hard disk ur giving at the boot prompt is a bootable one?

could u pls give the exact error message?

hth
-balaji

[Rajeev Shukla]

Hi, This is the PDC prompt where you have reached.
Type Pri(primary path) to see the actual disks which the system needs to boot from.
then use sea(search) command to see if you can see that disk. If you cant see that disk then there is something wrong either with the disk or the cable or the contraller to which it is connected.
type
bo pri
to book through primary boot disk.

[Matthias Gottschalk]

Hi,
is the problem that the server is not automatically startup the bootup
process? (solution would be to switch on the autoboot flag in the
above shown menu).
If you type 'bo pri' in the command line is the system hanging
afterwards?
The output you gave above is the boot menu you normally enter
if the autoboot functionality is not switched in.

Regards,
Matthias

[schneider_15]

Hi
when you are on main menu try :

SEA

it will show you the different possible boot path.

At the beginning of each line you 'll see one of P0, P1, P2

You just got to type on the main menu
bo PX
where x represent the boot path tou choose.

regards

[juno2]

Hi Balaji N,

No exect errro message , just boot to that menu.

Hi Rajeev , Gottschalk , Schneider ,

I tried your method - bo pri , switch on autoboot , bo PX , but all can't boot , what can I do? thx.

[schneider_15]

What did the sea give you as boot path ??

[juno2]

Except re-install the system , can suggest how can I fix the problem ? thx.

[Matthias Gottschalk]

Hi,
if the 'sea' command gives you any bootable disk and you have a
problem with your kernel (it is not clear from the description were
the system is showing a problem) you migth use the former kernel.
This can be done by the following scenario:
=> bo pri (or this P command)
=> interact with ipl (yes please)
=> hpux /stand/vmunix.prev (from the ipl command line)

Regards,
Matthias

[juno2]

Hi Matthias Gottschalk,

I can't access IPL , cos it only boot to above menu .

[Matthias Gottschalk]

Hi,
does it mean all the 'bo' commands do only end in a refresh of the
menu? Normally if you execute 'bo' together with 'pri/alt/Px' (one of
those options) and in addition 'isl' you should be able to enter the
initial system loader.
One example:
'bo pri isl' should end in a question like 'do you want to interact with
isl/ipl'. If you have in principle no bootable device, this will of course
not work and you have to recover you system from tape. In the isl
command line a 'hpux ls' should show the contents of /stand.

Regards,
Matthias

[juno2]

Hi Matthias Gottschalk ,


Yes , it mean all the 'bo' commands do only end in a refresh of the
menu .

[harry d brown jr]

search your disks for a BOOTABLE partition:

At this menu prompt:

Main Menu : Enter Command >

ENTER "sea"

Wait for it to come back to the PROMPT, then post that OUTPUT here, so we can help you with the boot string.

You could have a damaged disk.

live free or die
harry

[juno2]

The HP UX is connected to the network previously, now it stand alone , is the reason for failure to boot due to the system can't search the network ? thx.

[V. Nyga]

Hi,

no, not at that time.
Please check also if the SCSI buses are terminated.

Regards
Volkmar

[juno2]

The SEA result is

P1 8/4.9 Random Access Media
P2 8/4.8 Random Access Media

P3 8/16.5.2 Random Access Media

P4 8/16/5.0 Squential Access Media

P5 8/16/6.0 Lan Module

I tried all , but fail,


Besides , i checked the SCSI , it is no problem.

[juno2]

I tried all the boot path, but still fail , what can i do ? thx.

[harry d brown jr]

Boot from a CD or a tape in maintenance mode, but you are probably going to end up rebuilding your machine if your disk(s) are hosed.

Do you have support on this machine? If so, call HP.

Do you have a make_recovery tape? And other current backups?

live free or die
harry

[pap]

Hi,
Please enable autoboot to ON, auto search to ON and check the SCSI connections to the internal disk drives. IF possible please remove the SCSI connection cable from the disks and connect it again, same do for the power cable to the disks.
One more thing, CHECK THE TERMINATOR ON THE MACHINE. I BET YOUR SCSI TERMINATOR IS NOT CONECTED TO THE MACHINE OR MIGHT BE MISSING.

Thanks ,
-pap

[K.Vijayaragavan.]

Your comment:

The HP UX is connected to the network previously, now it stand alone , is the reason for failure to boot due to the system can't search the network ? thx

My reply:

Connect the system as it was before the system actually went nonoperational.

I don't know the setup of your environment. In some cases workstations are congigured to boot the OS from a server in local network and then use local disk for other purpose. I f your case is also same then put the system in the net.

You may paste the "display all" IPL command o/p for more reference.

[juno2]

does the problem due to the boot file failure , can I recover it by the recovery disk ? ( but i really don't want erase any data on my server ) .

[juno2]

is it possible to recover the boot file by the recovery disk ? thx

[juno2]

I only want to boot it up and start the database , ( use one time only ) , what is the simpliest way that i can do ? thx.

[Michael Steele_2]

OK, HW or SW.

First: Check your PDC firmware logs for Alert level error messages above 13. Call HP if found. Use this procedure to find your logs:

Ctrl B, hit enter until you get a GSP> prompt, type SL(for system logs), type E (error logs), type enter (for no filter), type q (for quit after looking at the logs.

Second: As discussed above you have to see the boot disks with the SEA command or another possible HW problem may exist. Call HP if you can't, but first check your SCCI cables for attachments AND POWER if use and external device like a jamaica drive bay.

Third: Here is the sequece that should appear on your console during reboot.

RS or recycle power to reboot the machine.

Watch at the console for it to prompt 'To dicsontinue, press any key within 10 seconds'

At that point hit the space bar.

At the 'Main Menu: Enter Command >' prompt type 'bo pri' and hit return

When asked 'Interact with IPL (Y,N,Q)?>' enter Y

'ISL>' should now be displayed.

Fourth: From here you want to determine if your bootlif is corrupt. Use the command "hpux -ll" to list the contents of /stand and "hpux -lm -is" to boot up. This last command bypasses the bootlif, which may be corrupt, and uses the /stand/rootconf binary file instead. If this fails then, corruption exists and you'll have to remake the kernel with a recovery CD. If this succeeds, then use the recovery CD to remake the bootlif.

These procedures are just the beginning. Pose additional question as they arise.

Finally, you can use Ignite make_recovery tapes from other servers to restore this server as long as they are of the same HW class. For example, K Class, N and L Class, etc. This is called Ignite cloning and procedures can be found all over this website. Just remember not to accept the automatic restore but to interrupt the restore and use the advance configuration setup. For this you'll need all basic host information like ip address, file system sizes for /usr, etc., etc.

[Michael Steele_2]

This looks like an older system not using GSP. Is this a work station or a G or H class server?

OK, HW or SW.

First: Check your PDC firmware logs for Alert level error messages above 13. Call HP if found. Use this procedure to find your logs:

Looks like you'll have to go into Display for this. SL or Show Logs is the GSP title.

Second: As discussed above you have to see the boot disks with the SEA command or another possible HW problem may exist. Call HP if you can't, but first check your SCCI cables for attachments AND POWER if use and external device like a jamaica drive bay. Verify your cable connections, especially check to see if cross cables hasn't occurred. For example, SCSI cables in the right connectors?


Third: If you can see your boot disk then your system firmware is OK and you can proceed with the following:

bo pri

When asked 'Interact with IPL (Y,N,Q)?>' enter Y

'ISL>' should now be displayed.

From here you want to determine if your bootlif is corrupt. Use the command "hpux -ll" to list the contents of /stand and "hpux -lm -is" to boot up. NOTE: Do not boot up all the way to run level 3 with this command if it succeeds, instead, reboot again or use "hpux -is".

The "hpux -lm -is" command bypasses the bootlif, which may be corrupt, and uses the /stand/rootconf binary file instead. If this command fails then, corruption exists in your O/S and you'll have to remake the kernel with a recovery CD. If "hpux -lm -is" succeeds, then use the recovery CD to remake the bootlif.

Finally, you can use Ignite make_recovery tapes from other servers to restore this server as long as they are of the same HW class. For example, K Class, N and L Class, etc. This is called Ignite cloning and procedures can be found all over this website. Just remember not to accept the automatic restore option but to interrupt the restore and use the advance configuration setup. For this you'll need all basic host information like ip address, file system sizes for /usr, etc., etc. Use the folloing to begin with: http://www.software.hp.com/products/IUX/index.html