- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Proliant 2500 System Halted
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО05-13-2003 02:48 PM
тАО05-13-2003 02:48 PM
Proliant 2500 System Halted
172-EISA Configuration Nonvolatile Memory Invalid Initialization Aborted
162-System Options Not Set
1785-Slot 1 Drive Array Not Configured Run Compaq Array Configuration Utility
1702-SCSI Cable Error Detected, System Board
System Halted
My system BIOS is - E24 (12/01/1999) and my SMART-2/P Array Controller is (version 1.36). I thought I would be able to boot from the cd again after I did the erase part but I guess I was wrong. If anybody has any ideas please help. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2003 07:53 PM
тАО05-13-2003 07:53 PM
Re: Proliant 2500 System Halted
First of all the Smart Start 3.10B wont let you install W2K. You would definitely need an updated version of Smart Start otherwise you would end up downloading all kinds of Softpaqs from our website. The latest smart start CD your server would accept is 5.50B and that can be ordered by call 1-800-573-1099.
To update the firmware version of the controller you need to go to the following link:
http://h18007.www1.hp.com/support/files/server/us/download/14694.html
You will be asked to make four diskettes but make the first one only.
Now if you would like to order the smart start CD that's fine otherwise let us know 'cos I can give you whole bunch of SW which you would need to set up your server.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2003 06:43 PM
тАО05-14-2003 06:43 PM
Re: Proliant 2500 System Halted
-Scott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2003 07:32 PM
тАО05-14-2003 07:32 PM
Re: Proliant 2500 System Halted
In that case you will have to manually reset the Switch no 6 on SW1. By default the Switch is to the OFF position. You need to turn it ON and then power on the server. Once it goes through the post then power it down and put the switch back to it's original position. This should reset your server's configuration.
Cheers,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2003 08:22 PM
тАО05-14-2003 08:22 PM
Re: Proliant 2500 System Halted
However, in your case you get the following error...
1702-SCSI Cable Error Detected, System Board
System Halted
...which isn't normal and doesn't allow you to do anything because the server halts rather than proceeding to the basic hardware detection.
If we take the error literally, then you have a problem with a SCSI cable which is causing the system to halt. Some trial and error should easily expose the bad cable, after which you should be able to proceed normally as outlined earlier.