Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring Dell PERC Arrays Health #361

Closed
gadago opened this issue Dec 5, 2014 · 2 comments
Closed

Monitoring Dell PERC Arrays Health #361

gadago opened this issue Dec 5, 2014 · 2 comments
Labels

Comments

@gadago
Copy link

gadago commented Dec 5, 2014

Hi,

This is a feature request to have the ability to monitor the health of arrays on Dell PERC/LSI controllers.

I believe the sensor data can be obtained from Dell OpenManage/IPMI.

In particular, it would be great if this could be supported on Dell 11th and 12th generation server with PERC H200 or H700 controller or newer.

Thanks,

@laf
Copy link
Member

laf commented Dec 8, 2014

If anyone fancies a crack at this we have Dell kit which we can provide access to.

@laf
Copy link
Member

laf commented May 19, 2015

Hopefully PR referenced above will provide this. It uses virtualDiskState which uses this for values:

The current condition of this virtual disk
(which includes any member array disks.)
Possible states:
0:Unknown
1:Ready - The disk is accessible and has no known problems.
2:Failed - Access has been lost to the data or is about to be lost.
3:Online
4:Offline - The disk is not accessible. The disk may be corrupted or intermittently unavailable.
6:Degraded - The data on the virtual disk is no longer fault tolerant because one of the underlying disks is not online.
15:Resynching
16:Regenerating
24:Rebuilding
26:Formatting
32:Reconstructing
35:Initializing
36:Background Initialization
38:Resynching Paused
52:Permanently Degraded
54:Degraded Redundancy

Once this is merged, if it doesn't fix provide what you need then please feel free to re-open this and provide more info.

@laf laf closed this as completed May 19, 2015
@lock lock bot locked as resolved and limited conversation to collaborators May 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants