From owner-freebsd-stable@FreeBSD.ORG Wed Mar 28 12:53:58 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 227A51065670 for ; Wed, 28 Mar 2012 12:53:58 +0000 (UTC) (envelope-from mattblists@icritical.com) Received: from mail1.icritical.com (mail1.icritical.com [93.95.13.41]) by mx1.freebsd.org (Postfix) with SMTP id 643368FC08 for ; Wed, 28 Mar 2012 12:53:56 +0000 (UTC) Received: (qmail 15256 invoked from network); 28 Mar 2012 12:53:54 -0000 Received: from localhost (127.0.0.1) by mail1.icritical.com with SMTP; 28 Mar 2012 12:53:54 -0000 Received: (qmail 15242 invoked by uid 599); 28 Mar 2012 12:53:54 -0000 Received: from unknown (HELO hydrogen.icritical.com) (212.57.254.146) by mail1.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 28 Mar 2012 13:53:54 +0100 Message-ID: <4F7309E2.4000502@icritical.com> Date: Wed, 28 Mar 2012 13:53:54 +0100 From: Matt Burke User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.3) Gecko/20120328 Thunderbird/10.0.3 MIME-Version: 1.0 To: Fred Liu References: <4F68FC3E.2090401@icritical.com> <4F71FEAE.3090506@icritical.com> <4F72C588.2000204@icritical.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Mar 2012 12:53:54.0075 (UTC) FILETIME=[D4C94EB0:01CD0CE1] X-Virus-Scanned: by iCritical at mail1.icritical.com Cc: "freebsd-stable@freebsd.org" Subject: Re: SAS Drive identification LEDs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2012 12:53:58 -0000 On 03/28/12 12:40, Fred Liu wrote: >> Shouldn't imagine so... I'm using a set of 4x four-bay Chenbro >> 80H10321513C0 jobbies in a 4U box for a total of 16 disks. >> >> My original post showed me lighting up an identification LED by poking >> values at the backplane via the ses device, but the Areca utility seems >> to >> do it by poking the drives themselves - which is a much better solution >> and >> *should* be backplane-agnostic. > > Sounds very good! But what if the drive is thoroughly damaged? How would you identify such a drive on any other system? -- Sorry for the disclaimer... The information contained in this message is confidential and is intended for the addressee only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. Critical Software Ltd. reserves the right to monitor and record e-mail messages sent to and from this address for the purposes of investigating or detecting any unauthorised use of its system and ensuring its effective operation. Critical Software Ltd. registered in England, 04909220. Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH. ------------------------------------------------------------ This message has been scanned for security threats by iCritical. For further information, please visit www.icritical.com ------------------------------------------------------------