From owner-freebsd-questions@FreeBSD.ORG Tue Jan 20 19:11:12 2009 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 615DC106566C for ; Tue, 20 Jan 2009 19:11:12 +0000 (UTC) (envelope-from chris@cjones.org) Received: from gamera.mt.sri.com (gamera.mt.sri.com [206.127.76.125]) by mx1.freebsd.org (Postfix) with ESMTP id 8D5878FC1B for ; Tue, 20 Jan 2009 19:11:10 +0000 (UTC) (envelope-from chris@cjones.org) Received: from [206.127.76.114] (myosin.mt.sri.com [206.127.76.114]) (authenticated bits=0) by gamera.mt.sri.com (8.13.8/8.13.8) with ESMTP id n0KJB7D4025467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 20 Jan 2009 12:11:07 -0700 (MST) Message-ID: <497621C4.6070203@cjones.org> Date: Tue, 20 Jan 2009 12:11:00 -0700 From: Chris Jones User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4974BE49.2080508@cjones.org> <44ljt5olwm.fsf@be-well.ilk.org> In-Reply-To: <44ljt5olwm.fsf@be-well.ilk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: DUMP: read error: Bad address 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: Tue, 20 Jan 2009 19:11:12 -0000 Lowell Gilbert wrote: > Chris Jones writes: > >> # dump -0aL -f - /var | ( cd /mnt/var && restore -rf - ) >> >> I got about a dozen messages like this: >> >> DUMP: read error from /dev/ad8s1d: Bad address: [block 10992192]: >> count=5120 >> > It could be a serious problem, but is not necessarily such. > Can you use smarttools to query the disk firmware for *its* > opinion? > SMART Error Log Version: 1 No Errors Logged ...so I assume the drive thinks it's doing just fine. Is this likely coming from a signal error, like a bad cable? Is it random driver lossage? Most importantly, is the ATA driver going to retry and correct this error, or does it mean I'm getting corrupted data on my disks? Chris