- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- HP Proliant Microserver Gen 8 booting to GRUB
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
08-05-2019 12:23 AM
08-05-2019 12:23 AM
HP Proliant Microserver Gen 8 booting to GRUB
The other day the machine started flashing red on the front (HP Proliant Microserver GEN8) so i rebooted the machine and it now starts up into Grub.
On the bootup i'm seeing the standard BIOS and then it says the boot drive is missing, so i try and login to IP to resolve it but it fails and jumps to GRUB.
I've logged into the iLOv4 firmware version 2.55, search HPE and found two revisions, but both attempts to install this via the Web Console fail. I'm unable to access the machine via SSH or SFTP into it to load and run the firmware, so i'm pretty stuck. Any help would be appreciated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2019 01:36 AM
08-05-2019 01:36 AM
Re: HP Proliant Microserver Gen 8 booting to GRUB
After a lot of messing about i've made some progress, i downloaded the windows update and used 7zip to extract the BIN from it, then updated the firmware to 2.70.
Performed a NAND reset using the untilty from the HP site and rebooted the machine. IP still didn't work, so i've downloaded the ISO and installed it to a 16GB USB (tried my 32GB but it wouldn't accept it, probably too big).
Ran the HP Boot untitly and created a boot USB, and started the server with this. Re-installed IP this got the IP back for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2019 04:50 AM
08-05-2019 04:50 AM
Re: HP Proliant Microserver Gen 8 booting to GRUB
I've not got it booting and installing Centos from a USB stick however i can't get the server to load afterwards. Anyone got any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2019 06:38 AM
08-05-2019 06:38 AM
Re: HP Proliant Microserver Gen 8 booting to GRUB
@Solidblueliquid wrote:The other day the machine started flashing red on the front (HP Proliant Microserver GEN8) so i rebooted the machine and it now starts up into Grub.
On the bootup i'm seeing the standard BIOS and then it says the boot drive is missing, so i try and login to IP to resolve it but it fails and jumps to GRUB.
I've logged into the iLOv4 firmware version 2.55, search HPE and found two revisions, but both attempts to install this via the Web Console fail. I'm unable to access the machine via SSH or SFTP into it to load and run the firmware, so i'm pretty stuck. Any help would be appreciated
Sounds like the boot disk has failed. Not being able to access IP is a seperate issue