Date: Wed, 16 Jan 2013 10:42:34 -0800 From: Waitman Gobble <gobble.wa@gmail.com> To: Robert Huff <roberthuff@rcn.com> Cc: questions@freebsd.org Subject: Re: fsck can't determine fstype Message-ID: <CAFuo_fx3D3Q1JChrh3tK0V2_6U4NN46Rm1jrRkAH4OKfNp_xgw@mail.gmail.com> In-Reply-To: <20726.61534.560876.700561@jerusalem.litteratus.org> References: <20726.61534.560876.700561@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFuo_fx3D3Q1JChrh3tK0V2_6U4NN46Rm1jrRkAH4OKfNp_xgw>