From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 18 22:27:46 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 B012116A4CE for ; Sat, 18 Dec 2004 22:27:46 +0000 (GMT) Received: from mail.nativenerds.com (host-70-0-111-24.midco.net [24.111.0.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C5D343D2D for ; Sat, 18 Dec 2004 22:27:46 +0000 (GMT) (envelope-from estover@nativenerds.com) Received: from red (host-14-37-230-24.midco.net [24.230.37.14]) iBIMW6Os002293 for ; Sat, 18 Dec 2004 15:32:06 -0700 (MST) (envelope-from estover@nativenerds.com) From: Ed Stover To: freebsd-hackers@freebsd.org In-Reply-To: <20041218211747.GE1068@cicely12.cicely.de> References: <41C3D62D.7000808@comcast.net> <20041218091739.GC97121@cirb503493.alcatel.com.au> <20041218195910.GD1068@cicely12.cicely.de> <20041218210720.GE97121@cirb503493.alcatel.com.au> <20041218211747.GE1068@cicely12.cicely.de> Content-Type: text/plain Organization: Native Nerds Date: Sat, 18 Dec 2004 15:27:45 -0700 Message-Id: <1103408865.90538.29.camel@red.nativenerds.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.nativenerds.com Subject: Re: Multiple hard disk failures - coincidence ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: estover@nativenerds.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Dec 2004 22:27:46 -0000 Have you run the low level disk tools from Maxtor on your failed drives? One day out of the blue my 80Gig maxtors started giving out hard error failures, so I downloaded a floppy image from maxtor and used it to scan and repair my drives. I rebooted in single user mode and fscked my drives and rescued the data from lostnfound. and everything has been Aok ever since. On Sat, 2004-12-18 at 22:17 +0100, Bernd Walter wrote: > On Sun, Dec 19, 2004 at 08:07:20AM +1100, Peter Jeremy wrote: > > On Sat, 2004-Dec-18 20:59:11 +0100, Bernd Walter wrote: > > >On Sat, Dec 18, 2004 at 08:17:39PM +1100, Peter Jeremy wrote: > > >> My approach to this is to add a line similar to > > >> dd if=/dev/ad0 of=/dev/null bs=32k > > >> for each disk into /etc/daily.local (or /etc/weekly.local or whatever). > > >> This ensures that the disks are readable on a regular basis. > > > > > >Regular reading of every file is part of what I call backup. > > > > That only verifies the used part of the disk. Reading the unused parts > > That's true - used parts are the only I'm interested in reading. > If blocks fail that aren't used write reallocation has to do it's > job. > > > of the disk as well helps reduce surprises. Also, in a mirrored environment, > > the backup does not ensure that the data can be read off both disks. > > (Or the parity area for RAID-5). > > Raid is another story. > Just dd'ing the disks wouldn't check redundance integrity, but if you > check the integrity why would you still want to check via dd too? >