From owner-freebsd-hardware Sat Dec 7 14:20:58 2002 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 874CC37B401 for <freebsd-hardware@freebsd.org>; Sat, 7 Dec 2002 14:20:57 -0800 (PST) Received: from yama.geminisolutions.com (yama.geminisolutions.com [216.57.214.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0D2443ED8 for <freebsd-hardware@freebsd.org>; Sat, 7 Dec 2002 14:20:52 -0800 (PST) (envelope-from michael@staff.openaccess.org) Received: from [10.0.1.2] (0-1pool22-36.nas8.bellevue1.wa.us.da.qwest.net [67.3.22.36]) by yama.geminisolutions.com (8.12.3/8.11.6) with ESMTP id gB7M9X4R049594 for <freebsd-hardware@freebsd.org>; Sat, 7 Dec 2002 14:09:33 -0800 (PST) (envelope-from michael@staff.openaccess.org) User-Agent: Microsoft-Entourage/10.0.0.1309 Date: Sat, 07 Dec 2002 14:20:39 -0800 Subject: Promise RAID controller From: Michael DeMan <michael@staff.openaccess.org> To: <freebsd-hardware@freebsd.org> Message-ID: <BA17B437.2A277%michael@staff.openaccess.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: <freebsd-hardware.FreeBSD.ORG> List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions) List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware> List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware> X-Loop: FreeBSD.org Hi All, We are using Promise RAID controllers built on motherboards. These provide simple RAID-1 mirroring for us. We had a disk fail a couple of weeks ago, and it took the whole system down. The console was still up, but the machine was unresponsive over the network. Looking at the console, it reported a hard-disk write error on the second IDE drive in the RAID configuration, on the swap partition. This was not a good thing, as we had to drive to our data center and find out what was wrong. My assumption would be that the RAID controller would respond and automatically detach a bad disk. Is anybody else working with the Promise controllers (device ar) in a production environment and found a way around this? The only thing I can think of, is to run a cronjob to watch the log file every couple of minutes looking for, and parsing, any disk failure messages and then detach the drive and fire off an e-mail. This is obviously a kludge, and it would be a lot better to pickup a signal from the ar device driver or something if there is a failure. Any ideas would be helpful. - Mike Michael F. DeMan Director of Technology OpenAccess Internet Services 1305 11th St., 3rd Floor Bellingham, WA 98225 Tel 360-647-0785 x204 Fax 360-738-9785 michael@staff.openaccess.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message