From owner-freebsd-questions Mon Feb 11 16:21:20 2002 Delivered-To: freebsd-questions@freebsd.org Received: from vms2.rit.edu (vms2.isc.rit.edu [129.21.3.9]) by hub.freebsd.org (Postfix) with ESMTP id 184D837B423 for ; Mon, 11 Feb 2002 16:20:51 -0800 (PST) Received: from sonic.rit.edu ([129.21.10.181]) by ritvax.isc.rit.edu (PMDF V5.2-32 #40294) with ESMTPA id <01KE5QES6WEUEPF5OG@ritvax.isc.rit.edu> for freebsd-questions@freebsd.org; Mon, 11 Feb 2002 19:20:47 EST Date: Mon, 11 Feb 2002 19:19:34 -0500 From: Matt Penna Subject: Re: random reboot problem In-reply-to: X-Sender: mdp1261@vmspop.isc.rit.edu To: freebsd-questions@freebsd.org Cc: David Winkler Message-id: <5.1.0.14.2.20020211191118.029b8970@vmspop.isc.rit.edu> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 05:00 PM 2/11/02 -0600, David Winkler wrote: >Any information on a fix for this problem, or where to check beyond >replacing >hardware ( have replaced drives in the 4.3 machine with no effect ) would >be greatly appreciated. David, You said "beyond replacing hardware," but you did not mention these points specifically, so I figured I would throw them out, anyway. I've had several similar problems on systems with unreliable SCSI buses. This was caused by a number of things, sometimes due to bad drives - a possibility which you're pretty much eliminated - but more often something less obvious like a bad cable, improper termination, or low-quality hardware. There was one system where I had (7) 80-pin SCA drives connected to a 68 pin cable with more than one brand of converter, and it turns out one of the brands was very low quality; it introduced so much latency as to break the SCSI bus and resulted in some similar errors as you quoted, though in my case I couldn't get FreeBSD to install, let alone boot. I have never seen those kinds of timeout errors in any case where the hardware was working perfectly, so my advice is to suspend disbelief and triple-check everything. Good luck to you! Maybe someone else can offer an alternative suggestion. Matt -- Matt Penna mdp1261@rit.edu ICQ: 399825 S0ba on AOLIM "The trouble with computers, of course, is that they're very sophisticated idiots." -Dr. Who To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message