VMware Cloud Community
vmvn01
Contributor
Contributor

Host Storage Status Alarm

Hello,
We are using the following versions:
- VCenter Server version 5.5.0 build 1,750,787
- VSphere client version 5.5.0 build 1,474,107
- ESXi version 5.5.0 build 1,623,387

Currently we are facing with the 5 hosts simultaneously appear on the Host Storage Status critical alarm. When checking the Hardware Status tab from vSphere client alarm appears as follows:

Disk 1 on HPSA1: Bay Port 0 Box 0: 0GB: Unconfigured Disk: Disk Error.
Sensor name: Disk 2 on HPSA1: Bay Port 0 Box 0: 0GB: Unconfigured Disk: Disk Error.

All the physical servers are C7000 HP Blades

Please guide us to check and fix this issue.
Thank you. /.

10 Replies
nnnnnng
Enthusiast
Enthusiast

Hi Everyone,

We have the same issue ! (DL580 G7, ESXi and vCenter version is the same)

current workaround is .... Migrate all VM to other host,

and reboot ESXi host.

Does any other workaround or FIX here?

Reply
0 Kudos
KeithBachmanTP
Contributor
Contributor

I also had this trigger on a host - HP DL120 G7 (Not on the HAL, I know).

DL120 G7:

System ROM J01 02/01/2012

iLO 3 Advanced, 1.70 Jan 09 2014

Drive Backplane Firmware v1.14

vCSA 5.5.0 U1 (5.5.0.10100 Build 1750781)

vSphere 5.5.0 U1 (build 1881737)

Its twin so far has no issue.

The error seems to talk about a Bay/Port that doesn't exist.

A reboot of the affected host also cleared it up for me.

I'll be applying SPP 2014.06 to it in the next day or two, in case it is something with an older firmware version that is causing it.

Reply
0 Kudos
vmvn01
Contributor
Contributor

Hello,
I tried implementing virtual machines migrate to other hosts and rebooted the alarm ESX host, but still did not to fix. Even now, upto 17 ESX hosts are having this alarm.
Had anyone ever been like this and fixed the errors, please help.
Thank you

Reply
0 Kudos
warring
Enthusiast
Enthusiast

Check Bios of host if the error can be cleared from that level.

VCP510-DCV
Reply
0 Kudos
KeithBachmanTP
Contributor
Contributor

Now also triggered on a pair of blades:

BL460c G7

HP SPP 2014.02.0-B

ESXi 5.5.0, Build 1881737

EDIT: Now that it has happened on supported hardware, I've filed a case with VMware Support over it, and referenced this discussion.

EDIT EDIT: VMware Support said to contact HP over it, as all vSphere does is report what the sensors report.

I also now have a third BL460c G7 with this issue.  Reboot still clears it.

Reply
0 Kudos
vmvn01
Contributor
Contributor

Hello,
I am also actively looking for information about similar errors like this, and now I'm thinking about the old firmware SmartArray reasonable?

Who is there a way to check the firmware version information of the Ethernet NIC card and SmartArray not?

Reply
0 Kudos
JimKnopf99
Commander
Commander

Hi,

here is the way how to check firmware.

VMware KB: Determining Network/Storage firmware and driver version in ESXi/ESX 4.x and ESXi 5.x

Frank

If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
FritzBrause
Enthusiast
Enthusiast

There are some issues with the hpsa driver 5.x.0.58-1.

You can check your logs if you find some of those lines:

WARNING: LinDMA: dma_alloc_coherent:726: Out of memory

hpsa 0000:03:00.0: cmd_special_alloc returned NULL!

hpsa 0000:03:00.0: out of memory at vmkdrivers/src_9/drivers/hpsa/hpsa.c:3562

cp 0x410c0b9e8500 has status 0x2 Sense: 0x5, ASC: 0x20, ASCQ: 0x0, Returning result: 0x2


You can check which hpsa driver is installed by running this command:

# esxcli software vib list | grep -ir hpsa

Upgrade the driver to 5.x.0.60-1.

http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/topIssuesDisplay?javax.portlet.b...

Reply
0 Kudos
vmvn01
Contributor
Contributor

Hi Fritz

Can you show me about the logfile location to check? Seemly, our problems related to driver version as your said.

Thanks./.

Reply
0 Kudos
bdonders
Contributor
Contributor

Hi,

Thanks for sharing... We encountered the same problems...

I upgraded the vib and we will wait if the error will show again...


Regards,

Bart

Reply
0 Kudos