- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- BIOS POST boot time
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
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
01-15-2015 02:10 AM
01-15-2015 02:10 AM
BIOS POST boot time
Hello
Is there any way to speed up POST boot time? It takes Minutes till the Server begins booting the OS. This is very very annoying especially when you are testing e.g. Auto Deploy (boot many times).
regards,
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2015 03:11 AM - edited 01-15-2015 04:16 AM
01-15-2015 03:11 AM - edited 01-15-2015 04:16 AM
Re: BIOS POST boot time
You did not say what server you have. But usually you can't. Maybe you can remove some memory or I/O cards that you don't need for your testing to reduce the test and scan time. As an example, for the new SuperDome X POST takes up to one hour because of the 12 TB memory ...
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
01-20-2015 08:03 AM
01-20-2015 08:03 AM
Re: BIOS POST boot time
Like Torsten said, the BIOS POST time depends on what system you have, what options are installed, how much memory, etc.
There might be a few things you could tweak, but it's already just doing a quick memory test unless it detects a change in how much memory is installed. The other things that normally happen in a Proliant during boot is when all of the option "cards" do their thing, like the array controller, ILO, and maybe the NIC module.
All of those things have to show something during boot so you can hit a key and configure them, so it's really just something that has to be there.
I guess whether it takes 30 seconds or 5 minutes, it's one of those things that server admins have probably learned to deal with over the years. I know I have. :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2015 05:33 AM - edited 01-21-2015 05:38 AM
01-21-2015 05:33 AM - edited 01-21-2015 05:38 AM
Re: BIOS POST boot time
I have a HP Proliant DL380 G9 Server.
No Disks, No Raid Controller, but 2x 10GBit PCIe. 256GB RAM, 2x 2690v3 CPU's.
Btw. its not for Production Site, because starttime does not matter there. It only matters during Testing/Trying on a Development Site. So maybe there are some unsafe options, which could be enabled but are not recommended for production?