LSI2008 controller clobbers first disk with new LSI mps driver

[Jason Wolfe]

Kashyap,

The boot drive is always the first disk, enclosure 0, and should be
da0.  It is the same model as the other 11 disks also.

PCI  ENCL LUN VENDOR   PRODUCT          PRODUCT     SIZE \
SLOT SLOT NUM NAME     IDENTIFIER       REVISION    NVDATA
---- ---- --- -------- ---------------- ----------- ---------
  5           LSI      SAS2008-IT       10.00.02.00  0A:02:00:04
  5    0   0  SEAGATE  ST91000640SS     0001           953 GB
<-------- boot drive/wanted da0/masked by ses device
  5    1   0  SEAGATE  ST91000640SS     0001           953 GB
  5    2   0  SEAGATE  ST91000640SS     0001           953 GB
  5    3   0  SEAGATE  ST91000640SS     0001           953 GB
  5    4   0  SEAGATE  ST91000640SS     0001           953 GB
  5    5   0  SEAGATE  ST91000640SS     0001           953 GB
  5    6   0  SEAGATE  ST91000640SS     0001           953 GB
  5    7   0  SEAGATE  ST91000640SS     0001           953 GB
  5    8   0  SEAGATE  ST91000640SS     0001           953 GB
  5    9   0  SEAGATE  ST91000640SS     0001           953 GB
  5   10   0  SEAGATE  ST91000640SS     0001           953 GB
  5   11   0  SEAGATE  ST91000640SS     0001           953 GB

Attached is the verbose dmesg with the mps.debuglevel set.

Jason

On Fri, Feb 17, 2012 at 11:54 AM, Desai, Kashyap <Kashyap.Desai at lsi.com> wrote:
>
>
> OK, So you have your / partion on da0. (this drive is attached to which phy ?)
> Since all Drive are from same manufacture and Same variant, it is difficult to collect data from this dmesg log.
>
> Can you put the following in /boot/loader.conf:
>
> hw.mps.debug_level=0xd
>
> Here is some context of the target id generation logic in <mps>
>
> Older driver available in FreeBSD-8 Stable, will not have any logic in driver to generate Target id mapping.
> So it will give da0 device name to the drive which is detected First by FW.
>
> With newer driver story is little different. Drive will find the DPM page in FW for particular drive detected by FW and it will do mapping
> Either by Enclosure slot mapping / Device mapping.
>
> I am trying to see how best I can solve your issue.
>
> Also, In this case which device has actually you wants to be da0 ? ( I mean boot driver has got which device name ? )
>
> Let me see your another dmesg output.
>
> ` Kashyap
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mpsdmesg
Type: application/octet-stream
Size: 82779 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-scsi/attachments/20120217/462dcc20/mpsdmesg.obj