Red Hat Bugzilla – Bug 169119
No RAID status info from the cciss raid driver
Last modified: 2007-11-30 17:07:20 EST
The hardware RAID system in our HP ProLiant DL385 uses the cciss linux driver.
To be able to safely use our RAID system and detect when disks fail, we need to
extract the current RAID status and pass it on into our monitoring system.
But we have not been able to find the current status of the RAID system with
the information provided by the driver. /proc/driver/cciss/cciss0 contain some
information, but no about the state of the RAID.
We would prefer some text file in /proc/ or /sys/ we could look at
every 5 minutes to check the status.
We are aware of the cpqarrayd server, capable of passing RAID events into the
syslog, but this do not cover our needs, as it will not report the current
I'm setting severity to high, as the lack of status information make the
hardware raid dangerous to use.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time. This request will be
reviewed for a future Red Hat Enterprise Linux release.
The HP Array Configuration Utility may do what you are looking for. See, for
Mike, does that allow one to monitor the current status of the RAID system? Ant
Yes, you can use the array config utility to report the status of logical
volumes. Some customers use the hpacucli to do this, but we don't recommend
that. The HP agents are the preferred method of reporting the status of the
With that said we also have a lightweight utility to report status. It's called
cciss_vol_status and is available at
We have discussed doing some of this in the driver, either in /proc or /sys. But
that's a future enhancement.
I'll close this now. Petter, re-open as a future feature request if this is not