On Wed, Jun 25, 2003 at 01:41:51AM -0400, Sean Sweda wrote:
> [...]
> 
> What could be causing this?  This machine is co-located, so I don't have
> easy physical access to the machine.  Also, I don't appear to have an
> old dmesg left around from a 1.5.2 boot.  I haven't yet tried hardwiring

Do you remember if you used the siop driver, or ncr ?

> a st device to scsi ID 5 on the mesh controller.  Would this even help
> if the kernel isn't recognizing the tape drive as a sequential device?

No

> [...]
> scsibus0: waiting 2 seconds for devices to settle...
> sd0 at scsibus0 target 0 lun 0: <QUANTUM, VIKING II 4.5WSE, 5520> SCSI2 0/direct fixed
> sd0: 4350 MB, 8338 cyl, 5 head, 213 sec, 512 bytes/sect x 8910423 sectors
> sd0: sync (50.0ns offset 16), 16-bit (40.000MB/s) transfers, tagged queueing
> sd1 at scsibus0 target 1 lun 0: <IBM, DNES-309170W, SA30> SCSI3 0/direct fixed
> sd1: 8748 MB, 11474 cyl, 5 head, 312 sec, 512 bytes/sect x 17916240 sectors
> sd1: sync (50.0ns offset 16), 16-bit (40.000MB/s) transfers, tagged queueing
> scsibus1: waiting 2 seconds for devices to settle...
> sd2 at scsibus1 target 5 lun 0: <, , > SCSI0 0/direct fixed
> sd2: drive offline

Strange, it looks like the adapter is getting all 0 in anserws to commands
sent to the adapter.
Is it a narrow or wide device ?
Can you try
scsictl sd2 identify
scsictl sd2 tur

and post the result ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--