From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 24 19:57:30 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6C159E31 for ; Thu, 24 Oct 2013 19:57:30 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0A9562709 for ; Thu, 24 Oct 2013 19:57:29 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id l18so2873406wgh.30 for ; Thu, 24 Oct 2013 12:57:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Px3FYKBym3mC5Ym53IcZwneHCBaRXA+MCPLt/K0ajFU=; b=GtzhH3MEKMsAwWzl+CVzmA27qfU1023hDOAyeNCZfU/HuanjkmmofVtlwnw6uHOOEQ cRz/ZXUkZulcf8GDWpEA5PzimVAi2k5etuuQ3fLzboUVyDfsqOfAyqpzZ0Ma+n0yCJg7 5CPkaKgVjn3XzK5e2zaoz2yd23kkWARO8i4m2TInGMXhUfLqvVjI2RfPvkQhNq55FTJM oK0VRr+bSs2uVirFsOMZKJNOcjT5OLN1CI27XzzBWLprwbAs+euv3Y7zkcMt/Zi2AwSl U0fcWbFmT9l+ZyL6Xznacy6og5oKmlMqosRpuVn/IMGl6zToV+b5oUN9ubKBS4gtYtQp Ogyw== MIME-Version: 1.0 X-Received: by 10.194.94.167 with SMTP id dd7mr4079972wjb.43.1382644648494; Thu, 24 Oct 2013 12:57:28 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.194.171.35 with HTTP; Thu, 24 Oct 2013 12:57:28 -0700 (PDT) In-Reply-To: References: Date: Thu, 24 Oct 2013 13:57:28 -0600 X-Google-Sender-Auth: mw_QDdSjsRpgLQDweVFRmH8ySjA Message-ID: Subject: Re: How to blink a sas drive light? From: Alan Somers To: Outback Dingo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2013 19:57:30 -0000 You can either use sysutils/sg3_utils or ses(4). Using ses(4), take a look at l/usr/share/examples/ses/setencstat . If you set the status for a DEVICE or ARRAY_DEVICE element to something bad, then the SES processor may decide to blink the error light. It's up to the firmware, though. Using sg_ses from sg3_utils, you can set the FAULT REQSTD or IDENT bit for a particular DEVICE or ARRAY DEVICE. That is more likely to cause it to blink, but again, it's up to the expander vendor. Read the man page for details. To identify the slot where da19, resides, you can look at SES page 10. Using sg3_utils, do "sg_vpd -i da019" and find the SAS Address of the offending drive. Then do "sg_ses -p 10 /dev/ses0" and find the index of the Element whose SAS address matches. It will help to read the SES spec to understand all of the SES configuration pages. http://www.t10.org/members/w_ses3.htm -Alan On Thu, Oct 24, 2013 at 1:22 PM, Outback Dingo wrote: > I need to replace a disk connected to a SAS expander also now, there are 44 > drives. > How do i use this ses to determine the drive, can i make its light blink ?? > > im getting > > da19:mps0:0:35:0 SCSI sense ABORTED COMMAND asc:44,0 (Internal target > failure) > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"