- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ML350 G5 Unable to Boot running Server 2003
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
Forums
Discussions
Discussions
Discussions
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
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
08-20-2015 06:18 PM - edited 08-20-2015 06:21 PM
08-20-2015 06:18 PM - edited 08-20-2015 06:21 PM
ML350 G5 Unable to Boot running Server 2003
History of problem:
Initial issue is Server wouldn't boot. Noted Smart Array e200i (v1.80) Controller errors: 1794 (Battery charge low), 1729 (Disk Performance Optimization Scan), and 1720 (HDD Imminent failure).
Steps take to resolution thus far:
1. Replaced Smart Array Battery and after 48 hours, errors 1794 and 1929 no longer occur. However, 1720 does still appear.
2. Tried removing failing HDD, but same error occurs when Windows does attempt to load: LSASS.exe - System Error. Security Accounts Manager initialization failed because of the following error: Directory Service cannot start. Error Status: 0xc00002e1. Please click .... system further.
3. Attempted Repair install using Server 2003 Disc 1, but during the repair install, the same error as in #2 above appears.
4. Two or three times, errors for *** Hardware malfunction, Call yoru hardware vendor for support, NMI: Parity Check / Memory Parity Error, *** The system has halted *** occurred. However, the past couple of restarts, this error has not occurred. I'm assuming, at first thought, this is due to impending HDD failure.
Notes: I noticed a hotfix for the error/issue in #2 above but it requires me to be able to boto into Windows to apply it.
Any help is greatly appreciated.