From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 29 07:07:46 2004 Return-Path: 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 4DF5B16A4CE for ; Thu, 29 Jan 2004 07:07:46 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C3AC43D2F for ; Thu, 29 Jan 2004 07:07:45 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id E06064554E; Thu, 29 Jan 2004 11:03:53 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id DDD2B3EC88 for ; Thu, 29 Jan 2004 11:03:53 -0400 (AST) Date: Thu, 29 Jan 2004 11:03:53 -0400 (AST) From: "Marc G. Fournier" To: freebsd-hardware@freebsd.org Message-ID: <20040129105934.I6922@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Permanently disabling alarm on Intel RAID controller ... X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2004 15:07:46 -0000 We have an SRCU42L controller in one of our machines whose alarm is going off due to a hard drive failure ... its driving the techs up the wall right now, so we'd like to disable it until the new drive gets in ... gonig into the onboard console and doing the Advanced F4 silences the alarm, but only until we reboot ... Is there no way of just turning it off so that it doesn't go off? and we can turn it back on again once the drive is replaced? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664