From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 3 23:01:11 2011 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 225E410656B2 for ; Thu, 3 Feb 2011 23:01:11 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id DF3338FC08 for ; Thu, 3 Feb 2011 23:01:10 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id p13N1AAD026048; Thu, 3 Feb 2011 16:01:10 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p13N19O2026047; Thu, 3 Feb 2011 16:01:09 -0700 (MST) (envelope-from ken) Date: Thu, 3 Feb 2011 16:01:09 -0700 From: "Kenneth D. Merry" To: Borja Marcos Message-ID: <20110203230109.GA25718@nargothrond.kdm.org> References: <20110120170046.GA40879@nargothrond.kdm.org> <13EDCBDE-6C2C-4CE5-9B0E-7FCF6FB02FA1@sarenet.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13EDCBDE-6C2C-4CE5-9B0E-7FCF6FB02FA1@sarenet.es> User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org Subject: Re: mps questions X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2011 23:01:11 -0000 On Wed, Jan 26, 2011 at 11:16:57 +0100, Borja Marcos wrote: > > On Jan 20, 2011, at 6:00 PM, Kenneth D. Merry wrote: > > > If you see all the disks in the LSI BIOS, it most likely means there is a > > driver bug that is keeping FreeBSD from seeing all the disks. > > > > Try booting with -v (boot -v at the boot loader prompt) and send the full > > dmesg output. That will cause the driver to print some additional > > information when it probes. > > > > After that, try booting with hw.mps.N.debug_level=1 set in loader.conf, > > where N is either 0 or 1, depending on which mps instance is having the > > problem. > > > > You can turn it off via sysctl after you boot. > > Sorry, more complete output follows. boot -v and debug enabled for the driver. > > I've omitted plenty of "mps0: writing postindex NNN" messages It looks like the driver does see 8 disks initially. Here are the SAS device pages, interleaved with their repsective PHY pages. The last two disks don't have PHY pages associated with them, so that means that the probe failed to get the PHY page from the controller for those devices. Try booting with hw.mps.N.debug_level=4 That should give us a printout with the IOC status, and perhaps it'll be clearer why those devices are failing to probe. They're in slots 6 and 7 of the enclosure, by the way. I'm not sure how that maps to their physical location. > mps0: SAS Device Page 0 : > Slot: 0 > EnclosureHandle: 0x2 > SASAddress: 0x5000c5002c4f7d2d > ParentDevHandle: 0xa > PhyNum: 2 > AccessStatus: 0x0 > DevHandle: 0xb > AttachedPhyIdentifier: 0x0 > ZoneGroup: 0 > DeviceInfo: c01,End Device > Flags: 0x1 > PhysicalPort: 0 > MaxPortConnections: 1 > DeviceName: 0x0 > PortGroups: 4 > DmaGroup: 0 > ControlGroup: 4 > mps0: SAS PHY Page 0 : > OwnerDevHandle: 0x0001 > AttachedDevHandle: 0x000a > AttachedPhyIdentifier: 21 > AttachedPhyInfo Reason: Loss DWORD Sync (0x14) > ProgrammedLinkRate: 6.0Gbps (0xa8) > HwLinkRate: 6.0Gbps (0xa8) > ChangeCount: 1 > Flags: 0x1 > PhyInfo Reason: Power On (0x10000) > NegotiatedLinkRate: 6.0Gbps (0xaa) > mps0: Found device ,End Device> <6.0Gbps> <0x000b> <2/0> > mps0: Triggering rescan of 0:1:-1 > mps0: SAS Device Page 0 : > Slot: 4 > EnclosureHandle: 0x2 > SASAddress: 0x5000c5002c4f6ec1 > ParentDevHandle: 0xa > PhyNum: 3 > AccessStatus: 0x0 > DevHandle: 0xc > AttachedPhyIdentifier: 0x0 > ZoneGroup: 0 > DeviceInfo: c01,End Device > Flags: 0x1 > PhysicalPort: 0 > MaxPortConnections: 1 > DeviceName: 0x0 > PortGroups: 4 > DmaGroup: 0 > ControlGroup: 4 > mps0: SAS PHY Page 0 : > OwnerDevHandle: 0x0001 > AttachedDevHandle: 0x000a > AttachedPhyIdentifier: 20 > AttachedPhyInfo Reason: Loss DWORD Sync (0x14) > ProgrammedLinkRate: 6.0Gbps (0xa8) > HwLinkRate: 6.0Gbps (0xa8) > ChangeCount: 1 > Flags: 0x1 > PhyInfo Reason: Power On (0x10000) > NegotiatedLinkRate: 6.0Gbps (0xaa) > mps0: Found device ,End Device> <6.0Gbps> <0x000c> <2/4> > mps0: Triggering rescan of 0:4:-1 > mps0: SAS Device Page 0 : > Slot: 5 > EnclosureHandle: 0x2 > SASAddress: 0x5000c5002c4f7425 > ParentDevHandle: 0xa > PhyNum: 4 > AccessStatus: 0x0 > DevHandle: 0xd > AttachedPhyIdentifier: 0x0 > ZoneGroup: 0 > DeviceInfo: c01,End Device > Flags: 0x1 > PhysicalPort: 0 > MaxPortConnections: 1 > DeviceName: 0x0 > PortGroups: 4 > DmaGroup: 0 > ControlGroup: 4 > mps0: SAS PHY Page 0 : > OwnerDevHandle: 0x0001 > AttachedDevHandle: 0x000a > AttachedPhyIdentifier: 15 > AttachedPhyInfo Reason: Loss DWORD Sync (0x14) > ProgrammedLinkRate: 6.0Gbps (0xa8) > HwLinkRate: 6.0Gbps (0xa8) > ChangeCount: 1 > Flags: 0x1 > PhyInfo Reason: Power On (0x10000) > NegotiatedLinkRate: 6.0Gbps (0xaa) > mps0: Found device ,End Device> <6.0Gbps> <0x000d> <2/5> > mps0: Triggering rescan of 0:5:-1 > mps0: SAS Device Page 0 : > Slot: 1 > EnclosureHandle: 0x2 > SASAddress: 0x5000c5002c4f7875 > ParentDevHandle: 0xa > PhyNum: 5 > AccessStatus: 0x0 > DevHandle: 0xe > AttachedPhyIdentifier: 0x0 > ZoneGroup: 0 > DeviceInfo: c01,End Device > Flags: 0x1 > PhysicalPort: 0 > MaxPortConnections: 1 > DeviceName: 0x0 > PortGroups: 4 > DmaGroup: 0 > ControlGroup: 4 > mps0: SAS PHY Page 0 : > OwnerDevHandle: 0x0001 > AttachedDevHandle: 0x000a > AttachedPhyIdentifier: 14 > AttachedPhyInfo Reason: Loss DWORD Sync (0x14) > ProgrammedLinkRate: 6.0Gbps (0xa8) > HwLinkRate: 6.0Gbps (0xa8) > ChangeCount: 1 > Flags: 0x1 > PhyInfo Reason: Power On (0x10000) > NegotiatedLinkRate: 6.0Gbps (0xaa) > mps0: Found device ,End Device> <6.0Gbps> <0x000e> <2/1> > mps0: Triggering rescan of 0:2:-1 > mps0: SAS Device Page 0 : > Slot: 2 > EnclosureHandle: 0x2 > SASAddress: 0x5000c5002c54578d > ParentDevHandle: 0xa > PhyNum: 6 > AccessStatus: 0x0 > DevHandle: 0xf > AttachedPhyIdentifier: 0x0 > ZoneGroup: 0 > DeviceInfo: c01,End Device > Flags: 0x1 > PhysicalPort: 0 > MaxPortConnections: 1 > DeviceName: 0x0 > PortGroups: 4 > DmaGroup: 0 > ControlGroup: 4 > mps0: SAS PHY Page 0 : > OwnerDevHandle: 0x0001 > AttachedDevHandle: 0x000a > AttachedPhyIdentifier: 13 > AttachedPhyInfo Reason: Loss DWORD Sync (0x14) > ProgrammedLinkRate: 6.0Gbps (0xa8) > HwLinkRate: 6.0Gbps (0xa8) > ChangeCount: 1 > Flags: 0x1 > PhyInfo Reason: Power On (0x10000) > NegotiatedLinkRate: 6.0Gbps (0xaa) > mps0: Found device ,End Device> <6.0Gbps> <0x000f> <2/2> > mps0: Triggering rescan of 0:3:-1 > mps0: SAS Device Page 0 : > Slot: 3 > EnclosureHandle: 0x2 > SASAddress: 0x5000c5002c545701 > ParentDevHandle: 0xa > PhyNum: 7 > AccessStatus: 0x0 > DevHandle: 0x10 > AttachedPhyIdentifier: 0x0 > ZoneGroup: 0 > DeviceInfo: c01,End Device > Flags: 0x1 > PhysicalPort: 0 > MaxPortConnections: 1 > DeviceName: 0x0 > PortGroups: 4 > DmaGroup: 0 > ControlGroup: 4 > mps0: SAS PHY Page 0 : > OwnerDevHandle: 0x0001 > AttachedDevHandle: 0x000a > AttachedPhyIdentifier: 12 > AttachedPhyInfo Reason: Loss DWORD Sync (0x14) > ProgrammedLinkRate: 6.0Gbps (0xa8) > HwLinkRate: 6.0Gbps (0xa8) > ChangeCount: 1 > Flags: 0x1 > PhyInfo Reason: Power On (0x10000) > NegotiatedLinkRate: 6.0Gbps (0xaa) > mps0: Found device ,End Device> <6.0Gbps> <0x0010> <2/3> > mps0: Triggering rescan of 0:6:-1 These two disks don't have PHY pages: > mps0: SAS Device Page 0 : > Slot: 7 > EnclosureHandle: 0x2 > SASAddress: 0x5000c5002c5454bd > ParentDevHandle: 0xa > PhyNum: 10 > AccessStatus: 0x0 > DevHandle: 0x11 > AttachedPhyIdentifier: 0x0 > ZoneGroup: 0 > DeviceInfo: c01,End Device > Flags: 0x1 > PhysicalPort: 0 > MaxPortConnections: 1 > DeviceName: 0x0 > PortGroups: 4 > DmaGroup: 0 > ControlGroup: 4 > mps0: SAS Device Page 0 : > Slot: 6 > EnclosureHandle: 0x2 > SASAddress: 0x5000c5002c4f5561 > ParentDevHandle: 0xa > PhyNum: 16 > AccessStatus: 0x0 > DevHandle: 0x12 > AttachedPhyIdentifier: 0x0 > ZoneGroup: 0 > DeviceInfo: c01,End Device > Flags: 0x1 > PhysicalPort: 0 > MaxPortConnections: 1 > DeviceName: 0x0 > PortGroups: 4 > DmaGroup: 0 > ControlGroup: 4 Ken -- Kenneth Merry ken@FreeBSD.ORG