- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- POST 177 error on ProLiant 3000
ProLiant Servers (ML,DL,SL)
1754252
Members
3481
Online
108812
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
Discussions
Discussions
Forums
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
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
тАО09-19-2006 09:10 AM
тАО09-19-2006 09:10 AM
POST 177 error on ProLiant 3000
On a Compaq ProLiant 3000 (remote location) running NT4 with an external array attached, have recently been getting the following error during boot: "POST Error: 177-Configuration Not Complete Controller Order Not Setup". Pressing F1 to continue just reboots the server. So far, the only way to get past this is to have site contact power down server, power down array, power up array and power up server. Then he is still prompted for F1, but this time server boots. I have searched long and hard for the 177 error in relation to the Proliant 3000, but only see references to it for other models. Have also talked to HP Support, and they have no reference to this error with the 3000 model.
Looking at the System Management Homepage, there is no indication of hardware failure/degradation, and this server has been in production status since 1999. First noticed approximately 1 month ago. No hardware changes have happened, and the only software change (that I'm aware of) was applying the MS06-040 Windows security patch.
In the references I have found to the POST 177 error, it indicates that we need to run the System Configuration Utility and correct. Does anyone else have any other solution, or is this the correct one for the 3000 model? Any ideas as to what would cause the system to all of a sudden think it is misconfigured?
Thanks
Looking at the System Management Homepage, there is no indication of hardware failure/degradation, and this server has been in production status since 1999. First noticed approximately 1 month ago. No hardware changes have happened, and the only software change (that I'm aware of) was applying the MS06-040 Windows security patch.
In the references I have found to the POST 177 error, it indicates that we need to run the System Configuration Utility and correct. Does anyone else have any other solution, or is this the correct one for the 3000 model? Any ideas as to what would cause the system to all of a sudden think it is misconfigured?
Thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-19-2006 06:45 PM
тАО09-19-2006 06:45 PM
Re: POST 177 error on ProLiant 3000
Hi Greg,
Try checking the SW2 switch, the SW2 configuration switches all need to be set to OFF.
Sometimes if the switch 7 is set to on you can get this error.
Regds
NS
Try checking the SW2 switch, the SW2 configuration switches all need to be set to OFF.
Sometimes if the switch 7 is set to on you can get this error.
Regds
NS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-19-2006 09:47 PM
тАО09-19-2006 09:47 PM
Re: POST 177 error on ProLiant 3000
As you have mentioned running System Configuration Utility is the right way from where you can set the Boot Controller order
Incase it still continues,it would be worth checking the System CMOS battery which may need a replacement as in case issue is recurring,it may be that the CMOS settings are not getting preserved.
Incase it still continues,it would be worth checking the System CMOS battery which may need a replacement as in case issue is recurring,it may be that the CMOS settings are not getting preserved.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP