HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Failed to initialize with ENTRY_INIT Status = -7
Operating System - HP-UX
1832988
Members
3026
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2009 01:46 AM
08-25-2009 01:46 AM
Failed to initialize with ENTRY_INIT Status = -7
We are facing below error during lan boot for Ignite Restore.
I checked some related forum but couldnt get much help.
Main Menu: Enter command or menu > boot lan.172.16.25.47 install
Interact with IPL (Y, N, or Cancel)?> n
Booting...
Failed to initialize with ENTRY_INIT Status = -7
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
b 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
.... FAILED.
I checked some related forum but couldnt get much help.
Main Menu: Enter command or menu > boot lan.172.16.25.47 install
Interact with IPL (Y, N, or Cancel)?> n
Booting...
Failed to initialize with ENTRY_INIT Status = -7
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
b 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
.... FAILED.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2009 02:17 AM
08-25-2009 02:17 AM
Re: Failed to initialize with ENTRY_INIT Status = -7
Hello,
The ENTRY_INIT = -7 means a non-existent
device. The device address specified may be
a valid device address, but it points to a
device that is not installed and/or not
responding.
In other words, it means there is no
bootable media at the boot device specified.
Boot device in this case is the Ignite
server and it is not there for boot help.
Try this command at the firmware prompt:
search lan install
And see if your server can find anything to
talk to.
Otherwise, check these yourself:
a) Ignite server and this client are on the
same subnet or you are using boot helper;
b) Verify that Ignite server is running
properly;
c) You are using core LAN card for remote
boot;
d) There are no firewall rules that prevent
connections between client and the Ignite
server.
and so on.
Cheers,
VK2COT
The ENTRY_INIT = -7 means a non-existent
device. The device address specified may be
a valid device address, but it points to a
device that is not installed and/or not
responding.
In other words, it means there is no
bootable media at the boot device specified.
Boot device in this case is the Ignite
server and it is not there for boot help.
Try this command at the firmware prompt:
search lan install
And see if your server can find anything to
talk to.
Otherwise, check these yourself:
a) Ignite server and this client are on the
same subnet or you are using boot helper;
b) Verify that Ignite server is running
properly;
c) You are using core LAN card for remote
boot;
d) There are no firewall rules that prevent
connections between client and the Ignite
server.
and so on.
Cheers,
VK2COT
VK2COT - Dusan Baljevic
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP