> I've got an IBM 18G scsi disk with SCA connector, and an SCA<->50-pin
> adapter.  This is connected to the internal scsi bus of my Power
> Tower Pro (OF 1.0.5, if it matters... mesh0), and no matter what
> jumpers I jump, it comes up as 'drive offline':

> sd1 at scsibus1 target 5 lun 0: <IBM, DXHS, 0430> disk fixed
> sd1: drive offline

> HOWEVER, if I use 'scsictl sd1 start', then use scsictl to detach and
> rescan the bus, the drive works OK: [...]

> Anyone know what I can do here?  I'd really, really like to use this
> 18G disk instead of the one that's there.

You quite likely can just go ahead and use it.  Have you tried?

I have an IBM drive on a SPARCstation IPX that has similar issues - it
is reported as offline by the boot-time device scan.  However, it isn't
offline; (a) it's the boot drove, from which the kernel was just
loaded, so it can't very well be offline; and (b) it works just fine to
continue to use it as if it weren't offline.

Thus, I feel reasonably sure this is some kind of MI SCSI issue, so
I've copied in tech-kern and set reply-to there.

I can't very well try your "detach and rescan" trick since in my case,
it's the drive with / on it - but since it works as /, it clearly is
not truly offline.

Interestingly, I have two other drives on that machine which probe just
fine:

scsibus1: waiting 2 seconds for devices to settle...
scsibus0: waiting 2 seconds for devices to settle...
sd1 at scsibus1 target 0 lun 0: <SEAGATE, ST32550N SUN2.1G, 0416> disk fixed
sd1: 2048 MB, 3511 cyl, 11 head, 108 sec, 512 bytes/sect x 4194995 sectors
sd1: sync (100.00ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing
sd2 at scsibus1 target 1 lun 0: <SEAGATE, ST15230N, 0498> disk fixed
sd2: 4095 MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sect x 8386733 sectors
sd2: sync (100.00ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing
sd0 at scsibus0 target 0 lun 0: <IBM, MXVS36D, 0100> disk fixed
sd0: drive offline
sd0: async, 8-bit transfers, tagged queueing

(The odd order is because I have scsibus0 and sd0 nailed down to
particular hardware in my config, but the device behind scsibus1 is
found before the device behind scsibus0.)

My sd0 is also an IBM drive.  I'm not sure what its' model number is,
unless it's the DMVS I see after "Type:".  You can find a scan of its
sticker in ftp.rodemts.montreal.qc.ca:/mouse/misc/IBM-drive/ in various
formats (GIF, JPG, PBM).

I don't see any statement of what NetBSD version you're using; I'm
using 2.0 on the machine in question.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B