BladeSystem - General
Showing results for 
Search instead for 
Did you mean: 

BL460c G7 hang on reboot

Occasional Visitor

BL460c G7 hang on reboot



i have a problem with several HP Blades. I have 2 Enclosures Domains, everyone with 4 C7000 (OA 3.21; VC 3.15) complete full with BL460c G7. When we do our monthly reboot for MS Patchday, then a few Blades hang on rebooting. System shuts down but will not restart. When we open a console you only see a black screen. Now we have to do an ILO reset an turn the Balde on again it will start. After the System is up again it works fine. If we do another reboot it also works. But after ~4 weeks we have the same problem again. The Blades have ROM Version I27 and ILO3 Firmware Version 1.26. Enclosure Dynamic Power Cap is not enabled.


Has anyone an idea or solution for this problem.



Re: BL460c G7 hang on reboot



The BIOS ROM ‘I27’ denotes the BIOS family. The version date is of significance. The latest BIOS version dated 2011.05.05 contains a fix the following fix among others:


‘Resolved an issue that may result in any of the following conditions: operating system stops responding, unexpected system reset, Blue Screen when using a Microsoft Windows operating system, kernel panic when using a Linux operating system, or Purple Screen when using VMware ESX.’


If BIOS is not updated to this version already, them it may be downloaded and installed from the following link:



If BIOS is already at this version, then logs extracted from the server needs to analyzed to further isolate the issue. Please gather the following logs and contact HP at:


a. Active Chat Support:





b. HP Support Center:




c. Contact HP:




The following logs that may be required for analysis:


a. The HPS report generated from the server by downloading and executing the utility from the following link:


32 bit:



64 bit:



b. The Integrated Management Logs from the server by logging to the server’s iLO, click ‘Information’ at the left hand side and then click ‘Integrated Management Log’. Export it or copy them and save in notepad.


c. The HP Insight Diagnostics Offline Survey file generated from the server in the following manner:


          1. Connect an USB drive, up to 2GB capacity, formatted with FAT32 file system to the server.


          2. Boot from the Smart Start CD/image.


          3. Select language as English (US) and keyboard layout as US English and click ‘Next’.


          4. Agree to EULA.


          5. Click Maintenance and then click on HP Insight Diagnostics.


          6. Click tab Survey. Set Category to ‘All’ and View level to ‘Advanced’, click button 'Save Report' to save the report to the USB key.


You may download the latest version of the SmartStart disk image from the following link:






I work for HPE
Views expressed herein are my personal opinion and is not the views of HPE

Accept or Kudo

Respected Contributor

Re: BL460c G7 hang on reboot

I don't think that'll fix this issue as Ulf had that as his version last November and was still seeing it:


I have 01/29/2011 installed and am seeing the issue (iLO is at 1.20).  My OA is at 3.32 and VC is 3.30.  So this appears to be a problem that hasn't been corrected yet.

New Member

Re: BL460c G7 hang on reboot

We're having the same issue with our 460 G7 blades. We have a Citrix farm that we automatically reboot every week and at least 2 of the servers don't come back up after a reboot. The ILO shows them as powered on, Green light at the bottom, but the screen is black. The only solution is to power cycle them. Today I have rebooted a G7 as part of a patching routine and it didn't come back up - had to go onto the ILO, shows as powered on but with a black scree, had to power cycle.


HP have changed out a system board but it made no difference - all BIOS firmware is 05.05.2011 as per the HP web site.


We've had this issue since we bought the servers. Each time we contact HP we go through the same process of checking firmware and generating log files. There is a problem with these servers that HP is not fixing and doesn't appear in the logs