Nick Holland wrote: ... > Ken was zooming in on something, I'm looking at something I am finding > even stranger:
(and now that I looked at the man page for mpt(4), I'm realizing that Ken's got a lot more credibility on this topic than I do! :) > sd0 at scsibus1 targ 0 lun 0: <LSILOGIC, 1030 IM, 1000> SCSI2 0/direct fixed > sd0: 34715MB, 34715 cyl, 16 head, 128 sec, 512 bytes/sec, 71096320 sec total > sd1 at scsibus1 targ 2 lun 0: <IBM-ESXS, MAS3367NC FN, C901> SCSI3 0/direct > fixed > sd1: 34715MB, 27150 cyl, 4 head, 654 sec, 512 bytes/sec, 71096640 sec total > > Since when did LSILOGIC start making HARD DISKS with the exact same > model number as their SCSI adapter?? Something is going seriously > wrong there. (I'm guessing since you have three "identical" machines, > they probably have six identical HDs). Briefly, ever so briefly, when I was writing that reply, it occurred to me that mpt(4) could be a RAID controller, not just a SCSI adapter. I promptly forgot this. A developer who knows this product much better than I indicated in a private mail that this is (or may be) the case, in which case, yes, having the DRIVE SET show up as brand/model LSILOGIC isn't unexpected. But that doesn't explain the second drive...if it is part of a RAID set, it shouldn't show up in dmesg. This person felt it could well be a misconfiguration of the RAID set on this controller. I'm trying to decide if I should take him up on the non-trivial bet that it "is not an OpenBSD issue" :) Nick.
