From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 9 18:26:24 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D5E116A4CE for ; Sat, 9 Oct 2004 18:26:24 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5CA843D1D for ; Sat, 9 Oct 2004 18:26:23 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i99IQIeJ052873; Sat, 9 Oct 2004 20:26:20 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <41682D3F.4060902@DeepCore.dk> Date: Sat, 09 Oct 2004 20:26:07 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: miha@ghuug.org References: <200410081937.15068.miha@ghuug.org> In-Reply-To: <200410081937.15068.miha@ghuug.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: hackers@freebsd.org Subject: Re: ad0: FAILURE - WRITE_DMA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Oct 2004 18:26:24 -0000 Mikhail P. wrote: > Hi, >=20 > This question probably has been discussed numerous times, but I'm somew= hat=20 > unsure what really causes ATA failures.. >=20 > I have pretty basic server here which has two IDE drives - each is 200G= B.=20 > System is FreeBSD-5.2.1-p9 > That server has been setup about 9 months ago, and just about 3 months = ago my=20 > logs quickly filled up with: > ad0: FAILURE - WRITE_DMA status=3D51 error=3D10=20 > LBA=3D268435455 Hmm, that means that the drive couldn't find the sector you asked for. Now, what has me wondering is that it is the exact sector where we=20 switch to 48bit adressing mode. Anyhow, I've just checked on the old=20 Maxtor preproduktion 48bit reference drive I have here and it crosses=20 the limit with no problems. What controller are you using ? not all supports 48bit mode correctly.. --=20 -S=F8ren