From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 25 02:36:58 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 3B57C4A0; Fri, 25 Oct 2013 02:36:58 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E89D72239; Fri, 25 Oct 2013 02:36:57 +0000 (UTC) Received: by mail-oa0-f49.google.com with SMTP id j10so373590oah.22 for ; Thu, 24 Oct 2013 19:36:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=obWnTWDc/UA58blaQ7nrr8miswWSFMTwJViR3N+7PSM=; b=HxFFD08QIF7XRa9z9oovzDBXiyJ/gpg6j5NuLSOlgmaQ1LYfhnvkEXDUPf7U//wt2j H0UkZ4XCPnEjwbQZ3t2YF7HR2YXFJ559yeMNlwswWhf8ucomcS7qbh/kv3KTvNFqKKYK ruIsrZNYEPtUtz76r2tmKNdbqZEzkWWOcQvZfVPBi220SAmr8QX4S6Wiidpwmiorftnt sUxMG6k+Z7ZGbz4vRxBV5pmVEelHtluEgR9Jn45MOYJRHzTzbbHqEJiTCLlTwm6aCSqW u2N7vQkhpwl/0K0B3gm/dFpxIatXZkxCOPVZf6VJ+aBcjDTGm2NjhVaDongGDpJBKKU0 B9Gg== MIME-Version: 1.0 X-Received: by 10.60.36.133 with SMTP id q5mr1052701oej.63.1382668617261; Thu, 24 Oct 2013 19:36:57 -0700 (PDT) Received: by 10.76.19.115 with HTTP; Thu, 24 Oct 2013 19:36:57 -0700 (PDT) In-Reply-To: References: <82839443-30E1-4243-A82C-E0AA12E56607@gsoft.com.au> <1382664264.2498.10.camel@localhost> <1382665841.2498.14.camel@localhost> <1382667668.18382.1.camel@localhost> Date: Thu, 24 Oct 2013 22:36:57 -0400 Message-ID: Subject: Re: How to blink a sas drive light? From: Outback Dingo To: sbruno@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers 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: Fri, 25 Oct 2013 02:36:58 -0000 On Thu, Oct 24, 2013 at 10:28 PM, Outback Dingo wrote: > > > > On Thu, Oct 24, 2013 at 10:21 PM, Sean Bruno wrote: > >> >> If you're up for Science, can you go upon you >> host's /usr/share/examples/ses >> > > been down that path...... its a wonder theres no "simple" way to just say > blink disk 18 from the cli > maybe i should be saying..... my disks are layed out in the chassis like left to right Row1 0-2, 0-1, 0-0, 1-2, 1-1, 1-0, 2-2, 2-1, 2-0, 3-2, 3-1, 3-0, 4-2, 4-1, 4-0 Row2 0-5, 0-4, 0-3, 1-5, 1-4, 1-3, 2-5, 2-4, 2-3, 3-5, 3-4, 3-3, 4-5, 4-4, 4-3 Row2 0-8, 0-7, 0-6, 1-8, 1-7, 1-6, 2-8, 2-7, 2-6, 3-8, 3-7, 3-6, 4-8, 4-7, 4-6 now ill assume 0- , 1- , 2- , 3- , and 4- are assigned an enclosure FreeBSD sees da19:mps0:0:35:0 SCSI sense ABORTED COMMAND asc:44,0 (Internal target failure) as dead, box scrolls forever at this and doesnt boot........ and its an SSD drive, there are a total of 4 in the chassis, and 40 SAS drives so.... how do i correlate what FreeBSD says in relation to its location in the chassis..... maybe this clears up the dilemma....... and pull the right drive to replace it. > > >> >> build the tools there, and post the output of getencstat /dev/ses0 ? >> >> sean >> >> p.s. if you've already done this, just send me the output privately. >> > >