boot error

[Balasubramanyam Verabat]

I am trying to boot a K-Class Server. While trying to boot from the PRIMARY Boot device it comes up with the following error message.

WAR A0BD
Boot Device Not Ready.
Retrying Boot Device..
Boot Device Not Ready.
Retrying Boot Device..

Could anyone please help in resolving this.

[S.K. Chan]

WARN A0BD (a boot device initialization error) means ..
"entry initialization failure because device not ready"

You probably have a corrupted boot area on your root disk, the system can see it, just could not boot from it.

[Balasubramanyam Verabat]

Could you please let me know how to resolve this problem.

[S.K. Chan]

Is the root disk mirror ?
Do you have a make_recovery tape ?

[Vincent Farrugia]

Hello,

Before booting, stop the boot process. Then type sea ipl. Check whether the bootable disk is visible through here.

HTH,
Vince

[Balasubramanyam Verabat]

I do have an Ignite Image of the root disk. I believe that I need to do make_recovery tape and boot off from it.

[Carlos Fernandez Riera]

Frist ry to boot from tape ( select run recovery shell) , and run ioscan to see if disk if broken.


If it is broken, of course you must change...

[Nelson Chamba]

Look, i have the same erro but i don´t have the ignite or backup of this system. I can see many path from the SEA command.

Path# Device Path Deice path (mnem) Device Type
-------------------------------------------------------------
P0    8/12.14      Random access media
P1    8/12.13      Random access media
P2    8/12.12      Random access media
P3    8/12.3         Random access media
P4    10/0.15      Random access media
P5    10/0.6        Random access media
P6    10/0.5        Random access media
P7    10/0.4        Random access media
P8    10/8.14     Random access media
P9    10/8.13     Random access media
P10 10/8.12     Random access media
P11 10/8.3       Random access media
P12 10/12.6.0 lan.0 LAN Module
P13 10/16/4.8 Random access media
P14 10/16/4.9 Random access media
P15 10/16/4.10 Random access media
P16 10/16/4.11 Random access media
P17 10/16/8.1 Sequential access media

Can someone help me please.

Regards,

Nelson Chamba\

[Robert_Jewell]

You can see many paths, but how many of these are boot disks?

Try the following:

SEA IPL

That will report drives that have a boot strap installed.  Try booting from each of those.  If none show up, then your boot disk is probably failed.

-Bob

[Nelson Chamba]

Hi Robert,

Now i can see the ISL promt, how can o proceed.

I have the paths:

Primary 10/0.15.0.0.0.0
Alternative 8/12.13.0.0.0.0

Regards,

[Torsten.]

Try

boot pri

or

boot alt.

Don't interact with ISL. Capture the output.

[Robert_Jewell]

If you are at an ISL prompt you can proceed by typing 'hpux'.  You got there by answering Y to the question about interacting with IPL....or you have a problem with the kernel or AUTO file.

-Bob

[Nelson Chamba]

Hi all

From the ISL I typed the SEL IPL and the output was this:

P0  10/8.12          Random Access
P1  10/12/6.0      Lan.0

The output of the PA command i got this:

Primary Boot Path fwscsi.15
                                                  10/0.15
Alternate Boot Path               8/12.13
Console Boot Path                10/8.0
Keyboard Boot Path            10/12/7.0

When i run the BO ALT in order to boot from the alternative path i got his feedback:

Boot IO Dependent Code (IODC) revision 152
IPL error: bad LIF magic
Error reading IPL

From the main boot path, BO PRI i got this feedback:

Booting ...
Boot Device Not Ready . . .
Boot Device Not Ready . . .
Retrying Boot Device . . .

How do i proceed?

Regards,
NC

[Torsten.]

Hi from the ISL in typed the SEL IPL and the output was this:

P0 10/8.12 Random Access

Try "bo p0"!

[Robert_Jewell]

and if that works set the primary boot path from the OS as follows:

# setboot -p 10/8.12.0

If you want the system to autoboot to this path:

# setboot -s on -b on

-Bob

[Nelson Chamba]

Hi Torsten,

It´s working, after the bo p0 it returned me this:

Booting...

Boot IO Dependent ....

Hard Booted

ISL>hpux and the result was booting

Boot

:disco()/stand/vmunix

...

...

but still giving me erros and kernel panic.

I rebooted againt to check if can reproduce the error and share here.

Regards,

Nelson CHamba\

[Nelson Chamba]

Dear all,

According with the erros i got from the screen, I can see that It can boot from the alternative path but still looks for the PV where the root VG is, and this PV is from the failed disk or problematic path.

It can´t boot from the 10/0.15 but it boots from 10/8.12 and after that end up on kernel panic because is looking for the PV located on the (10.0.15).

Any idea please.

See the screenshots for more details.

Regards,

Nelson Chamba\

[Torsten.]

Try this:

Looks like the disks are mirrored, so you can also try quorum mode from ISL:

> hpux -lq

- if this doesn't work, from ISL do

> hpux -lm

to start in maintenance mode

once you have a prompt, do vgdisplay -v vg00

[Nelson Chamba]

Dear all,

after the options "hpux -lq" it goes to the step from the screen and takes longer.

Regards,

NC\