From owner-freebsd-questions@FreeBSD.ORG Wed Oct 22 06:57:12 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E22116A4B3 for ; Wed, 22 Oct 2003 06:57:12 -0700 (PDT) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89C5543FA3 for ; Wed, 22 Oct 2003 06:57:09 -0700 (PDT) (envelope-from heartley@earthlink.net) Received: from sdn-ap-003dcwashp0270.dialsprint.net ([63.188.17.16] helo=taz.local) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1ACJTz-0007CV-00; Wed, 22 Oct 2003 06:57:04 -0700 From: Marshall Heartley To: "M.D. DeWar" In-Reply-To: <002f01c398a3$96aa4be0$6a1fa8c0@ocfl061> References: <1066772319.2046.24.camel@taz.local> <20031022155037.1d6ecf07.doublef@tele-kom.ru> <1066828441.3555.11.camel@taz.local> <002f01c398a3$96aa4be0$6a1fa8c0@ocfl061> Content-Type: text/plain Message-Id: <1066831021.1860.3.camel@taz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Rubber Turnip www.usr-local-bin.org Date: Wed, 22 Oct 2003 09:57:02 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: Need some insight on error messages that I am getting. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2003 13:57:12 -0000 On Wed, 2003-10-22 at 09:51, M.D. DeWar wrote: > I get these all the time. > I was told that it was possibly in the cable or motherboard controller. > The point was the drive was like ata 100 and the cable was ata 33 or the mb > did not support the ata mode of the drive. > I never confirmed it cuz when I put in a maxtor ata controller I lost all my > slices and had to go back to the mb controller. > > I think that the person that sent me that was off this list so it might be > in the archives. Thanks, I used atacontrol to change the mode in which the drive was working and the errors went away. I changed it from UDMA66 to PIO0 and no more messages. My motherboard controller will handle the UDMA66 mode so I do not know what the deal is. My drives are on a ATA100 cable. I will look a little deeper so see what else is causing this. I would much rather operate the drive in UDMA66 mode than PIO0. I will take a look in the archives to see what I can dig up. Marshall