- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ML350e Gen8 v2 - Server won't boot , red internal ...
-
-
Forums
- Products
- Servers and Operating Systems
- Storage
- Software
- Services
- HPE GreenLake
- Company
- Events
- Webinars
- Partner Solutions and Certifications
- Local Language
- China - 简体中文
- Japan - 日本語
- Korea - 한국어
- Taiwan - 繁體中文
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Blog, Poland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
05-20-2019 03:25 AM - edited 05-20-2019 03:36 AM
05-20-2019 03:25 AM - edited 05-20-2019 03:36 AM
ML350e Gen8 v2 - Server won't boot , red internal led flashing - could't find meaning in docs
Hi eveybody and thanks for the time you may spend reading my problem! Here I go:
Proliant ML350e Gen8 v2, with Windows Server2016, just changed it's phisical location and it doess't boot - can't even enter in BIOS - no POST screen shown.
Everything seems normal, except an internal red light blinking and no signal on screen. All front indicator are fine. I attach a picture showing red led location on motherboard.
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-21-2019 01:23 AM
05-21-2019 01:23 AM
Re: ML350e Gen8 v2 - Server won't boot , red internal led flashing - could't find meaning in docs
Hi, Good Day,
I would recommend the following plan of action if there is at least fan activity:
1. Power on the server within a minimal configuration (no parts replaced yet) and allow the server to complete POST. Please confirm the minimal configuration is only consisting of:
- System board
- 1x CPU (test both the CPUs in slot 1)
- 1x DIMM installed in slot 1A dedicated to CPU1 (please reseat the DIMM and test another memory module as well))
- 1x PSU
- No network cards installed, No PCI cards, no riser boards, without the Smart Array controller, No HDD backplanes, power cables and hard drives attached to the system board, etc.
2. If the POST is successfully completed – start adding the removed components one by one - else continue with the next step.
3. Perform “NVRAM clear”.
When the system maintenance switch position 6 is set to the On position, the system is prepared to erase all system configuration settings from both CMOS and NVRAM.
CAUTION: Clearing CMOS and/or NVRAM deletes configuration information. Be sure to properly configure the server or data loss could occur!
4. If the issue persist remove the CMOS battery.
5. Perform a short circuit on the terminals of the already removed CMOS battery for at least 60 seconds.
6. Put the CMOS battery back.
7. Once the above steps are performed and if the issue persist - collect AHS report and open a support case.

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2022 Hewlett Packard Enterprise Development LP