From owner-freebsd-hackers Mon Nov 27 15:53:46 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA11487 for hackers-outgoing; Mon, 27 Nov 1995 15:53:46 -0800 Received: from nwnexus.wa.com (nwnexus.wa.com [192.135.191.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id PAA11479 for ; Mon, 27 Nov 1995 15:53:42 -0800 Received: by nwnexus.wa.com id AA15589 (5.65c/IDA-1.4.4 for freebsd-hackers@freebsd.org); Mon, 27 Nov 1995 15:53:34 -0800 Received: (from gfm@localhost) by angel.readybox.com (8.6.8/8.6.6) id PAA00293 for freebsd-hackers@freebsd.org; Mon, 27 Nov 1995 15:42:46 -0800 Date: Mon, 27 Nov 1995 15:42:46 -0800 From: Frank McCormick Message-Id: <199511272342.PAA00293@angel.readybox.com> To: freebsd-hackers@freebsd.org Subject: Re: 2.0.5R: SCSI hang and panic... HELP Sender: owner-hackers@freebsd.org Precedence: bulk Mike Borowiec wrote > > I'm having tape drive problems... > I'm trying to back-up my 2.0.5R machine to 8mm Exabyte, but every time > I get close to finishing my tar backup, this happens: > > ahc0: target 0, lun 0 (sd0) timed out > ahc0: target 0, lun 0 (sd0) timed out > ...[repeats]... > > SCSI bus hangs, and I'm forced to reboot system... > > [...] > > The machine is a 486DX50 EISA/VESA w/16MB, with an Adaptec 2742AT EISA > SCSI card. > Responses that just say, "Me, too," aren't particularly useful, I know. However, at the risk of uselessness, I'd like to say, "Me, too." I have similar symptoms under an aging 1.1R box. Similarities include having an EISA/VESA motherboard, an Adaptec host adapter and an Exabyte tape drive. The differences include having a 1542B, rather than Mike's 2742AT, and a 4mm Exabyte. (Exabyte's 4mm products are rebadged from some corporate acquisition. The name of the actual manufacturer of what is now the Exabyte 4mm line escapes me.) The part that strikes me as even weirder is that my box makes it through a full backup about three times out of four. The symptoms described above arise for me about a quarter of the time. When it does fall over, I get a lot of spooky console messages about the 1542 debugger being called. As far as I know, I've never lost any data, but it's an unpleasant phenomenon. Anyone with solutions gets free beer in heaven. Frank McCormick