- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Re: HP Proliant Microserver gen8 - Celeron version
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
тАО06-12-2017 10:09 AM
тАО06-12-2017 10:09 AM
HP Proliant Microserver gen8 - Celeron version
Hi all,
I have got this server to replace my old Synology NAS. It's less than 6 months old with 2 new 2TB WD RED drives in RAID 1, single 1.5TB backup drive and Debian 8 as a server system on a SSD. About two weeks ago the server went from blue to blinking red which suggests an error. Debian logs showed nothing wrong and I didn't bother with iLO at that time (everything worked after a reboot). Logged in through iLO after a second blinking event later and it showed me that a one of the HDD is failing (erasing) and the controller (PCIe P410) also showed an error. I also see in iLO that the second ETH port states "degraded - link down" even if it's not used. After the last red blinking and a reboot the hdd and controller looks fine again but it did a couple of times before. I have got a spare new P410 controller (got a new 2TB drive too just in case) but it won't fix the ethernet port. Any suggestions? The reason I'm asking is that I have seen some posts when the mtb had to be replaced in this server series. Thanks, Pepe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-12-2017 10:41 AM
тАО06-12-2017 10:41 AM
Re: HP Proliant Microserver gen8 - Celeron version
THe server won't pop into the red mode for a disconnetcted NIC. What error message does the iLO and IML logs show? Have you ran the array diagnostics utility?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-12-2017 10:54 AM
тАО06-12-2017 10:54 AM
Re: HP Proliant Microserver gen8 - Celeron version
The diagnostics showed nothing when I ran them after the reboot. However, looking at the IML it shows 3 different errors 5 count each. Internal and External enclosure on bay 0 Slot 1 and then Drive Array Controller on slot 1 error.
"ID","Severity","Class","Last Update","Initial Update","Count","Description", "63","Repaired","Network","06/11/2017 15:47","06/11/2017 15:47","1","Network Adapter Link Down (Slot 0, Port 1)", "62","Critical","Network","06/11/2017 15:47","06/11/2017 15:47","1","Network Adapter Link Down (Slot 0, Port 1)", "61","Repaired","Network","06/11/2017 14:47","06/11/2017 14:47","1","Network Adapter Link Down (Slot 0, Port 1)", "60","Critical","Network","06/11/2017 14:47","06/11/2017 14:47","1","Network Adapter Link Down (Slot 0, Port 1)", "59","Repaired","Network","06/11/2017 12:58","06/11/2017 12:58","1","Network Adapter Link Down (Slot 0, Port 1)", "58","Critical","Network","06/11/2017 12:58","06/11/2017 12:58","1","Network Adapter Link Down (Slot 0, Port 1)", "57","Repaired","Network","06/11/2017 10:37","06/11/2017 10:37","1","Network Adapter Link Down (Slot 0, Port 1)", "56","Critical","Network","06/11/2017 10:37","06/11/2017 10:37","1","Network Adapter Link Down (Slot 0, Port 1)", "55","Repaired","Network","06/11/2017 09:37","06/11/2017 09:37","1","Network Adapter Link Down (Slot 0, Port 1)", "54","Critical","Network","06/11/2017 09:37","06/11/2017 09:37","1","Network Adapter Link Down (Slot 0, Port 1)", "53","Repaired","Network","06/11/2017 08:37","06/11/2017 08:37","1","Network Adapter Link Down (Slot 0, Port 1)", "52","Critical","Network","06/11/2017 08:37","06/11/2017 08:37","1","Network Adapter Link Down (Slot 0, Port 1)", "51","Repaired","Network","06/11/2017 07:37","06/11/2017 07:37","1","Network Adapter Link Down (Slot 0, Port 1)", "50","Critical","Network","06/11/2017 07:37","06/11/2017 07:37","1","Network Adapter Link Down (Slot 0, Port 1)", "49","Repaired","Network","06/11/2017 06:37","06/11/2017 06:37","1","Network Adapter Link Down (Slot 0, Port 1)", "48","Critical","Network","06/11/2017 06:36","06/11/2017 06:36","1","Network Adapter Link Down (Slot 0, Port 1)", "47","Repaired","Network","06/11/2017 05:36","06/11/2017 05:36","1","Network Adapter Link Down (Slot 0, Port 1)", "46","Critical","Network","06/11/2017 05:36","06/11/2017 05:36","1","Network Adapter Link Down (Slot 0, Port 1)", "45","Repaired","Network","06/11/2017 04:36","06/11/2017 04:36","1","Network Adapter Link Down (Slot 0, Port 1)", "44","Critical","Network","06/11/2017 04:36","06/11/2017 04:36","1","Network Adapter Link Down (Slot 0, Port 1)", "43","Repaired","Network","06/11/2017 03:36","06/11/2017 03:36","1","Network Adapter Link Down (Slot 0, Port 1)", "42","Critical","Network","06/11/2017 03:36","06/11/2017 03:36","1","Network Adapter Link Down (Slot 0, Port 1)", "41","Repaired","Network","06/11/2017 02:36","06/11/2017 02:36","1","Network Adapter Link Down (Slot 0, Port 1)", "40","Critical","Network","06/11/2017 02:36","06/11/2017 02:36","1","Network Adapter Link Down (Slot 0, Port 1)", "39","Repaired","Network","06/11/2017 01:36","06/11/2017 01:36","1","Network Adapter Link Down (Slot 0, Port 1)", "38","Critical","Network","06/11/2017 01:36","06/11/2017 01:36","1","Network Adapter Link Down (Slot 0, Port 1)", "37","Repaired","Network","06/11/2017 00:36","06/11/2017 00:36","1","Network Adapter Link Down (Slot 0, Port 1)", "36","Critical","Network","06/11/2017 00:36","06/11/2017 00:36","1","Network Adapter Link Down (Slot 0, Port 1)", "35","Repaired","Network","06/10/2017 23:36","06/10/2017 23:36","1","Network Adapter Link Down (Slot 0, Port 1)", "34","Critical","Network","06/10/2017 23:36","06/10/2017 23:36","1","Network Adapter Link Down (Slot 0, Port 1)", "33","Repaired","Network","06/10/2017 22:13","06/10/2017 22:13","1","Network Adapter Link Down (Slot 0, Port 1)", "32","Critical","Network","06/10/2017 22:12","06/10/2017 22:12","1","Network Adapter Link Down (Slot 0, Port 1)", "31","Repaired","Network","06/10/2017 21:12","06/10/2017 21:12","1","Network Adapter Link Down (Slot 0, Port 1)", "30","Critical","Network","06/10/2017 21:12","06/10/2017 21:12","1","Network Adapter Link Down (Slot 0, Port 1)", "29","Repaired","Network","06/10/2017 20:12","06/10/2017 20:12","1","Network Adapter Link Down (Slot 0, Port 1)", "28","Critical","Network","06/10/2017 20:12","06/10/2017 20:12","1","Network Adapter Link Down (Slot 0, Port 1)", "27","Repaired","Network","06/10/2017 19:12","06/10/2017 19:12","1","Network Adapter Link Down (Slot 0, Port 1)", "26","Critical","Network","06/10/2017 19:12","06/10/2017 19:12","1","Network Adapter Link Down (Slot 0, Port 1)", "25","Repaired","Network","06/10/2017 18:12","06/10/2017 18:12","1","Network Adapter Link Down (Slot 0, Port 1)", "24","Critical","Network","06/10/2017 18:12","06/10/2017 18:12","1","Network Adapter Link Down (Slot 0, Port 1)", "23","Informational","Maintenance","06/10/2017 15:02","06/10/2017 15:02","1","Maintenance note: Intelligent Provisioning was loaded.", "22","Informational","Maintenance","06/10/2017 14:59","06/10/2017 14:59","1","Maintenance note: Intelligent Provisioning was loaded.", "21","Critical","Drive Array","06/10/2017 20:37","05/06/2017 23:42","5","Drive Array Controller Failure (Slot 1)", "20","Critical","Drive Array","06/10/2017 20:27","05/06/2017 23:32","5","External Storage Enclosure Device Failure (Bay 0, Box 0, Port , Slot 1)", "19","Critical","Drive Array","06/10/2017 20:22","05/06/2017 23:27","5","Internal Storage Enclosure Device Failure (Bay 0, Box 0, Port , Slot 1)", "18","Caution","POST Message","03/03/2017 14:17","03/03/2017 14:17","1","POST Error: 1785-Slot X Drive Array Not Configured", "17","Informational","Maintenance","03/02/2017 05:57","03/02/2017 05:57","1","Maintenance note: Intelligent Provisioning was loaded.", "16","Informational","Maintenance","03/02/2017 05:52","03/02/2017 05:52","1","Maintenance note: Intelligent Provisioning was loaded.", "15","Caution","POST Message","03/02/2017 05:31","03/02/2017 05:31","1","POST Error: 1726-Slot X Drive Array - Cache Memory Size or Battery Presence Has Changed - Cache Module configuration has automatically been updated.", "14","Caution","POST Message","03/02/2017 05:37","03/02/2017 05:31","2","POST Error: 1785-Slot X Drive Array Not Configured", "13","Informational","Maintenance","02/28/2017 08:50","02/28/2017 08:50","1","Maintenance note: Opt-in", "12","Informational","Maintenance","11/07/2015 03:50","11/07/2015 03:50","1","Maintenance note: Intelligent Provisioning was loaded.", "11","Informational","POST Message","06/12/2017 05:43","11/07/2015 03:36","70","POST Information: Processor 1, DIMM 2 could not be authenticated as genuine HP SmartMemory. Enhanced and extended HP SmartMemory features will not be active.", "10","Caution","POST Message","11/07/2015 03:28","11/07/2015 03:28","1","POST Error: 1785-Slot X Drive Array Not Configured", "9","Informational","Maintenance","11/07/2015 03:27","11/07/2015 03:27","1","IML Cleared (System Administrator)",
It's probably a faulty controller but I'd rather ask a professional. Thanks, Pepe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-13-2017 11:28 AM
тАО06-13-2017 11:28 AM
Re: HP Proliant Microserver gen8 - Celeron version
Updates: Done a full diagnostic test of the system and everything passed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2017 11:00 PM
тАО06-21-2017 11:00 PM
Re: HP Proliant Microserver gen8 - Celeron version
Got some new updates after the red flashing came again. The IML says "Uncorrectable Machine Check Exception (Board 0, Processor 1, APIC ID 0x00000000, Bank 0x00000003, Status 0xB2000000'00800400, Address 0x00000000'00000000, Misc 0x00000000'00000000)". This sounds like a faulty processor: http://h17007.www1.hpe.com/docs/enterprise/servers/gen9/tsg/246310.htm
I'll do a complete test in the HPIP but it has passed once everything it could.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2017 01:18 PM
тАО09-09-2017 01:18 PM
Re: HP Proliant Microserver gen8 - Celeron version
Hi guys,
Got some new updates. Changed the P410 SA Controller and currently with only a single disk/logical drive. It won't last 24 hours without the red flashing. I use it as an FTP server only so far and the data is fine and accessible. Updated the iLO and IP to the latest versions but it doesn't really matter I guess. It always starts red flashing when the sever is not in use.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2017 01:16 AM
тАО09-13-2017 01:16 AM
Re: HP Proliant Microserver gen8 - Celeron version
More updates! I have removed all the hard drives and connected one of them over USB. It took about an hour to start red flashing and Debian unmounted the usb drive in the process. It sounds like a server OS problem since the RAID controller is not even in use and still gives me a failure error.