From owner-freebsd-hackers Sun Dec 5 13:58:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak2.texar.com (pak2.texar.com [216.208.160.130]) by hub.freebsd.org (Postfix) with ESMTP id 9475B15464 for ; Sun, 5 Dec 1999 13:58:11 -0800 (PST) (envelope-from dseg@pak2.texar.com) Received: from localhost (dseg@localhost) by pak2.texar.com (8.9.2/8.8.3) with ESMTP id QAA17146; Sun, 5 Dec 1999 16:57:36 -0500 (EST) Date: Sun, 5 Dec 1999 16:57:36 -0500 (EST) From: Dan Seguin To: "Ronald F. Guilmette" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Strange SCSI sickness In-Reply-To: <22337.944430730@monkeys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >1. It's quite possible that the drive and/or the cabling in this > > system has been defective all along. > > I suspect not, based upon the history. > > I think that the drive and/or controler has just developed this sickness > within the past 24 hours. > > >2. It's equally possible that the linux driver simply doesn't report > > the errors but, as FreeBSD does, retries the failing operations. > > This would result in a system which appeared to work just fine, > > just more slowly at times (which would probably not even be > > noticed). > > FreeBSD was also perfectly happy with this drive (and controller) for > weeks... up until last night. > > >3. Any system I saw spitting out errors like this would get the following > > treatment, in roughly this order: > > (I now think that my first order of business should be to start making > backup tapes as quick as I can. :-) > > > 3a) Complete check of all cables and the seating of connectors. > > > > 3b) Examination of the drive(s) in question for any cooling or > ^^^^^^^ > > The drive is mounted in a crappy external box with perfectly lousy > ventilation. > > I just touched the drive and guess what... It's hot as Hades. > > I think I found my answer. > [stuff snipped] If it already hasn't been done, we should capture the procedure that Jordan posted, added to by Matt and maybe post it to the troubleshooting part of the guide(s). Unlike some of us who've been fooling with computers since pre-1985, this standard operating procedure may not be second nature. -------------------------------------------------------------------------------- Dan Seguin Texar Software, Corporation. The trouble with doing something right the first time is that nobody appreciates how difficult it was. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message