From owner-freebsd-hardware@FreeBSD.ORG  Fri Oct  8 19:04:36 2004
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6FA8B16A4CE
	for <hardware@freebsd.org>; Fri,  8 Oct 2004 19:04:36 +0000 (GMT)
Received: from error404.nls.net (error404.nls.net [216.144.36.24])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0CA3743D46
	for <hardware@freebsd.org>; Fri,  8 Oct 2004 19:04:36 +0000 (GMT)
	(envelope-from ketrien@error404.nls.net)
Received: from [192.168.0.100] (eiterra.achedra.org [192.168.0.100])
	by error404.nls.net (8.12.10/8.12.10) with ESMTP id i98J4YqP041021;
	Fri, 8 Oct 2004 15:04:34 -0400 (EDT)
	(envelope-from ketrien@error404.nls.net)
Message-ID: <4166E4BE.2060402@error404.nls.net>
Date: Fri, 08 Oct 2004 15:04:30 -0400
From: "Ketrien I. Saihr-Kesenchedra" <ketrien@error404.nls.net>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Simon <simon@optinet.com>, hardware@freebsd.org
References: <20041008170717.2728D43D39@mx1.FreeBSD.org>
In-Reply-To: <20041008170717.2728D43D39@mx1.FreeBSD.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Monitoring LSI MegaRAID 320-1
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: General discussion of FreeBSD hardware
	<freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>,
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Oct 2004 19:04:36 -0000

Simon wrote:

>Hello Folks!
>
>I have several servers with LSI MegaRAID 320-1 controllers. What do
>you all use to monitor the arrays? how is one supposed to know when
>a drive dies, remotely? I found a utility MegaControl which does exactly
>this, but it is buggy and causes my servers to malfunction and start
>panicing left and right. I noticed that the array would be reinitialized in background after installing MegaControl which made no sense since the array was already %100 initialized. This would of course corrupt the live system and was probably the cause of panics.
>
>Any insights on this would be appreciated!
>
amr(4) provides a cam passthrough function, which exposes the individual 
drives cleanly. (I've tested this on 320-2 and 320-0.) I'd use 
camcontrol rather than megacontrol, but bear in mind that, AFAIK, 
camcontrol cannot tell you the array status, only individual drive status.

-Ketrien I. Saihr-Kesenchedra | ketrien AT error404 DOT nls DOT net