<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: check_megaraid_sas Nagios plugin</title>
	<atom:link href="http://www.techno-obscura.com/~delgado/blog/2007/06/check_megaraid_sas-nagios-plugin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techno-obscura.com/~delgado/blog/2007/06/check_megaraid_sas-nagios-plugin/</link>
	<description>Jonathan&#039;s periodic postings of varying importance</description>
	<lastBuildDate>Wed, 18 Jan 2012 03:14:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Brian</title>
		<link>http://www.techno-obscura.com/~delgado/blog/2007/06/check_megaraid_sas-nagios-plugin/comment-page-1/#comment-2405</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Wed, 18 Jan 2012 03:14:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.techno-obscura.com/~delgado/blog/?p=14#comment-2405</guid>
		<description>Thanks for the plug in and this post, I just discovered that I have 15 &quot;other errors&quot; on one of my drives. 

I&#039;ll try contacting LSI tomorrow and see if I can squeeze any info out of them.  I&#039;ll also try powering down the server and changing out the cable in hopes of removing the errors.</description>
		<content:encoded><![CDATA[<p>Thanks for the plug in and this post, I just discovered that I have 15 &#8220;other errors&#8221; on one of my drives. </p>
<p>I&#8217;ll try contacting LSI tomorrow and see if I can squeeze any info out of them.  I&#8217;ll also try powering down the server and changing out the cable in hopes of removing the errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Delgado</title>
		<link>http://www.techno-obscura.com/~delgado/blog/2007/06/check_megaraid_sas-nagios-plugin/comment-page-1/#comment-2404</link>
		<dc:creator>Jonathan Delgado</dc:creator>
		<pubDate>Wed, 04 Jan 2012 00:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.techno-obscura.com/~delgado/blog/?p=14#comment-2404</guid>
		<description>Figuring out what the &quot;Other&quot; errors were never really ended up being much of a priority for me. The ones I see seem to indicate communications issues between the controller and the drive. They do seem to get reset at times, but I have not seen a way to directly reset the count via MegaCli or anything else without a reboot of the system.

I am also not sure what is a reasonable number for media errors. I have only seen a few drives where the media error has gone over a dozen, and in those cases the error count was low (or zero) and then exploded with the drive failing shortly thereafter. I don&#039;t know if once the media error count hits a certain number the predictive failure flag is set, or is it really a drive-specific parameter. Media errors are, to an extent, to be expected and the drive should be invisible recovering from them up to a point. Are the ones being count unrecoverable errors or revoverable ones?

I don&#039;t think the LSI is really providing any documentation on what these error types mean and how they ought to be interpreted.</description>
		<content:encoded><![CDATA[<p>Figuring out what the &#8220;Other&#8221; errors were never really ended up being much of a priority for me. The ones I see seem to indicate communications issues between the controller and the drive. They do seem to get reset at times, but I have not seen a way to directly reset the count via MegaCli or anything else without a reboot of the system.</p>
<p>I am also not sure what is a reasonable number for media errors. I have only seen a few drives where the media error has gone over a dozen, and in those cases the error count was low (or zero) and then exploded with the drive failing shortly thereafter. I don&#8217;t know if once the media error count hits a certain number the predictive failure flag is set, or is it really a drive-specific parameter. Media errors are, to an extent, to be expected and the drive should be invisible recovering from them up to a point. Are the ones being count unrecoverable errors or revoverable ones?</p>
<p>I don&#8217;t think the LSI is really providing any documentation on what these error types mean and how they ought to be interpreted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Whit</title>
		<link>http://www.techno-obscura.com/~delgado/blog/2007/06/check_megaraid_sas-nagios-plugin/comment-page-1/#comment-2403</link>
		<dc:creator>Whit</dc:creator>
		<pubDate>Tue, 03 Jan 2012 21:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.techno-obscura.com/~delgado/blog/?p=14#comment-2403</guid>
		<description>Thanks for a useful plugin!

Did you ever learn more about what &quot;other&quot; errors are? I find mentioned elsewhere a suggestion that they often come from cable problems. But does anyone know a definition? Are they cumulative? Is there a way to reset them? 

Also, what&#039;s a reasonable number to ignore for media errors? I see in an older LSI doc that at least some of their controllers fail a drive at 32 media errors. I see in another doc advice to replace a drive with even a single media error.</description>
		<content:encoded><![CDATA[<p>Thanks for a useful plugin!</p>
<p>Did you ever learn more about what &#8220;other&#8221; errors are? I find mentioned elsewhere a suggestion that they often come from cable problems. But does anyone know a definition? Are they cumulative? Is there a way to reset them? </p>
<p>Also, what&#8217;s a reasonable number to ignore for media errors? I see in an older LSI doc that at least some of their controllers fail a drive at 32 media errors. I see in another doc advice to replace a drive with even a single media error.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Magnus369</title>
		<link>http://www.techno-obscura.com/~delgado/blog/2007/06/check_megaraid_sas-nagios-plugin/comment-page-1/#comment-2399</link>
		<dc:creator>Magnus369</dc:creator>
		<pubDate>Thu, 20 Oct 2011 08:39:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.techno-obscura.com/~delgado/blog/?p=14#comment-2399</guid>
		<description>Hi, just found your plugin recently and started testing it on one of my systems, when I found a small gotcha- apparently MegaCli under vmware as of version 8.02.16 has a small change that puts the word &quot;Size&quot; in the ldinfo output several times, ie:

Adapter 0 -- Virtual Drive Information:
Virtual Drive: 0 (Target Id: 0)
Name                :
RAID Level          : Primary-5, Secondary-0, RAID Level Qualifier-3
Size                : 271.899 GB
Parity Size         : 135.949 GB
State               : Optimal
Strip Size          : 64 KB
Number Of Drives    : 3
Span Depth          : 1
Default Cache Policy: WriteThrough, ReadAhead, Cached, No Write Cache if Bad BBU
Current Cache Policy: WriteThrough, ReadAhead, Cached, No Write Cache if Bad BBU
Default Access Policy: Read/Write
Current Access Policy: Read/Write
Disk Cache Policy   : Enabled
Encryption Type     : None
Is VD Cached: No

which was creating the output of:

OK: 0:0:RAID-5:3 drives:135.949GB:Optimal 0:1:RAID-1:2 drives:135.899GB:Optimal 0:2:RAID-1:2 drives:0GB:Optimal 0:3:RAID-5:3 drives:135.949GB:Optimal 0:4:RAID-5:3 drives:0GB:Optimal 0:5:RAID-5:8 drives:0GB:Optimal Drives:24 Hotspare(s):3

(yes, I have several disks, and I didn&#039;t feel like putting out all the listing)

You can see that the first virtual disk isn&#039;t correct, it should read 271.899GB, however the script output shows 135.949GB. it gets worse later, as disk sizes of 0 show up.

on line 144, change 

if ( m/Size\s*:\s*((\d+\.?\d*)\s*(MB&#124;GB&#124;TB))/ ) {

to 

if ( m/^Size\s*:\s*((\d+\.?\d*)\s*(MB&#124;GB&#124;TB))/ ) {


rerun script and get

OK: 0:0:RAID-5:3 drives:271.899GB:Optimal 0:1:RAID-1:2 drives:135.899GB:Optimal 0:2:RAID-1:2 drives:135.899GB:Optimal 0:3:RAID-5:3 drives:271.899GB:Optimal 0:4:RAID-5:3 drives:271.898GB:Optimal 0:5:RAID-5:8 drives:951.794GB:Optimal Drives:24 Hotspare(s):3


Thanks again for the great script, and sorry for the huge text wall!</description>
		<content:encoded><![CDATA[<p>Hi, just found your plugin recently and started testing it on one of my systems, when I found a small gotcha- apparently MegaCli under vmware as of version 8.02.16 has a small change that puts the word &#8220;Size&#8221; in the ldinfo output several times, ie:</p>
<p>Adapter 0 &#8212; Virtual Drive Information:<br />
Virtual Drive: 0 (Target Id: 0)<br />
Name                :<br />
RAID Level          : Primary-5, Secondary-0, RAID Level Qualifier-3<br />
Size                : 271.899 GB<br />
Parity Size         : 135.949 GB<br />
State               : Optimal<br />
Strip Size          : 64 KB<br />
Number Of Drives    : 3<br />
Span Depth          : 1<br />
Default Cache Policy: WriteThrough, ReadAhead, Cached, No Write Cache if Bad BBU<br />
Current Cache Policy: WriteThrough, ReadAhead, Cached, No Write Cache if Bad BBU<br />
Default Access Policy: Read/Write<br />
Current Access Policy: Read/Write<br />
Disk Cache Policy   : Enabled<br />
Encryption Type     : None<br />
Is VD Cached: No</p>
<p>which was creating the output of:</p>
<p>OK: 0:0:RAID-5:3 drives:135.949GB:Optimal 0:1:RAID-1:2 drives:135.899GB:Optimal 0:2:RAID-1:2 drives:0GB:Optimal 0:3:RAID-5:3 drives:135.949GB:Optimal 0:4:RAID-5:3 drives:0GB:Optimal 0:5:RAID-5:8 drives:0GB:Optimal Drives:24 Hotspare(s):3</p>
<p>(yes, I have several disks, and I didn&#8217;t feel like putting out all the listing)</p>
<p>You can see that the first virtual disk isn&#8217;t correct, it should read 271.899GB, however the script output shows 135.949GB. it gets worse later, as disk sizes of 0 show up.</p>
<p>on line 144, change </p>
<p>if ( m/Size\s*:\s*((\d+\.?\d*)\s*(MB|GB|TB))/ ) {</p>
<p>to </p>
<p>if ( m/^Size\s*:\s*((\d+\.?\d*)\s*(MB|GB|TB))/ ) {</p>
<p>rerun script and get</p>
<p>OK: 0:0:RAID-5:3 drives:271.899GB:Optimal 0:1:RAID-1:2 drives:135.899GB:Optimal 0:2:RAID-1:2 drives:135.899GB:Optimal 0:3:RAID-5:3 drives:271.899GB:Optimal 0:4:RAID-5:3 drives:271.898GB:Optimal 0:5:RAID-5:8 drives:951.794GB:Optimal Drives:24 Hotspare(s):3</p>
<p>Thanks again for the great script, and sorry for the huge text wall!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.techno-obscura.com/~delgado/blog/2007/06/check_megaraid_sas-nagios-plugin/comment-page-1/#comment-2398</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Mon, 26 Sep 2011 14:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.techno-obscura.com/~delgado/blog/?p=14#comment-2398</guid>
		<description>Hi,

We recently replaced a drive in our RAID array and about 2 weeks later I got a message similar to what you state in your description above:  

WARNING: 0:0:RAID-5:4 drives:1394GB:Optimal Drives:4 (4 Errors)

What I am wondering is if those errors are listed out somewhere so I can see if it is something I need to address or not?

Thanks for a great plugin!
Ben</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>We recently replaced a drive in our RAID array and about 2 weeks later I got a message similar to what you state in your description above:  </p>
<p>WARNING: 0:0:RAID-5:4 drives:1394GB:Optimal Drives:4 (4 Errors)</p>
<p>What I am wondering is if those errors are listed out somewhere so I can see if it is something I need to address or not?</p>
<p>Thanks for a great plugin!<br />
Ben</p>
]]></content:encoded>
	</item>
</channel>
</rss>

