Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Jun 2015 17:33:07 +0200
From:      Borja Marcos <borjam@sarenet.es>
To:        Alan Somers <asomers@freebsd.org>
Cc:        FreeBSD-scsi <freebsd-scsi@freebsd.org>
Subject:   Re: LSI 3008 based HBA (mpr) and backplane slot identification
Message-ID:  <539C61B5-770C-4C75-8B1E-258BB885B55E@sarenet.es>
In-Reply-To: <CAOtMX2jLkXtV7smc9Ot0iu0ZJbx9nxwJ2r6ZNxwPxtetC83MQA@mail.gmail.com>
References:  <42B5FB65-9A1A-4F55-A15A-1F91F9770363@sarenet.es> <CAOtMX2jLkXtV7smc9Ot0iu0ZJbx9nxwJ2r6ZNxwPxtetC83MQA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539C61B5-770C-4C75-8B1E-258BB885B55E>