RSS

Tag Archives: hp proliant

Redhat/SUSE kdump and HP cciss driver issue

Got this HP advisory Document ID: c02758009, though its Redhat related, thought it would be useful for someone out there.

SUPPORT COMMUNICATION – CUSTOMER ADVISORY
Document ID: c02758009

Version: 1

Advisory: HP Smart Array Controllers – CUSTOMER ACTION REQUIRED for Certain HP Smart Array Controllers to Ensure Pending Writes to Storage Devices Complete Properly if Attempting to Use the Linux Kdump Facility
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.

 Release Date: 2011-03-16

Last Updated: 2011-03-16

——————————————————————————–

DESCRIPTION
IMPORTANT : Pending writes to storage devices may not complete properly as detailed below if the kdump facility is used. Using the kdump facility could leave the server in an unstable condition, which could potentially result in an inconsistent filesystem state. By disregarding this notification, the customer accepts the risk of incurring potential related errors.

The Linux kdump facility fails to execute properly when used on HP ProLiant servers running Linux and configured with certain Smart Array controllers using certain versions of the cciss device drivers. Read the rest of this entry »

 
Leave a comment

Posted by on March 22, 2011 in Operations

 

Tags:

HP DL385 G7s and BL465 failures due to suspected AMD processor failures

You may see some of your HP DL385 G7s which powers off at their own accord or BL465 which crashes for no apparent reasons.

HP has recommendation to upgrade the BIOS and iLo firmware and also change some BIOS power settings but other HP customers have done this and continued to see the issues.

It is now suspected to be an issue with the AMD processors as the issue was not confined to HP servers only. HP and AMD is currently investigate as far as I am aware

 
Leave a comment

Posted by on December 9, 2010 in Operations

 

Tags:

ProLiant Server May Unexpectedly Reboot And Display Event ID 57 Error Messages

We have seen this case in a number of our Proliant servers since last year and have been fixing it as we see them. You may be interesting in this one too.

Advisory: (Revision) Integrated Lights-Out 2 (iLO 2) Firmware Version 1.81 (Or Earlier) And iLO 2 Management Controller Driver Version 1.11.1.0 (Or Earlier) – ProLiant Server May Unexpectedly Reboot And Display Event ID 57 Error Messages

Update: Tests in our environment has shown that despite the firmware and driver update from HP, we continue to see unexpected reboots. HP has agreed that this is an issue and will revert to us.

 
5 Comments

Posted by on May 11, 2010 in Windows

 

Tags:

HpCISSs2 event 129 hanging Windows server

I got a ticket post mortem on a HP proliant box running Windows server 2003. The report was that the server was unresponsive and had to be rebooted.

A quick check of the eventlog show a lot of warning event 129 from HpCISSs2 source. There is not much description on the event other than \Device\RaidPort0. So obviously this does not help. Read the rest of this entry »

 
8 Comments

Posted by on January 27, 2010 in Windows

 

Tags:

HP Proliant DL380 G6 BIOS issues causing reboots

Recently, we’v been building new DL380G6 and some of them would just reboot for no other reasons. This was finally traced to the BIOS issue for a certain batch of proliant servers. So if your server has a revision earlier than Rev 0S shipped prior to 16 Nov 2009 and server serial number prior to XXX947XXXX, where the 4th characther i the year code and 5th and 6th is the week code of manufacturer, you’ve got the problem.

The good part is that is solvable, the bad part is that the BIOS update needs to be manually done including unplugging the power physically.

Advisory: (Revision) HP ProLiant DL380 G6 Server – Limited Number of Servers Shipped Prior to November 16, 2009 (11/16/2009) and Configured with a System Board with Revision Level Earlier Than Rev 0S May Unexpectedly Reboot

A quick workaround is to change the BIOS profile to “Max Performance” from “Balanced Power and Performance” profile… but didn’t seem to help some of the servers.

 
2 Comments

Posted by on December 18, 2009 in Windows

 

Tags:

Using command line to configure HP Proliant arrays

One of the things we needed to do when deploying a server is that we need to setup the partitions correctly before we deploy it. Of course, we could always load up the smart start utility and perform the RAID configuration. But when you are doing remote deployment, that is, someone in London racked and powered up the server and you deploy it, it not always fun to load the ISO CD image, mostly because of the synchronization of the stupid mouse cursor over the WAN in some locations. And even in locations where the WAN is good, getting the cursor to go where you want to with the smart start it no fun. The other point is also it takes time for Smart Start to run.

So what we did was to include the command line equivalent of the array configuration called hpacucli.exe (you can download this from HP) into our deployment image. We can then launch this from the command prompt after its booted up in WinPE. Read the rest of this entry »

 
4 Comments

Posted by on October 17, 2009 in Windows, Windows CMD

 

Tags:

The iLO firmware is in a network flash recovery state

My team mate handed over an issue with the HP iLO on a DL380. When trying to browse to the iLO web page, he got the following error:

The iLO firmware is in a network flash recovery state.
Refer to the iLO network flash recovery under the trouble shooting section in the iLO users guide.

The first thing as recommended is to try pulling out the cables in the server and see it the iLO recovers. No such luck, which is why my team mate passed it on to me!

Anyway, did a quick search on the internet and found the solution. I am sure this can be found in the iLO troubleshooting manual, but if google did not find it, it must be hidden quite deep.

You can perform a flash recovery via FTP to the iLO (assuming you can still ping the iLO).

  1. Logon to the iLO via FTP
  2. Logon using the flash recovery  credentials
  3. put  the  iLO  bin
  4. iLO will  reset  (and  hopefully recover after that!)

Here is a sample  of what you might do:

 FTP 10.198.2.5

login: flash

password: recovery

put c:\temp\ilo189.bin

 
18 Comments

Posted by on July 17, 2007 in Windows

 

Tags: