Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Feb 2012 10:21:56 -0500
From:      Douglas Gilbert <dgilbert@interlog.com>
To:        "Desai, Kashyap" <Kashyap.Desai@lsi.com>
Cc:        "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org>, "McConnell, Stephen" <Stephen.McConnell@lsi.com>
Subject:   Re: LSI2008 controller clobbers first disk with new LSI mps driver
Message-ID:  <4F450814.4020100@interlog.com>
In-Reply-To: <B2FD678A64EAAD45B089B123FDFC3ED72B96D347BB@inbmail01.lsi.com>
References:  <CAAAm0r2NFhF=eh2bOPMnVN8E6e2o0KfaST0N-M_gWoJHpFOLmQ@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D344F2@inbmail01.lsi.com> <CAAAm0r02bXNve6Do5C1m1RyzLhWA9xx97KKMeLhcHC66U2SF4g@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D34500@inbmail01.lsi.com> <CAFPOs6pwb44oNabH5vabDPJyFutMKa5mhgvHY=HkQVpV20YiYw@mail.gmail.com> <CAAAm0r1pWN-F=madGdk7N%2BoRuZmSD5_MAYwLh6By126L0CTGuw@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D34558@inbmail01.lsi.com> <CAAAm0r1x15_ho2MD0tX7Y7A6mnU2N6zihNOz_Qz=jpsyBkDCWQ@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D3455B@inbmail01.lsi.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D34626@inbmail01.lsi.com> <CAAAm0r3_S2jTG=Te4UhLqHPqiXq7_aAOHNp=W3jb4KLJx9PTRg@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D34748@inbmail01.lsi.com> <CAAAm0r3oRTcfipyVcp9nE1CL3dcK7cft8AUSf%2BfGYVK90b2A0w@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D347BB@inbmail01.lsi.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F450814.4020100>