From owner-freebsd-hardware Tue Oct 9 19:38:16 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from gahch.it.ca (gahch.it.ca [216.126.86.4]) by hub.freebsd.org (Postfix) with ESMTP id 116F337B408 for ; Tue, 9 Oct 2001 19:38:11 -0700 (PDT) Received: (from paul@localhost) by gahch.it.ca (8.11.6/8.11.6) id f9A2b0X27740; Tue, 9 Oct 2001 22:37:00 -0400 (EDT) (envelope-from paul) Date: Tue, 9 Oct 2001 22:37:00 -0400 From: Paul Chvostek To: sawilson@sawilson.com Cc: freebsd-hardware@freebsd.org Subject: Re: amr driver and disk failure notification Message-ID: <20011009223700.B14443@gahch.it.ca> References: <20011010021644.2718.cpmta@c001.snv.cp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011010021644.2718.cpmta@c001.snv.cp.net>; from sawilson@sawilson.com on Tue, Oct 09, 2001 at 07:16:44PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thanks for the advice, but.... If there is a speaker on the Dell PERC card, I suspect I wouldn't be able to hear it from where I'm sitting. The server sits in a lights-out co-location environment which is visited very rarely, about fifteen blocks from my office. If a disk fails, the machine continues to run on the remaining disk, so the idea here is to put something together that will let the box send out an email or run qpage or something in the event of a problem. I've got healthd running, along with SNMP monitoring of disk space and CPU, but is there no way to detect recoverable disk failure? Could I maybe ... hook up the speaker on the controller to a line on an unused serial port, and write a daemon to watch for a particular pattern? Or, since there's a "disk warning" LED on the front, maybe I could wire *that* to an unused line on a serial or parallel port. It seems really odd that this box, designed specifically for this kind of environment, won't let me detect a problem without my being physically near the box. :-( p On Tue, Oct 09, 2001 at 07:16:44PM -0700, sawilson@sawilson.com wrote: > > On Tue, 09 October 2001, Paul Chvostek wrote: > > > I suspect that AMI or whoever has come up with Windows software that > > talks to this controller, but I'm obviously not aware of anything for > > FreeBSD. > > > > Any help would be appreciated. :) > > I have a great answer. Most of the cards have their own built in speaker that will signal you with a beep system. Off the top of my head it's: > > 3 second beep one second break when a drive dies and while it's rebuilding > 1 second beep 3 second break after it's done rebuilding > > If I'm not mistaken, that dell has a megaraid 428 in it. I can say that from experience the beeping is really frelling annoying. A lot of OEM's elect to turn the speaker off in the config. You should ctrl+m during boot and turn it back on. My megaraid 1300 has been awesome so far. The only issue is that for some reason I couldn't get into the config from the boot prompt. I had to download a disk image of a win98 boot disk, and spend a saturday afternoon finding MEGACONF.exe for DOS. Hope this helps. > > -- > > Best Regards, > S.A.Wilson > > "The box said 'Requires Windows 95, NT, or better' so I installed FreeBSD." -- Paul Chvostek Operations / Development / Abuse / Whatever vox: +1 416 598-0000 IT Canada http://www.it.ca/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message