From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 4 15:33:12 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 9698523C; Thu, 4 Jun 2015 15:33:12 +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 538FE13CC; Thu, 4 Jun 2015 15:33:11 +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 BE3CF9DDE8B; Thu, 4 Jun 2015 17:33:08 +0200 (CEST) Subject: Re: LSI 3008 based HBA (mpr) and backplane slot identification Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: Date: Thu, 4 Jun 2015 17:33:07 +0200 Cc: FreeBSD-scsi Content-Transfer-Encoding: quoted-printable Message-Id: <539C61B5-770C-4C75-8B1E-258BB885B55E@sarenet.es> References: <42B5FB65-9A1A-4F55-A15A-1F91F9770363@sarenet.es> To: Alan Somers 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 15:33:12 -0000 On Jun 4, 2015, at 5:23 PM, Alan Somers wrote: > 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. Thank you very much. At least on the machines on which I am using it, = the mapping is stable and even intuitive.=20 What I was wondering was it something could change the mapping = unexpectedly.=20 Understood, a firmware update is a risk, but I was thinking about those = static mappings between target IDs and particular disks (I imagine, serial numbers) kept = by the HBA. It would be a tickling timebomb if, say, after four or five disk = replacements numbers begun to get shuffled. > 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. Sorry, I didn't know that command. I haven't been exactly eager to try = options to sas[23]ircu because it's intended for IR firmware (or that I understand) and I am = using IT. Thank you very much! Borja.