Michael Posted February 20, 2017 Posted February 20, 2017 Hi all, I have a HP Gen9 server setup using HP's Intelligent Provisioning, running Server 2016. Sometimes (but not always) the server gets 'stuck' on the Windows Boot Loader between Windows Server 2016 (default) and Win PE or RAM Disk Options as it's listed as (see illustration): Any idea(s) why the server sometimes gets stuck on the Boot Loader? And what is the RAM Disk Option or Windows PE boot option required for? When it gets stuck, I have to hold down Escape and then eventually it takes me to the UEFI BIOS whereby I can boot Server 2016 as normal. Not seen this behaviour before and Googling the issue is revealing little results, hence me posting here. Thanks!
Tefters Posted February 21, 2017 Posted February 21, 2017 Hi all, I have a HP Gen9 server setup using HP's Intelligent Provisioning, running Server 2016. Sometimes (but not always) the server gets 'stuck' on the Windows Boot Loader between Windows Server 2016 (default) and Win PE or RAM Disk Options as it's listed as (see illustration): [ATTACH=CONFIG]41668[/ATTACH] Any idea(s) why the server sometimes gets stuck on the Boot Loader? And what is the RAM Disk Option or Windows PE boot option required for? When it gets stuck, I have to hold down Escape and then eventually it takes me to the UEFI BIOS whereby I can boot Server 2016 as normal. Not seen this behaviour before and Googling the issue is revealing little results, hence me posting here. Thanks! The Windows PE option is for the Windows recovery options, you can simply disable it via a command line. I do so on all my desktop machines to stop the kids booting into recovery options and doing all sorts of crap, never had to do it on a server but it is simple enough. Will dig out the code from my task sequence when in the office as you need to run a command in order to get the boot guid ID which I can't remember right now off the top of my head.
Tefters Posted February 21, 2017 Posted February 21, 2017 bcdedit /set {default} bootstatuspolicy ignoreallfailures bcdedit /set {default} recoveryenabled No bcdedit /set {default} winpe no Those are the 3 commands you want, will disable WinPE, Recovery Mode and ignore any boot failures which cause that menu to appear on reboot. 1
Michael Posted February 21, 2017 Author Posted February 21, 2017 bcdedit /set {default} bootstatuspolicy ignoreallfailures bcdedit /set {default} recoveryenabled No bcdedit /set {default} winpe no Those are the 3 commands you want, will disable WinPE, Recovery Mode and ignore any boot failures which cause that menu to appear on reboot. Thanks for this, but I didn't require it in the end. For some unknown reason, it's the KVM that affects all HP Servers in the same way, but not older Servers. It's not the keyboard or mouse, as unplugging these from the KVM still displays the problem. When completely disconnecting the USB cable from KVM > Server, the problem goes away. It's not a massive problem as I can now manage Servers using iLO (Integrated Lights Out), but still, somewhat of a mystery.
Tefters Posted February 21, 2017 Posted February 21, 2017 Good old fashioned 15" monitor with long vga and USB keyboard is how I manage my boxes physically when I can't iLo which is the obvious first go to. Never bothered to invest in a KVM out of laziness and cost. Glad you found the route cause.
Michael Posted February 22, 2017 Author Posted February 22, 2017 It's one of these that's the issue. HP iLO firmware is up-to-date (version 2.50) and not sure if the firmware on this unit is even upgradeable!
Tefters Posted February 22, 2017 Posted February 22, 2017 £600!!!!!! That's why I stick with my £20 monitor, £5 keyboard and mouse and £3 long VGA cable
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now