From owner-freebsd-scsi@FreeBSD.ORG Tue Mar 11 16:59:15 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 79D2FCFC; Tue, 11 Mar 2014 16:59:15 +0000 (UTC) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E4CEADF7; Tue, 11 Mar 2014 16:59:14 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id x13so10357787wgg.21 for ; Tue, 11 Mar 2014 09:59:13 -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=NjoE1o7y2gIU910340JLkPTdEDzT+HrSqfQi75aZtM4=; b=YHJWaMDyew11d2uPw5GFNrP0V8gLTeKgCLZYocTeYWjFDRIGrIAUpqjd+1SBVF428/ NpwdEIpAngexCT3ebz4INaPK5Nwi0igEoDMp8C8Zb6NNgAX+Ft/EkGtOAWMmjzihm30f UAkW3qr6DJ+qYv9+pv51LznB93RthXatSAsimFkKPCcIQ+Gu/92b4vKS9nTRZulQuBi8 tzGRugMjG7mUfuESncUaPWlnwo3vKNptKVd4KIcRbW92usOCXaXHBl6LuaI5u5Oy2Yb2 0Ao3uKv23u/5IY+IvXyiIzK4MybxlqBj9ytM73WWPg5dhF+73XxgfVuYFrJb//JdpyII Uo9A== MIME-Version: 1.0 X-Received: by 10.194.2.194 with SMTP id 2mr2134418wjw.73.1394557153317; Tue, 11 Mar 2014 09:59:13 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.194.168.197 with HTTP; Tue, 11 Mar 2014 09:59:13 -0700 (PDT) In-Reply-To: References: <2336CAA2-7FC0-41EC-AE1D-0592A9E1E8E0@sarenet.es> Date: Tue, 11 Mar 2014 10:59:13 -0600 X-Google-Sender-Auth: Zkl8bDV1YC0Z7vH6YDpGlvhUN94 Message-ID: Subject: Re: LSI SAS HBAs (mps) utility From: Alan Somers To: Borja Marcos Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Mar 2014 16:59:15 -0000 On Tue, Mar 11, 2014 at 10:45 AM, Borja Marcos wrote: > > On Mar 11, 2014, at 5:35 PM, Alan Somers wrote: > >> What do you mean, it doesn't find the "real" slots? What are you >> expecting to see? Do you have a SAS expander in this system? If so, >> you have some hope of seeing useful information about the physical >> position of a drive. If not, then you won't get much better than >> knowing which SAS port is connected to a drive. > > I just notice that, since I flashed the card (A Dell H200) to so-called "IT Mode" it doesn't show the expanders. > > This is what I saw before flashing the card: > Feb 12 10:01:33 pruebassd kernel: ses0 at mps0 bus 0 scbus0 target 3 lun 0 > Feb 12 10:01:33 pruebassd kernel: ses0: Fixed Enclosure Services SCSI-5 device > Feb 12 10:01:33 pruebassd kernel: ses0: 150.000MB/s transfers > Feb 12 10:01:33 pruebassd kernel: ses0: Command Queueing enabled > Feb 12 10:01:33 pruebassd kernel: ses0: SCSI-3 ENC Device > > And now, same hardware, different firmware, I don't see the "ses0" expander, odd. Surprising. What does "camcontrol devlist" show you? > > Anyway, I pulled one of the disks (physical slot 4) and it wasn't the disk identified by sas2ircu as connected to "1:4" but > a different one. What do you mean by "physical slot 4"? The HBA doesn't know anything about physical positions. Even the SES expander probably isn't numbering the slots in the order that you expect. > > That I mean. Chaos... ;) I'm having trouble understanding your English. What does this sentence mean? -Alan > > > > > Borja. >