From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 4 15:23:44 2015 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0DA6470 for ; Thu, 4 Jun 2015 15:23:44 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C82FF112E for ; Thu, 4 Jun 2015 15:23:43 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by oihb142 with SMTP id b142so33668909oih.3 for ; Thu, 04 Jun 2015 08:23:43 -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=WYaYsyzsMZghcnl//iK2GMZQY2Iq1Sh3wJcfxAMkjh0=; b=CNLZvbeWROoBJkGjFnNRQYbBsVycBdmiUmrpq3SZit9j6jP0yCMWJ7fpiXP1rEHulM u/1dvByajV2W2hSVqV922ohC3tlUm1KlbWdsitqQwafwn2z4WjWMhDOL1S7Rby6HGagC iO60zzCB9t9bO2Nv3IZoWJpvYgmc57/GKUi0rwnK1yXYMYoH0oYBpcb6BGk+FaqO+V9r SHQS6F7CIq6SaMrs1eFlWJBAOzsL+Vx93MGvDymPrPqrzu3d+JZRJ1mm+P/klM8D6q0u CCpF25P7G0RirlGOZurYIDAhIUPkLwEe95HR/ySrVC9TJ2gqp81RJnTw4SqpopNiHAE2 IIzA== MIME-Version: 1.0 X-Received: by 10.202.54.3 with SMTP id d3mr31027086oia.103.1433431423152; Thu, 04 Jun 2015 08:23:43 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.107.3 with HTTP; Thu, 4 Jun 2015 08:23:43 -0700 (PDT) In-Reply-To: <42B5FB65-9A1A-4F55-A15A-1F91F9770363@sarenet.es> References: <42B5FB65-9A1A-4F55-A15A-1F91F9770363@sarenet.es> Date: Thu, 4 Jun 2015 09:23:43 -0600 X-Google-Sender-Auth: nb0_pESihancQy0EnwEVcK_UA1w Message-ID: Subject: Re: LSI 3008 based HBA (mpr) and backplane slot identification From: Alan Somers To: Borja Marcos Cc: FreeBSD-scsi Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2015 15:23:44 -0000 On Thu, Jun 4, 2015 at 5:08 AM, Borja Marcos wrote: > > Hello, > > I am now trying the LSI 3008 based HBAs, and I would like to know wether I have a _reliable_ slot identification method or not. > > I am using the sas3ircu tool in the same way I did with the LSI 2008 HBA. It helps me to locate the slot number for a disk > using "sas3ircu 0 display". > > -------- > Device is a Hard disk > Enclosure # : 2 > Slot # : 16 > SAS Address : 5005076-0-3ea6-f971 > State : Ready (RDY) > Size (in MB)/(in sectors) : 953869/1953525167 > Manufacturer : ATA > Model Number : Samsung SSD 840 > Firmware Revision : CB6Q > Serial No : S1D9NSAFB14948X > GUID : N/A > Protocol : SATA > Drive Type : SATA_SSD > ------- > > What I don't know is: can I consider this a reliable method of identification? Can these slot numbers be somewhat shuffled due to > "cached" parameter oddities similar to the target ID persistance issues? > > In case we need to replace a disk we need to make sure we are using the right slot number. > > Besides, it would be a good idea to have a port with sas3ircu, the same way there is one for sas2ircu. > > > > > Thanks! > > > > > > Borja. I've never used sas3ircu or sas2ircu, but it's probably getting the slot number based on either the expander's SES Additional Element Status Page, or by the expander's SMP DISCOVER response. Both of those methods will give stable responses. Even if you swap drives, move them around, turn phys on and off, etc, both of those methods will still map the same physical slot to the same Slot # every time. Only an expander or HBA firmware upgrade can change it. However, the slot mapping may not make intuitive sense. You'll have to experiment to see what Slot # corresponds to what physical slot. When you need to replace a drive, your best option would be to use the "sas3ircu locate" command to turn on the slot's error LED. Then you won't need to consult a slot mapping diagram. -Alan