From owner-freebsd-hackers Thu Jun 19 17:51:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA00559 for hackers-outgoing; Thu, 19 Jun 1997 17:51:00 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA00540; Thu, 19 Jun 1997 17:50:55 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0werrr-0003js-00; Thu, 19 Jun 1997 17:47:59 -0700 Date: Thu, 19 Jun 1997 17:47:59 -0700 (PDT) From: Tom Samplonius To: Jared Proudfoot cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: SCSI Problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Jun 1997, Jared Proudfoot wrote: > > Greetings, > > I've been looking through the mailing list archives and I've noticed that > a lot of people have been experiencing the damn SCSI problems that I have > been having recently. > > I'm currently running FreeBSD 2.2.1-RELEASE on a P166 with 128MB RAM, an > Adaptec 2940 UW controller, 2 Quantam Atlases, 1 Quantam Grand Prix and an > IDE Quantum Sirocco. You should probably upgrade to 2.2.2 The errors, look really familar. Is sd1 the Grand Prix? Is it always sd1? I found the Grand Prix to be very unreliable. So if sd1 is the Grand Prix, and sd1 is always the cause, rip it out. Also, 2.2.2-stable is better able to handle recovery. The drive still times out, and the system will freeze for a couple for seconds, and continue on. Tom