From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 1 08:56:16 2015 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A76616D0 for ; Mon, 1 Jun 2015 08:56:16 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2857811AD for ; Mon, 1 Jun 2015 08:56:14 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. ([IPv6:fd00::77d]) by elf.hq.norma.perm.ru (8.14.9/8.14.9) with ESMTP id t518u95e028410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 1 Jun 2015 13:56:10 +0500 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <556C1E29.808@norma.perm.ru> Date: Mon, 01 Jun 2015 13:56:09 +0500 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: scsi@freebsd.org Subject: FreeBSD, HP Smart Array controllers and stuff Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (elf.hq.norma.perm.ru [IPv6:fd00::30a]); Mon, 01 Jun 2015 13:56:10 +0500 (YEKT) X-Spam-Status: No hits=-99.9 bayes=0.0000 testhits AWL=0.573,BAYES_00=-1.9, RDNS_NONE=0.793,SPF_SOFTFAIL=0.665,USER_IN_WHITELIST=-100 autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on elf.hq.norma.perm.ru 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: Mon, 01 Jun 2015 08:56:16 -0000 Hi. I just wanted to ask - how do you guys deal with Smart Array controllers ? Do you install Linux/Solaris on these servers (I do), because FreeBSD doesn't have an utility to watch after the raid (I'm aware that it used to have one, first it was just fine, then it was required to do a lot of stuff to use it, and nowadays it's finally noy useable with new firmware)? Same thing about the cciss driver - Linux has the hpsa one, for like 6 years. It's called "opensource" by HP, so I guess the sources are available (I'm aware that porting it to FreeBSD may and would be a hell of a work, but still). Another question (for me at least) is wht we even have a HP Smart Array driver - seems to be purely of academic interest without an utility. But may be I miss something (yeah, know that some guys create r0 units from each disk but this still seems weird to me). May be a kickstarter project or something like it would help ? Or this is condemned from the start, because HP won't cooperate ? Thanks. Eugene. From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 1 09:06:39 2015 Return-Path: Delivered-To: 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 C939A9FA for ; Mon, 1 Jun 2015 09:06:39 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com [195.16.148.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 883371475 for ; Mon, 1 Jun 2015 09:06:39 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop02.sare.net (Postfix) with ESMTPSA id 119EE9DC814; Mon, 1 Jun 2015 10:59:23 +0200 (CEST) Subject: Re: FreeBSD, HP Smart Array controllers and stuff Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <556C1E29.808@norma.perm.ru> Date: Mon, 1 Jun 2015 10:59:19 +0200 Cc: scsi@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <556C1E29.808@norma.perm.ru> To: "Eugene M. Zheganin" 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: Mon, 01 Jun 2015 09:06:39 -0000 On Jun 1, 2015, at 10:56 AM, Eugene M. Zheganin wrote: > I just wanted to ask - how do you guys deal with Smart Array = controllers > ? Do you install Linux/Solaris on these servers (I do), because = FreeBSD > doesn't have an utility to watch after the raid (I'm aware that it = used > to have one, first it was just fine, then it was required to do a lot = of > stuff to use it, and nowadays it's finally noy useable with new > firmware)? I own two Microserver Gen8 servers. The way to go is to set up the = controller in SATA mode (no RAID) and use ZFS. Borja. From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 1 10:23:56 2015 Return-Path: Delivered-To: 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 3CE2E6A for ; Mon, 1 Jun 2015 10:23:56 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AF7B117FE for ; Mon, 1 Jun 2015 10:23:55 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. ([IPv6:fd00::77d]) by elf.hq.norma.perm.ru (8.14.9/8.14.9) with ESMTP id t51ANoMR042259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 1 Jun 2015 15:23:50 +0500 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <556C32B6.9030500@norma.perm.ru> Date: Mon, 01 Jun 2015 15:23:50 +0500 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 CC: scsi@freebsd.org Subject: Re: FreeBSD, HP Smart Array controllers and stuff References: <556C1E29.808@norma.perm.ru> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (elf.hq.norma.perm.ru [IPv6:fd00::30a]); Mon, 01 Jun 2015 15:23:50 +0500 (YEKT) X-Spam-Status: No hits=-99.4 bayes=0.0000 testhits AWL=0.015,BAYES_00=-1.9, MISSING_HEADERS=1.021,RDNS_NONE=0.793,SPF_SOFTFAIL=0.665, USER_IN_WHITELIST=-100 autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on elf.hq.norma.perm.ru 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: Mon, 01 Jun 2015 10:23:56 -0000 Hi. On 01.06.2015 13:59, Borja Marcos wrote: > On Jun 1, 2015, at 10:56 AM, Eugene M. Zheganin wrote: > >> I just wanted to ask - how do you guys deal with Smart Array controllers >> ? Do you install Linux/Solaris on these servers (I do), because FreeBSD >> doesn't have an utility to watch after the raid (I'm aware that it used >> to have one, first it was just fine, then it was required to do a lot of >> stuff to use it, and nowadays it's finally noy useable with new >> firmware)? > I own two Microserver Gen8 servers. The way to go is to set up the controller in SATA mode (no RAID) > and use ZFS. > What exactly is the model of the raid controller you have there ? Eugene. 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. 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 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. From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 4 15:52:26 2015 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87AE94F6 for ; Thu, 4 Jun 2015 15:52:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (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 4B8C718C2 for ; Thu, 4 Jun 2015 15:52:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by obbea3 with SMTP id ea3so35619100obb.0 for ; Thu, 04 Jun 2015 08:52:25 -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=h4ft+Me1IA/vjS5Ev9ctn9x/W67+3GPKrJEQFngrbYQ=; b=HbliKT6ZcHH7uazGryyZvZCEEMnUIJ5GEyMGaR8D3MRvJhI/jNEy9x0K8Ryxe5KaJB XMDVRZT/+XLGzDq3fJ+C2ahEnzk6BXqLSBbNdcSP9woxYD9rDSRT1+t+y49cYLj3iu2T KfppTsfLobxpGUpVrgnlH6vxG7iVoe/GOZxUCTqBvr1w51KErY185oeuzR7Hkms2JAnj XwwJldNYr4E5b/nQy3ZafhBMNcEvRG7233ymLVn9pvMIw2LIg+OuqtXD/XGGX+K+aNso Kpu40+s/n50pmbXABgKqtyudTktzj88N6Ma4kSzOvQK02ZDWzxptIxn7ibmy+QjJUCWV WA4g== MIME-Version: 1.0 X-Received: by 10.182.16.161 with SMTP id h1mr12183384obd.49.1433433145563; Thu, 04 Jun 2015 08:52:25 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.107.3 with HTTP; Thu, 4 Jun 2015 08:52:25 -0700 (PDT) In-Reply-To: <539C61B5-770C-4C75-8B1E-258BB885B55E@sarenet.es> References: <42B5FB65-9A1A-4F55-A15A-1F91F9770363@sarenet.es> <539C61B5-770C-4C75-8B1E-258BB885B55E@sarenet.es> Date: Thu, 4 Jun 2015 09:52:25 -0600 X-Google-Sender-Auth: CmgzcWRRJBHMOcKiFIPCesWL7FQ 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:52:26 -0000 On Thu, Jun 4, 2015 at 9:33 AM, Borja Marcos wrote: > > 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. > > What I was wondering was it something could change the mapping unexpectedly. > 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. Nope. Slot stuff happens at a lower layer than bus/target/lun assignment. For each slot, the expander tells the host the SAS Address of the drive installed in that slot, if any. If you want to play around, install sysutils/sg3_utils and run "sg_ses -p 10 /dev/ses0". > >> 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. > Glad to help. -Alan