From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 22 15:22:03 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29A931065672 for ; Wed, 22 Feb 2012 15:22:03 +0000 (UTC) (envelope-from dgilbert@interlog.com) Received: from smtp.infotech.no (smtp.infotech.no [82.134.31.41]) by mx1.freebsd.org (Postfix) with ESMTP id C2E888FC1E for ; Wed, 22 Feb 2012 15:22:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.infotech.no (Postfix) with ESMTP id 9FBB8204172; Wed, 22 Feb 2012 16:21:59 +0100 (CET) X-Virus-Scanned: by amavisd-new-2.6.6 (20110518) (Debian) at infotech.no Received: from smtp.infotech.no ([127.0.0.1]) by localhost (smtp.infotech.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MPTBJjPZ8Y1c; Wed, 22 Feb 2012 16:21:58 +0100 (CET) Received: from [192.168.48.66] (unknown [69.166.22.91]) by smtp.infotech.no (Postfix) with ESMTPA id BB96620402E; Wed, 22 Feb 2012 16:21:57 +0100 (CET) Message-ID: <4F450814.4020100@interlog.com> Date: Wed, 22 Feb 2012 10:21:56 -0500 From: Douglas Gilbert User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Desai, Kashyap" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-scsi@freebsd.org" , "McConnell, Stephen" Subject: Re: LSI2008 controller clobbers first disk with new LSI mps driver X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dgilbert@interlog.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2012 15:22:03 -0000 On 12-02-22 03:39 AM, Desai, Kashyap wrote: > Here is a possible root cause of this issue. > > Enclosure which you are using in your setup (might be) not configured properly. > > You have Enclosure with 12 Slots + 1 SES Device. > See below detail from the log. > > EventDataLength: 5 > AckRequired: 0 > Event: SasEnclDeviceStatusChange (0x1d) > EventContext: 0x0 > EnclosureHandle: 0x2 > ReasonCode: Added > PhysicalPort: 0 > NumSlots: 13 > StartSlot: 0 > PhyBits: 0xff > > StartSlot is 0 in this case. > Correct behavior should be each device on your enclosure must have different slot number starting from 0 till 12. > I have doubt that SES device has not configured well and it is using slot-0 as default. This can create issue for actual device which is connected to slot-0. > So In your setup you will have slot-0 till slot-11 assigned for actual Phys of your enclosures and again slot-0 is assigned for SES device instead of Slot-12. No. SAS-2 expanders typically have an integral SES device on an expander _virtual_ phy (see SMP DISCOVER (LIST) response). Once you see that virtual phy flag the slot number is irrelevant. Doug Gilbert