From owner-freebsd-questions@FreeBSD.ORG Tue Aug 17 16:08:25 2004 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 2432016A4CE for ; Tue, 17 Aug 2004 16:08:25 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3CEE43D67 for ; Tue, 17 Aug 2004 16:08:24 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.11/8.12.11) id i7HG8J5t016089; Tue, 17 Aug 2004 11:08:19 -0500 (CDT) (envelope-from dan) Date: Tue, 17 Aug 2004 11:08:19 -0500 From: Dan Nelson To: doug@polands.org Message-ID: <20040817160819.GA53307@dan.emsphone.com> References: <20040817155512.GB21780@omniresources.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040817155512.GB21780@omniresources.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: questions@freebsd.org Subject: Re: Harddrive beginning to expire? 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: Tue, 17 Aug 2004 16:08:25 -0000 In the last episode (Aug 17), doug@polands.org said: > I'm seeing this entry in my /var/log/messages approx. every three hours: > > Aug 17 06:09:07 judea /kernel: (da5:ahc0:0:5:0): WRITE(06). CDB: a 0 1 f9 a 0 > Aug 17 06:09:07 judea /kernel: (da5:ahc0:0:5:0): RECOVERED ERROR asc:5d,0 > Aug 17 06:09:07 judea /kernel: (da5:ahc0:0:5:0): Failure prediction threshold exceeded field replaceable unit: 1 > Aug 17 09:28:52 judea /kernel: (da5:ahc0:0:5:0): WRITE(06). CDB: a 0 1 f9 a 0 > Aug 17 09:28:52 judea /kernel: (da5:ahc0:0:5:0): RECOVERED ERROR asc:5d,0 > Aug 17 09:28:52 judea /kernel: (da5:ahc0:0:5:0): Failure prediction threshold exceeded field replaceable unit: 1 > > This 4.9-STABLE box is running 7 SCSI drives in a vinum stripped array. > Question, is this the beginning of the end for drive da5? It probably still has some life left in it. It looks like you don't have automatic write reallocation enabled, since the block number is the same on both requests. You can enable it by running "camcontrol mode da5 -e -m 1 -P 3", and setting AWRE to 1. That will let the drive remap that disk block to a spare one. You can monitor how many blocks have been reallocated by viewing the grown defect list: "camcontrol defects da5 -f phys -G". If you use -P instead of -G, you can see the primary defect list, which is a list of all the bad blocks found when the disk was shipped. -- Dan Nelson dnelson@allantgroup.com