From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 25 03:05:51 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 3A96F79B; Fri, 25 Oct 2013 03:05:51 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7434E2482; Fri, 25 Oct 2013 03:05:49 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id gq1so395976obb.17 for ; Thu, 24 Oct 2013 20:05:48 -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=NWk2A6dXX3EVrfii3fjsj8z+AheRBClnMVOOOKtORtA=; b=yAcQJd9b4gy3Cue31loMfsR63GJOjYL2rB/HYTnRG1RkMOJjB5N6x/94zbiE34aeBj HM0fciG/5RsnHpeSN9jHNDZpvgRHa0EyqDIEYs2Egh20IPj6qHGt+WHK6yVYQhEG4udM xzFRrykKrhEk52BM/ZuBbSWB7LV/TMCnF9ISiYzQJS/pTK8sLo0Hx0y/NSv8BmlYf1YY /C8LmdQnVhsL2SmPuIy/AXY8DNDG2nrqLSxOYTDYdUqL2pg1SiOsE804qcua4irg89pg o0y//4FrF0MCTclSzX1J1UBMxfSEJHUaMUSGjfU+jspgWfb+0kaa8UUotittE6Zortr9 vWiw== MIME-Version: 1.0 X-Received: by 10.182.88.202 with SMTP id bi10mr1235998obb.52.1382670348524; Thu, 24 Oct 2013 20:05:48 -0700 (PDT) Received: by 10.76.19.115 with HTTP; Thu, 24 Oct 2013 20:05:48 -0700 (PDT) In-Reply-To: <1382670178.18382.8.camel@localhost> References: <82839443-30E1-4243-A82C-E0AA12E56607@gsoft.com.au> <1382664264.2498.10.camel@localhost> <1382665841.2498.14.camel@localhost> <1382667668.18382.1.camel@localhost> <1382670178.18382.8.camel@localhost> Date: Thu, 24 Oct 2013 23:05:48 -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 03:05:51 -0000 On Thu, Oct 24, 2013 at 11:02 PM, Sean Bruno wrote: > On Thu, 2013-10-24 at 22:36 -0400, Outback Dingo wrote: > > > > > > > > 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. > > > > > > > > Yeah, its clear from this what you want. It *should* be simple, but I > can't tell the wiring though. > > I *think* you want to use sysutils/smp_utils ... maybe. It sure looks > like its for just this type of thing. I don't have anything available > to give you more of a clue though. > > But, don't do that if you don't have a /dev/ses0 device to talk to in > the first place. I looked back through the thread and I didn't see that > you tried this way of doing it yet. > Thanks ill look into this, due to multipath theres actually 16 ses devices, ill get back on the research > > sean > > >