From owner-freebsd-questions Thu Aug 1 10:30:03 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26715 for questions-outgoing; Thu, 1 Aug 1996 10:30:03 -0700 (PDT) Received: from dan.emsphone.com (-@dan.emsphone.com [199.67.51.101]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA26699 for ; Thu, 1 Aug 1996 10:30:00 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.7.5/8.7.3) id MAA23363; Thu, 1 Aug 1996 12:29:34 -0500 (CDT) Message-Id: <199608011729.MAA23363@dan.emsphone.com> Subject: Re: DAT problems To: msmith@revolution.3-cities.com (Mark D. Smith) Date: Thu, 1 Aug 1996 12:29:34 -0500 (CDT) Cc: freebsd-questions@freeBSD.org In-Reply-To: <199608011531.IAA22990@revolution.3-cities.com> from "Mark D. Smith" at Aug 1, 96 08:31:11 am From: dnelson@emsphone.com (Dan Nelson) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-questions@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk in the last episode, Mark D. Smith said: > I've just put the Archive Python (now conner, er, Seagate ) on my > system. It's hung off of a Buslogic BT545S (bt0:) and on the same > SCSI bus as a Quantum Lightening 512MB SCSI2 drive and a Toshiba > 3401B CDROM. All 3 devices have correct termination, the HDD is > scsi id 6, cdrom is 0 and the tape is 1 and they're all on a 3 foot > long ribbon cable. > > The current problem is that when I try to say "tar cvf /dev/rst0 /cdrom" > ,that is, tar the whole CDROM to a tape for a friend that has a DAT > but no CDROM(don't ask me why), it goes for quite awhile then I start > getting errors like kernel: bt0: trying to reset, etc. Then, /usr, > which is on the SCSI drive, dissapears and if I'm lucky, I start getting > errors reporting BT0: trying to reset and calling debugger. If I'm > NOT lucky, it just reboots. Then I have to rebuild /usr. The same thing happens to me, but I'm using an internal Adaptec 1542CP, "ARCHIVE Python 25947-XXX 2.49" DAT drive. The lockups occur when reading tapes written on other drives. I think it's the drive locking up the SCSI bus, since if I unplug the SCSI cable from the drive, cycle power on the drive, and plug the SCSI cable back in, the bus frees up. In the syslog, I get: Jul 25 10:34:45 dan /kernel: st0(aha0:3:0): HARDWARE FAILURE asc:44,0 Internal target failure Jul 25 10:39:57 dan /kernel: st0(aha0:3:0): timed out Jul 25 10:40:03 dan /kernel: aha0: adapter not taking commands.. frozen?! (panic/drop to DDB. Reset tape drive, "C"ontinue from DDB, system continues as usual.) System is a Micron P100/PCI, FreeBSD 2.2-960612-SNAP, IDE disks. The 1542 is only used for the tape drive. -Dan Nelson dnelson@emsphone.com > So, question, is my trying to tar from a cd to a tape causing the hard > drive requests to time out and kill the drive or is my scsi bus going > whacko? > > Machine is: > 486DX4-100, generic mb clone > 32MB ram > Buslogic BT545S > Quantum Lightening 512MB SCSI hdd as /usr > Toshiba 3401B cdrom > Maynard/Archive/conner/Seagate Python 2GB 4mm DAT > Promise 2300+ EIDE card (bios disabled) > 2 each Western Digital 31200 HDDS 500MB as /