Failed to initialize with ENTRY_INIT Status = -7

[Suraj K Sankari]

Hi all,

This is the first time I am facing this problem, after changing root alternate disk I am not able to boot the server I am getting this error. server model is rp3440

Main Menu: Enter command or menu > bo alt
Interact with IPL (Y, N, or Cancel)?> n
Booting...
Failed to initialize with ENTRY_INIT Status = -7

fffffff9 1 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 3 9 0
454e4841 0 0 454e4841
0 1b 51 20
3 51 20 3
.... FAILED.

While do a search I am getting this output….

Main Menu: Enter command or menu > sea

Searching for potential boot device(s)
This may take several minutes.

To discontinue search, press any key (termination may not be immediate).

IODC
Path# Device Path (dec) Device Path (mnem) Device Type Rev
----- ----------------- ------------------ ----------- ----
P0 0/0/2/0.0 ide.0 Random access media 1
P1 0/1/1/0.1 intscsia.1 Random access media 1
P2 0/1/1/0.0 intscsia.0 Random access media 1
P3 0/1/1/1.2 intscsib.2 Random access media 1
P4 0/3/1/0.0 Random access media 10
P5 0/4/1/0.0 Random access media 10


Below is the lvlnboot output
myserver ==> lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c3t2d0 (0/1/1/1.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t0d0
/dev/dsk/c3t2d0
Root: lvol3 on: /dev/dsk/c2t0d0
/dev/dsk/c3t2d0
Swap: lvol2 on: /dev/dsk/c2t0d0
/dev/dsk/c3t2d0
Dump: lvol2 on: /dev/dsk/c2t0d0, 0

I have checked all the mirrors of this disk are good, no issue with the disk dd and diskinfo give good result, no stale found as well.

Please suggest what will be the issue…. Is the boot disk address is giving some problem?

Suraj

[S RAVI]

Hi Suraj,

please check if you can do list the lif files on your alt disk ?

Thanks
Ravi

[Ismail Azad]

Hi Suraj,

Normal causes for an ENTRY_INIT status=-7 could be because you are booting from the --wrong path-- or --non-existent device--. It can also mean the boot disk is --not responding--.

This most probably is the --root cause-- of the problem and a workaround can be found or a permanent solution.

Is there a problem in the "binding" of hardware paths for that disk?

Why is the disk not "responding"?.

Probably the answer to these questions could lead to the solution.


Regards
Ismail Azad

[Hakki Aydin Ucar]

did you try;
# ioscan -fnCdisk
is there any HW problem ?

and did you check the;
# vi /var/adm/syslog

Probably there is no bootable media in that address, check this out;
http://h30499.www3.hp.com/t5/Ignite-UX/RP3440-failed-to-initialize-with-entry-init-status-7/m-p/5179917#M22266

[Torsten.]

A

lifls

of the disk would be nice.

I have seen people installing the offline diags (for whatever reason?) without protecting the boot loader (hpux or ISL) - the result was an unbootable disk.

[Robert_Jewell]

Can you state that the disk was ever bootable? If so, then you could have a disk problem. If not, well...creating a mirror of a boot disk is great and all, but failing to test it before there are problems is just about as bad as not having one at all.

If you have an Ignite server or an OS CD you can boot to Recovery Mode and try to restore the boot LIF.

-Bob

[Andrew Rutter]

hi,

what does setboot say?

check the boot paths here

#setboot

it could be because you havent set the boot paths up correctly at PDC.

you can either do this in hpux or at PDC

post this output from setboot, or at least verify its set to the same path as your alt mirror

Andy