From owner-freebsd-questions Tue Dec 12 19:31:22 2000 From owner-freebsd-questions@FreeBSD.ORG Tue Dec 12 19:31:21 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from froody.rupture.net (froody.rupture.net [205.252.38.80]) by hub.freebsd.org (Postfix) with ESMTP id 8092637B400 for ; Tue, 12 Dec 2000 19:31:20 -0800 (PST) Received: from localhost (jon@localhost) by froody.rupture.net (8.9.3/8.9.3) with ESMTP id WAA03169 for ; Tue, 12 Dec 2000 22:41:17 -0500 (EST) (envelope-from jon@blading.com) X-Authentication-Warning: froody.rupture.net: jon owned process doing -bs Date: Tue, 12 Dec 2000 22:41:16 -0500 (EST) From: Jon Nathan X-Sender: jon@froody.rupture.net To: questions@freebsd.org Subject: raid - failed disks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, how can one monitor the status of individual disks in a raid array under freebsd? i have a bunch of machines with dpt smartraid iv and ami megaraid controllers. they're expected to be production, 24/7 servers, so scheduled downtime is rare. how can i tell if a disk has failed so i can replace it? userland programs? or do i really have to drop into the raid bios (or boot to dos and use dptmgr)? anything under development? with disks often being the least reliable component these days, how do other administrators handle this? -jon -- Jon Nathan jon@blading.com http://www.rupture.net/~jon/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message