From owner-freebsd-questions Tue Mar 14 20:19: 7 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 2EF0237B86B for ; Tue, 14 Mar 2000 20:19:03 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id RAA50630; Wed, 15 Mar 2000 17:18:41 +1300 (NZDT) Message-Id: <200003150418.RAA50630@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: Greg Lehey Date: Wed, 15 Mar 2000 17:18:36 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: vinum and "recovered error" Reply-To: dan@freebsddiary.org Cc: freebsd-questions@FreeBSD.ORG In-reply-to: <20000313214753.B475@mojave.worldwide.lemis.com> References: <200003131821.HAA40076@ducky.nz.freebsd.org>; from dan@freebsddiary.org on Tue, Mar 14, 2000 at 07:21:46AM +1300 X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13 Mar 00, at 21:47, Greg Lehey wrote: > On Tuesday, 14 March 2000 at 7:21:46 +1300, Dan Langille wrote: > > Hi folks, > > > > This morning I found the following in my logs: > > > > Mar 14 00:27:42 fred /kernel: (da2:ncr0:0:4:0): READ(06). CDB: 8 18 2a 99 > > 70 0 Mar 14 00:27:43 fred /kernel: (da2:ncr0:0:4:0): RECOVERED ERROR > > info:182ae9 asc:17,1 Mar 14 00:27:43 fred /kernel: (da2:ncr0:0:4:0): > > Recovered data with retries sks:80,1 > > > > Mar 14 01:06:16 fred /kernel: (da1:ncr0:0:2:0): READ(06). CDB: 8 4 14 a9 > > 48 0 Mar 14 01:06:16 fred /kernel: (da1:ncr0:0:2:0): RECOVERED ERROR > > info:414b0 asc:17,1 Mar 14 01:06:16 fred /kernel: (da1:ncr0:0:2:0): > > Recovered data with retries sks:80,3 > > > > da2 is the second of a two disks which are used by vinum. Should > > I be worried about the above messages? > > Yes, there's cause for concern, but not because of Vinum. You should > check whether you have ARRE and AWRE set on the drive. If not, your > disk may be on the way out. And if they are set? See below. > Here's information about ARRE and AWRE from "The Complete FreeBSD": [partial snip] > # camcontrol modepage da1 -m 1 -e -P 3 Here are my settings: AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 1 TB (Transfer Block): 0 EER (Enable Early Recovery): 0 PER (Post Error): 1 DTE (Disable Transfer on Error): 0 DCR (Disable Correction): 0 Read Retry Count: 18 Write Retry Count: 18 I notice some values missing from your example. The above is an old 1G SCSI drive. Would that explain the missing options? The following is a list of the missing options: > RC (Read Continuous): 0 > Correction Span: 41 > Head Offset Count: 0 > Data Strobe Offset Count: 0 > Recovery Time Limit: 0 > The values for AWRE and ARRE should both be 1. If they aren't, as in > this case, where AWRE is 0, change the data with the editor, save it, and > exit. The camcontrol program will write the data back to the disk and > enable the option. Given that both AWRE and ARRE are 1, what action should I take now? As a side note, both vinum drives (da1 and da2) had AWRE and ARRE set. da0 didn't but now has these values set. thanks greg. -- Dan Langille - DVL Software Limited [I'm looking for more work] http://www.dvl-software.com/ | http://www.unixathome.org/ http://www.racingsystem.com/ | http://www.freebsddiary.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message