From owner-freebsd-questions@FreeBSD.ORG Thu Sep 2 13:51:01 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EF5610657CE for ; Thu, 2 Sep 2010 13:51:01 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.41]) by mx1.freebsd.org (Postfix) with ESMTP id 692EE8FC17 for ; Thu, 2 Sep 2010 13:51:01 +0000 (UTC) Received: (qmail 6463 invoked from network); 2 Sep 2010 13:51:00 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 2 Sep 2010 13:51:00 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id A7E2C50852; Thu, 2 Sep 2010 09:50:58 -0400 (EDT) From: Lowell Gilbert To: Xihong Yin , Mike Jeays References: <201009012243.57415.mike.jeays@rogers.com> Date: Thu, 02 Sep 2010 09:50:58 -0400 In-Reply-To: <201009012243.57415.mike.jeays@rogers.com> (Mike Jeays's message of "Wed, 1 Sep 2010 22:43:56 -0400") Message-ID: <44tym89rul.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: error - ad2: FAILURE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2010 13:51:01 -0000 Mike Jeays writes: > On September 1, 2010 10:29:42 pm Xihong Yin wrote: >> Hi, >> >> I received the following error when I try to access files in some of the >> directories in /usr and when the computer boots. ad2s1f is mounted on >> /usr. >> >> ad2: FAILURE - READ_DMA status=51 error=40 >> LBA=37370159 g_vfs_done():ad2s1f[READ(offset=15415558144, >> length=16384)]error = 5 >> >> Is this a sign of hard drive failure? Can I fix the error or do I have to >> replace the hard drive? > I would think it is a hardware error, and the disk has run out of replacement > sectors. If possible, it should be replaced, and any valuable data copied to > somewhere safe, as soon as possible. Not necessarily. This is a read error, so replacement sectors wouldn't help anyway. The problematic files might get fixed by the disk if they were rewritten. A SMART report (e.g., from sysutils/smartmontools) might give more information about the condition of the drive. None of which is to say that it isn't worrying, or that backing up valuable data isn't called for (even more so than usual). Make sure you have good backups before you do anything else.