- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Degraded State | HP ProLiant ML310 Gen3 v2 Server
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
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
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
07-10-2015 02:17 AM
07-10-2015 02:17 AM
Degraded State | HP ProLiant ML310 Gen3 v2 Server
HP ProLiant ML310 Gen3 v2 Server
The system health indicator (steady blinking amber) indicates the system is in a degraded state. Memory (memtest86), internal fans, and HDD's all pass diagnostic tests.
The server is under warranty.
I have gone through the HP documentation - what additional specific component tests should be performed to verify the cause of the 'dregraded state' health?
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2015 05:59 AM
07-10-2015 05:59 AM
Re: Degraded State | HP ProLiant ML310 Gen3 v2 Server
Gen3?
Is it Gen8 maybe?
If Gen8 v2, then connect to ILO, check ILO and IM logs and check status from there.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2015 01:36 PM
07-10-2015 01:36 PM
Re: Degraded State | HP ProLiant ML310 Gen3 v2 Server
Yes we need logs first.
If the system is reporting a degraded state but all drives are passing diagnostic, then most likely scenario is inconsistent parity due to intermitent drive failures.
You need to determine if any drives have fallen out of the array in the past from the logs first.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2015 01:37 AM
07-26-2015 01:37 AM
Re: Degraded State | HP ProLiant ML310 Gen3 v2 Server
Pardon the long delay. Update / logs follow.
After updating the iL0 4 firmware the system health indicator reverted to healthy.
localhost:2381 displays health system status.
IML Logs (multiple occurences of memory module 4 log entry and stop code 0x00000002).
-
Critical 30 | Operating System | 5/14/2015 14:52 | 1
Operating System failure (Windows bug check STOP: 0x00000050 (0xFFFFF8800CF5C289 0x0000000000000000 0xFFFFF8800182B4A1 0x0000000000000000))
Critical 46 | Operating System | 16/24/2015 05:49 | 1
Operating System failure (Windows bug check STOP: 0x0000000A (0x00000000496AD1CA 0x000000000000000B 0x0000000000000000 0xFFFFF80001FFF648))
Critical 57 | Operating System 1 6/28/2015 18:26 6/28/2015 18:26 | 1
Operating System failure (Windows bug check STOP: 0x00000019 (0x0000000000000003 0xFFFFF8800BD68170 0x1898E1FA00050CA0 0xFFFFF8800B9E8170))
Critical 62 | Main Memory | 23 | 7/2/2015 07:47 | 1
Uncorrectable Memory Error ((Processor 1 Memory Module 4))
Critical 61 | Unrecoverable System Error | 3 | 7/2/2015 07:47 | 1
An Unrecoverable System Error (NMI) has occurred (System error code 0x00000002 0x00040002)