- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: HP Proliant ML110 G6 Boot Failed
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
12-09-2011 07:46 AM
12-09-2011 07:46 AM
HP Proliant ML110 G6 Boot Failed
Hello,
I have HP Proliant ML110 G6 server with following RAID configuration:
1st RAID - 1 disk in Raid 0 (just a logical drive to make the system to see it)
2nd RAID - 2 disks in Raid 1+0
When I install Windows 7 on the 2nd RAID and it goes to restart first time - it doesn't boot from HDD - "Boot Failed".
What Can I do?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2011 12:33 AM
12-11-2011 12:33 AM
Re: HP Proliant ML110 G6 Boot Failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2011 03:27 AM
12-11-2011 03:27 AM
Re: HP Proliant ML110 G6 Boot Failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2011 11:19 PM
12-11-2011 11:19 PM
Re: HP Proliant ML110 G6 Boot Failed
Windows 7 is not supported on ML110 G6.
But I would suggest you to check/change Boot Order in BIOS.
Boot Settings Configuration:
Standard Boot Order:
I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2014 04:35 PM
09-13-2014 04:35 PM
Re: HP Proliant ML110 G6 Boot Failed
I just had the same issue. I obtained this old server from a business who's IT guy couldn't get the server to stay up. The following worked for me.
The HP Proliant ML110 G6 has the capability for SATA RAID. So if there was a failed drive, the RAID is trying to restore/rebuild it.
Go inside the case and look at the diagram to make sure the drives & cables are installed in accordance with the diagram. Then reset the BIOS by moving switch 1 down to the on position - all other switches should be up. Power up/down & move the swtich back to the up / off position.
Go into BIOS and tell it to use SATA RAID mode. Reboot & go into the RAID configuration mode (F8). If you don't need anything on the HDD you can delete the array. Build a new array and then reinstall the operating system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2016 05:30 AM
01-14-2016 05:30 AM
Re: HP Proliant ML110 G6 Boot Failed
I had same symptoms on same hardware with similar configuration. In my case a Windows update somehow managed to change the disk boot order in BIOS. I simply corrected it in BIOS, and problem solved!