>> 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 <, , >
>> sd1 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 <, , >
>> sd2 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.

Whoops!  That's what I get for typing in the damn message by hand... I
never got aound to setting up a serial console... if I had, that typo
wouldn't have occured.  I *am* getting sd0, 1, and 2.

The problem is that (now that I have corrected the output above!) I now get
the scsi_inqmatch lines and it hangs right after fscking sd0... when it
should check 2 more drives, and then go on into multi user mode.

Sorry for the confusion

(By the way, except for the scsi_inqmatch lines, this is as far as I can
remember, the exact output I got from the base 1.1 kernel.)

Aaron



--
Aaron Scott Magill                                             amagill@uiuc.edu
-------------------------------------------------------------------------------
}{  "I have SEEN evil!  I have SEEN horror!  I have seen the unholy maggots  }{
}{    which feast in the dark recesses of the human soul!  I have seen all   }{
}{  this, officer, but until today, I had never seen... YOU!" - Gomez Addams }{
-------------------------------------------------------------------------------