From owner-freebsd-questions@FreeBSD.ORG  Wed Jan 16 18:42:42 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: questions@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 0D55184F
 for <questions@freebsd.org>; Wed, 16 Jan 2013 18:42:42 +0000 (UTC)
 (envelope-from gobble.wa@gmail.com)
Received: from mail-bk0-f41.google.com (mail-bk0-f41.google.com
 [209.85.214.41]) by mx1.freebsd.org (Postfix) with ESMTP id 9CD831FF
 for <questions@freebsd.org>; Wed, 16 Jan 2013 18:42:41 +0000 (UTC)
Received: by mail-bk0-f41.google.com with SMTP id jg9so892860bkc.14
 for <questions@freebsd.org>; Wed, 16 Jan 2013 10:42:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:cc:content-type;
 bh=82j61QLF6IZFAgAYHhnOILjYgV/Lsi0fMIOwiGyfPRE=;
 b=EDLoN7TmM0SKnrUhxAqBgW3hmUj3pOxrOwEiF1fP4Qby93TgYF37htbY38Yr45K4jj
 a5Hpm9TcvOm6D5mIVLgy5M08tmBsnCeDGwigOWG3jpgq5xsezRmBbgpwfPuvfUyat9xF
 2TWnDv962N+uKNl2E+VNvi54fq7p+s56ardtuPkGR8FJ0HywGzoQ/NQBOXTQLvXOx3Nc
 6W75ALxWyJpY4M3bz3Oddi96GmK2tK9y+1UK9Z2BIAiniDAuRfabpaoNiNtMObAEtviz
 nI8rbUb2KeNiVwpKccOhZ9lYlNv6yRDm0KfyvtZRbo91bPfjQfnk3jB5Hijv6iDukZYl
 3zvg==
MIME-Version: 1.0
X-Received: by 10.204.12.220 with SMTP id y28mr786735bky.112.1358361754741;
 Wed, 16 Jan 2013 10:42:34 -0800 (PST)
Received: by 10.204.75.211 with HTTP; Wed, 16 Jan 2013 10:42:34 -0800 (PST)
Received: by 10.204.75.211 with HTTP; Wed, 16 Jan 2013 10:42:34 -0800 (PST)
In-Reply-To: <20726.61534.560876.700561@jerusalem.litteratus.org>
References: <20726.61534.560876.700561@jerusalem.litteratus.org>
Date: Wed, 16 Jan 2013 10:42:34 -0800
Message-ID: <CAFuo_fx3D3Q1JChrh3tK0V2_6U4NN46Rm1jrRkAH4OKfNp_xgw@mail.gmail.com>
Subject: Re: fsck can't determine fstype
From: Waitman Gobble <gobble.wa@gmail.com>
To: Robert Huff <roberthuff@rcn.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 18:42:42 -0000

On Jan 16, 2013 10:24 AM, "Robert Huff" <roberthuff@rcn.com> wrote:
>
>
>        Situation:
>        I have a hard drive which may or may not have died already,
> from which I would _very_ much like to recover maybe 1 gbyte of data.
>        After extracting it from the old machine, it's now hooked up to
> a system running:
>
> FreeBSD 10.0-CURRENT #0: Sun Dec 30 12:52:09 EST 2012 amd64
>
>       "gpart show" identifies it as "ad1" with partition 2 as type
> "freebsd-ufs" and label "g_user".
>           However:
>
> >> fsck /dev/ad1p2
> fsck: could not determine filesystem type
>
>       Adding " -t ufs " produces:
>
> huff@>> fsck -t ufs /ad1p2
> ** /dev/ad1p2
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> -2103374334359810 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103382924294404 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103391514228998 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103400104163592 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103408694098186 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103417284032780 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103425873967374 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103434463901968 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103443053836562 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103451643771156 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> -2103460233705750 BAD I=342
> UNEXPECTED SOFT UPDATE INCONSISTENCY
>
> EXCESSIVE BAD BLKS I=342
> CONTINUE? [yn] ^C
> ***** FILE SYSTEM STILL DIRTY *****
>
>
>       While I'm not an fs expert, this feels wrong.
>       Is there some clue I'm missing?
>
>       Respectfully,
>
>
>                         Robert Huff
>
> ________________________________________

hi,

you might try to force a read only mount, if the drive is clicking its
probably losing "tracking", I have had luck in the past putting it in a
ziplock and in the freezer for a good while. hope that helps.

Waitman Gobble
San Jose California


_______
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
freebsd-questions-unsubscribe@freebsd.org"