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

megaclisas-status and Hotspare #31

Closed
Tuxdiver opened this issue Feb 11, 2016 · 5 comments
Closed

megaclisas-status and Hotspare #31

Tuxdiver opened this issue Feb 11, 2016 · 5 comments

Comments

@Tuxdiver
Copy link

Hi,

we have an unconfigured hotspare drive and megaclisas-status reports the RAID as not optimal.

This patch fixes it for me:

diff --git a/wrapper-scripts/megaclisas-status b/wrapper-scripts/megaclisas-status
index c212e03..891f6ba 100755
--- a/wrapper-scripts/megaclisas-status
+++ b/wrapper-scripts/megaclisas-status
@@ -756,7 +756,7 @@ if totalunconfdrivenumber:
                arraydisk = returnUnconfDiskInfo(output,controllerid)
                for array in arraydisk:
                        dbgprint('Disk c'+str(controllerid)+'uXpY status : ' + array[3])
-                       if array[3] not in [ 'Online', 'Unconfigured(good), Spun Up', 'JBOD' ]:
+                       if array[3] not in [ 'Online', 'Unconfigured(good), Spun Up', 'JBOD','Hotspare, Spun Up' ]:
                                bad = True
                                nagiosbaddisk=nagiosbaddisk+1
                        else:

Not sure, if it could be 'Hotspare' only...

Best regards,

Dirk

@Tuxdiver Tuxdiver changed the title megaclisas-status and Hostpare megaclisas-status and Hotspare Feb 11, 2016
@ElCoyote27
Copy link
Contributor

Hi Dirk,
Thanks for the patch. I've merged your patch into my repo. I'm going to issue a new PR for the main repo. Please test again when it's released.
Thanks,
Vincent

@fabianwenk
Copy link

Hello
I have the same situation, but in my case the hotspare was in spun down state shown as: 'Hotspare, Spun down'.
Eventually also adding this to the check could probably be helpful for others. In my case I changed the hotspare to be in spin up state with this (for adapter 0):
megacli -AdpSetProp -DsblSpinDownHSP -1 -a0
I think it is more useful to have the hotspare also in use (spinning) and be able so see when it fails, as it may not spin up when it would be needed for recovery.

bye
Fabian

@eLvErDe
Copy link
Owner

eLvErDe commented Feb 16, 2016

Hey,

I merged the big pull request from elcoyote including this one.
Also, I'll have Hotspare, Spun Down to the whitelist.

Regards, Adam.

@eLvErDe eLvErDe closed this as completed Feb 16, 2016
@ElCoyote27
Copy link
Contributor

Hey,
Thanks for the merge.
Just a thought: Are we sure if we should consider 'Hotspare, Spun Down' to be OK?
Thanks,
Vincent

@eLvErDe
Copy link
Owner

eLvErDe commented Feb 16, 2016

Hello,

Well it seems to be some kind of power saving feature. A friend also have the same behaviour on its RAID and the drive is definitely not broken, so yes, I guess…

Adam.

From: Vincent S. Cojot [mailto:notifications@github.com]
Sent: 16 February 2016 14:27
To: eLvErDe/hwraid hwraid@noreply.github.com
Cc: Adam Cécile gandalf@le-vert.net
Subject: Re: [hwraid] megaclisas-status and Hotspare (#31)

Hey,
Thanks for the merge.
Just a thought: Are we sure if we should consider 'Hotspare, Spun Down' to be OK?
Thanks,
Vincent


Reply to this email directly or view it on GitHub #31 (comment) . https://github.com/notifications/beacon/ABg2RYTrezwX0oGvo6_p0KQCRsPP3a6jks5pkxsMgaJpZM4HX9aE.gif

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants