Date: Fri, 25 Feb 2000 12:55:43 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: "Walter A. Roberts" <wroberts@med.wayne.edu> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Fw: Adaptec 1542c and Exabyte 8200/tar: Device not config Message-ID: <20000225125543.A48858@panzer.kdm.org> In-Reply-To: <004301bf7f15$5a0e7180$986f4acf@walt>; from wroberts@med.wayne.edu on Thu, Feb 24, 2000 at 05:20:19PM -0500 References: <004301bf7f15$5a0e7180$986f4acf@walt>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 24, 2000 at 17:20:19 -0500, Walter A. Roberts wrote: > Dear folks: > > I was referred to this list for possible help on the problems with a recent > installation of 3.2 BSD related to a need for SCSI. I swapped out my > adaptec 1502 cheapie for a 1542c since the CAM drivers don't support the > 1502 and I had the 1542c on the shelf, thinking this would be easy. Sigh. > > I would be willing to write a driver for the 1502, but I've never written > UNIX drivers, just VMS drivers so I'm not sure how steep the learning curve > would be, but if any of you'd be willing to coach a little I could give it a > whack. FreeBSD 3.4 and FreeBSD-current have a driver for the AIC-6260 and 6360 chips that are on the 1502, so you don't need to write a driver. :) > I mainly (actually only) need the scsi on the UNIX side to read a tar file > off an EXABYTE EXB-8200 scsi drive. If there's no hope for the present > situation, if anyone knew of a way to get the stuff on the MS side onto > other media (via the 1502/EXB), without a lot of contortions that would work > too, although I know this part is way off the track of this list. > > Thanks for any help you can be. Technical details follow. It should be possible to use an Exabyte 8200. They're known to be rather cantankerous, though. > >> Problem: Swapped ADAPTEC 1502 out to use ADAPTEC 1542C after installing > >> 3.3.x and can't get tar (or mount or mt) to access the EXABYTE 8200 > >> (scsi device 4) to read the device. > >> > >> History: Since no device drivers appeared to be available for the 1502 > >> and I have tarred stuff on 8 mm (DEC ULTRIX tarred files), I tried to > >> install the AHA-1542C board and an EXABYE-8200 (taken from the VAX) to > >> read the files. > >> > >> The AHA installed and appeared to be properly identified by FreeBSD at > >> all the right spots. During boot it tickled the exabyte numerous times > >> (slowly), and came up fine. > >> > >> Camcontrol dev will show the aha1542 device on scbus0 but no devices. > >> Camcontrol periph will show the aha1542 likewise. > >> Camcontrol scan will then show the exabyte-8200 and hangs at this > >> point. Kill -9 won't make this process go away. Only reboot does. Does camcontrol rescan hang the whole system, or is it just that process that is hung, or what? > >> Tar commands tried: > >> tar -tf /dev/rsa0-6 > >> (likewise mount and mt) > > > >Could you post the dmesg(8) output? > >-- > >Crist J. Clark cjclark@home.com [ ... ] > aha0 at 0x330-0x333 irq 9 drq 5 on isa > aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host Adapter, SCSI ID 7, 16 CCBs > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > Waiting 5 seconds for SCSI devices to settle > (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out > (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out > aha0: No longer in timeout > (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out > (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out [ ... ] > options SCSI_DELAY=5000 #Be less pessimistic Joe SCSI device I would suggest increasing this to at least 30 seconds. Exabyte 8200's take a long time to recover from a reset. If 30 seconds doesn't work, try 60 seconds. The delay above is in milliseconds, so it'll need to be 30000 or 60000, respectively. > camcontrol devlist -v [on startup] > > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > scbus0 on aha0 bus 0: > < > at scbus0 target -1 lun -1 () > > camcontrol devlist -v [after issuing camcontrol rescan scbus0] > > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > scbus0 on aha0 bus 0: > <EXABYTE EXB-8200 425A> at scbus0 target 0 lun 0 (probe0) > < > at scbus0 target -1 lun -1 () That definitely looks like a bug. Essentially the probe peripheral isn't going away for some reason, and the device isn't getting announced to any of the other peripherals. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000225125543.A48858>