From owner-freebsd-fs@FreeBSD.ORG Mon Nov 27 20:38:45 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B938116A4FB for ; Mon, 27 Nov 2006 20:38:45 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CFEF451D9 for ; Mon, 27 Nov 2006 20:21:23 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kARKMNCe074664; Mon, 27 Nov 2006 14:22:23 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <456B4901.5000500@centtech.com> Date: Mon, 27 Nov 2006 14:22:25 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Greg Eden References: <69404A94-8EBC-4978-8EA6-32E3DB1FA6A6@wholemeal.net> In-Reply-To: <69404A94-8EBC-4978-8EA6-32E3DB1FA6A6@wholemeal.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2252/Mon Nov 27 12:47:11 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: fsck crash: bad inode number to nextinode X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2006 20:38:45 -0000 On 11/24/06 03:31, Greg Eden wrote: > Hello, > > I'm try to recover a RAID5 volume which was badly corrupted when a > drive was removed during a rebuild. It contained about 1 TB of data > and was formatted with default values under FreeBSD 6.0-R. > > I have used dd to image the drive onto another volume and am mounting > it with mdconfig so I can work on that an not cause futher damage. > However when I run fsck_ufs on the /dev/md0 partition it eventually > crashes out during Phase 1 with > > UNKNOWN FILE TYPE I=42151497 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? yes > > fsck_ufs: bad inode number 42158080 to nextinode > > Is it possible to work around this to get fsck to complete? > > It is possible to mount the partition and some of the data is there, > however most of it is not. > > Thanks in advance for any help. I have previously posted to freebsd- > questions without a response. I've seen this before with really badly UFS filesystems, where the cylinder groups were mangled. I couldn't think of a good way to have fsck fix this, since you can't really guess at the inode information, and so the only option is really to just 'delete' the inode information, but that wasn't clear to me how to do that safely. You would probably be best served by running one of the various tools (in source and also in ports) that try to recover files themselves from a dd'ed image. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology An undefined problem has an infinite number of solutions. ------------------------------------------------------------------------