From owner-freebsd-stable Sat Nov 27 20:17:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by hub.freebsd.org (Postfix) with ESMTP id 7BA4414A0E for ; Sat, 27 Nov 1999 20:17:18 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id XAA94595; Sat, 27 Nov 1999 23:17:12 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14400.44231.893101.170807@trooper.velocet.net> Date: Sat, 27 Nov 1999 23:17:11 -0500 (EST) To: "Kenneth D. Merry" Cc: dgilbert@velocet.ca (David Gilbert), freebsd-stable@FreeBSD.ORG Subject: Re: ahc problems (with vinum?) In-Reply-To: <199911280410.VAA18887@panzer.kdm.org> References: <14400.40032.603375.82448@trooper.velocet.net> <199911280410.VAA18887@panzer.kdm.org> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Kenneth" == Kenneth D Merry writes: Kenneth> David Gilbert wrote... >> Several times, on a system I've been configuring and testing, I've >> got some maddening ahc0 messages. In general, they complain of a >> timeout on the bus (I think some packet got lost)... and x SCBs are >> aborted. >> >> At this point, some portion of the SCSI bus is unusable... and the >> machine eventually hangs due to this. It does claim that it's >> resetting channel A of the ahc0 controller, but I gather it doesn't >> do any good. >> >> I'm running 3.3-STABLE (as of thursday, I think) and am trying to >> format and test an 8-drive vinum RAID-5 array. Kenneth> You'll need to provide more information in order for anyone Kenneth> to make sense of your problem. Specifically, please post any Kenneth> and all relevant kernel messages, including your controllers Kenneth> and drives and the errors you've seen printed out, explain Kenneth> your SCSI bus configuration, where it is terminated, etc. Kenneth> The #1 cause of problems is cabling and termination. The Kenneth> second most common cause of problems is bogus drive firmware. Kenneth> In any case, check your cabling and termination, as that is Kenneth> most likely problem. Regardless of terminaion, the SCSI bus reset should clear things... the unit will run for hours just fine... get this one error and hang. It is difficult to copy down all the messages --- as they don't get copied into the logs (since the SCSI bus is locked). The controller is the 2940 U2W --- the one with a SE and an LVD connector. The LVD bus is connected to a professional 8 drive LVD case which is connected and terminated with the supplied cables. The SE connector is connected to a single drive. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message