From owner-freebsd-questions@FreeBSD.ORG Sat Nov 15 09:57:13 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 8CBBB16A4CF for ; Sat, 15 Nov 2003 09:57:13 -0800 (PST) Received: from lakemtao06.cox.net (lakemtao06.cox.net [68.1.17.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41C3F43F85 for ; Sat, 15 Nov 2003 09:57:12 -0800 (PST) (envelope-from kitbsdlists@HotPOP.com) Received: from fortytwo ([68.109.49.234]) by lakemtao06.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20031115175711.DWOP24575.lakemtao06.cox.net@fortytwo>; Sat, 15 Nov 2003 12:57:11 -0500 Date: Sat, 15 Nov 2003 11:55:58 -0600 From: Vulpes Velox To: "Jaques du Plessis" Message-Id: <20031115115558.386d7ff1.kitbsdlists@HotPOP.com> In-Reply-To: References: X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: HI ATA0 Resseting Device Error 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: Sat, 15 Nov 2003 17:57:13 -0000 On Thu, 13 Nov 2003 19:29:19 +0200 "Jaques du Plessis" wrote: > Hi i have found the following error on 4.8 4.9 but 5.1 > works except that the bootloader in 5.1 doesnt work many > other people found the same problem thought it would be > sorted in 4.9.. > > What can i do to avoid the ATA0 Resetting Device in 4.9? If find it a little odd that it happens in 4.8/9 but not in 5.1. I have seen something like this twice. Once was bad cables and the other time the drive was getting ready to die. Are they both on the same drive? If so I would really begin suspecting that there may be a drive problem... such as the disk going bad in a spot. I have had this happen to me one, the drive for the most part would read everything fine till it got to one part, thankfully I was able to replace it in time befor it totally failed. You may want to check around on current and stable lists if the hardware checks out good.