From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 4 11:16:15 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 01FF6641 for ; Thu, 4 Jun 2015 11:16:15 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com [195.16.151.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B5F211443 for ; Thu, 4 Jun 2015 11:16:14 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop01.sare.net (Postfix) with ESMTPSA id E025F9DDD53 for ; Thu, 4 Jun 2015 13:08:33 +0200 (CEST) From: Borja Marcos Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: LSI 3008 based HBA (mpr) and backplane slot identification Date: Thu, 4 Jun 2015 13:08:29 +0200 Message-Id: <42B5FB65-9A1A-4F55-A15A-1F91F9770363@sarenet.es> To: FreeBSD-scsi Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) 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 11:16:15 -0000 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=20 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 =20 Model Number : Samsung SSD 840=20 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=20 "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.