From owner-freebsd-questions Tue Jun 17 13:07:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA04111 for questions-outgoing; Tue, 17 Jun 1997 13:07:40 -0700 (PDT) Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA04104 for ; Tue, 17 Jun 1997 13:07:36 -0700 (PDT) Received: from localhost (fbsdlist@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id QAA18811 for ; Tue, 17 Jun 1997 16:07:30 -0400 (EDT) Date: Tue, 17 Jun 1997 16:07:30 -0400 (EDT) From: Cliff Addy To: questions@freebsd.org Subject: SCSI bus timeouts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What has happened to my lovely little FreeBSD systems? They used to be so stable, so rock-solid reliable. Now they don't even stay up a day anymore. What happened? I "upgraded" them to 2.2, since then my life has been hell. I thought 2.2.2 was going to fix the problem with lockups during tape backups. But the newest system, running the latest code off the ftp site, just died with that same "SCSI bus timed out" error message. This was not a "heavily loaded" system, it was brand new and doing *nothing* but a backup. On our systems, about 35% of our backups to tape lock up the machine with the bus timeouts. Does anyone have an idea on how to fix this? We're running the same hardware that stayed up for weeks at a time under 2.1.5, Cyrix 6x86, 64MB, Adaptec 2940UW, Seagate HDD and DAT.