From owner-freebsd-questions@FreeBSD.ORG Mon Aug 24 19:32:44 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 CA3891065698 for ; Mon, 24 Aug 2009 19:32:44 +0000 (UTC) (envelope-from kellymartin@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mx1.freebsd.org (Postfix) with ESMTP id 87DC98FC18 for ; Mon, 24 Aug 2009 19:32:44 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 3so1405238qwe.7 for ; Mon, 24 Aug 2009 12:32:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=+O5VRLMonaxNtrtFagzF14X/H1lx/d/b7fqBa2Zk7p8=; b=h2s6tO5EpualSu+x0z/a/8jYW5KU5LaV3owRALLg65XnIO51wAZXSZNHUXn3m0NPVv ngfMKG5uoe7f02Y3qXwkQwK14uD56B0ZJ1FsdZOGgPxcQ4Nr0L2q6cJ+YdAq1BU44cYW KMDg0sdwWiPa8ZfD+3Q3fggqEpNNpEFWml/EY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=GFL3sORjslRjlPudoQtHiKcbIZl1doC36ATqzmCciYCL9jk2z5cybgOT1mHKia4nPI 3WWKFNfIt6S9b4I+AXtViEkCwI84MKv2dhv5e3COXh/sZ4BbqWdVtRE4k+L6uGKkhHQ3 tI/BbhAysYtX5cQSmTU+gMwTRGMd4y4hHotAk= MIME-Version: 1.0 Received: by 10.224.12.195 with SMTP id y3mr3117880qay.34.1251138561246; Mon, 24 Aug 2009 11:29:21 -0700 (PDT) Date: Mon, 24 Aug 2009 12:29:19 -0600 Message-ID: <1338880b0908241129p75b6845cg26d21804e118364@mail.gmail.com> From: Kelly Martin To: FreeBSD Questions Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: hard disk failure - now what? 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: Mon, 24 Aug 2009 19:32:44 -0000 I just experienced a hard drive failure on one of my FreeBSD 7.2 production servers with no backup! I am so mad at myself for not backing up!! Now it's a salvage operation. Here are the type of errors I was getting on the console, over-and-over: ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=441633503 ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly ad4: FAILURE - WRITE_DMA48 timed out LBA=441633375 g_vgs_done():ad4s1f[WRITE(offset=216338284544, length=16384)]error = 5 I could still login to the machine (after an eternity) but got lots of read/write errors along the way. The offset shown in the errors kept changing, so I thought it was a hardware eSATA controller issue instead of a bad sector on the drive - I replaced the motherboard, but the problem persisted. So I bought a new hard drive and have re-installed FreeBSD 7.2 on it. I'd like to plug in the old hard drive today, mount it and salvage as much as I can... especially the database files, config files, etc. My question: what kind of checks and/or repair tools should I run on the damaged drive after it's mounted? Or should I mount it as read-only and start backing it up? I am hoping most of my data is still there, but also don't want to damage it further. I desperately need to salvage the data, what do the kind people on this list recommend? thanks, kelly