From owner-freebsd-scsi Mon Dec 13 22:53:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles528.castles.com [208.214.165.92]) by hub.freebsd.org (Postfix) with ESMTP id A865015512; Mon, 13 Dec 1999 22:53:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA01148; Mon, 13 Dec 1999 22:56:12 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912140656.WAA01148@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Cc: Mike Smith , freebsd-scsi@freebsd.org Subject: Re: Again: CRD-Raid-Controller and FreeBSD 3.x In-reply-to: Your message of "Mon, 13 Dec 1999 21:07:22 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 22:56:12 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > I love playing the "which disk is dead" game when a DPT RAID > > > controller's audible alarm is sounding, but I have to boot into the > > > management interface to figure out which one. > > > > This is what managed enclosures are for. > > Huh? And how is that supposed to work? I use SAF-TE enclosures. > Unless I can access the RAID management app, how can I access that info? > That certainly isn't possible with a DPT controller. > > Besides, SAF-TE can tell what disks are plugged in, not which ones > actually work. Any decent managed enclosure has a 'fault' indicator for each drive. Any decent controller will set the 'fault' indicator for a failed drive. I concede your basic point - we need a better software management interface yet; but my original one also stands that these controllers are something that with a bit more encouragement we will be able to depend upon just as well. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message