> 
> > ncrscsi0 at mainbus0
> > scsibus0 at ncrscsi0
> > ncrscsi0 targ 0 lun 0: <QUANTUM, LP240S GM240S01X, 6.3> SCSI2 0/direct fixed
> > scsi_inqmatch: 2/0/0 <, , >
> > sd0 at scsibus0: 234MB, 1818 cyl, 4 head, 65 sec, 512 bytes/sec
> > ncrscsi0 targ 1 lun 0: <MAXTOR, 7345-SCSI, 1761> SCSI1 0/direct fixed
>            ^^^^^^
> > scsi_inqmatch: 2/0/0 <, , >
> > sd0 at scsibus0: 329MB, 2220 cyl, 4 head, 76 sec, 512 bytes/sec
> > ncrscsi0 targ 2 lun 0: <QUANTUM, LP240S GM240S01X, 6.3> SCSI2 0/direct fixed
>            ^^^^^^
> > scsi_inqmatch: 2/0/0 <, , >
> > sd0 at scsibus0: 234MB, 1818 cyl, 4 head, 65 sec, 512 bytes/sec
> 
> Multiple targets on a given SCSI address?  And they _all_ seem to get 
> called sd0!   Hmm.

Euwww!

I haven't looked at the SCSI code recently, but I've had lots of recent
"fun" with the autoconfig stuff. Looks like sd might not be coming up
as a "STAR" device, or that the unit # in the config data is not
getting incrimented right (it gets incrimented right after each new
device gets found, just before the attach call).

I've forgotten, is this a custom config'ed kernel, or a distributed
one?

Take care,

Bill