From owner-freebsd-fs@FreeBSD.ORG Mon Nov 27 21:15:17 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 3D3D016A412 for ; Mon, 27 Nov 2006 21:15:17 +0000 (UTC) (envelope-from greg@wholemeal.net) Received: from mail9.messagelabs.com (mail9.messagelabs.com [194.205.110.133]) by mx1.FreeBSD.org (Postfix) with SMTP id 118EA43DD4 for ; Mon, 27 Nov 2006 20:54:48 +0000 (GMT) (envelope-from greg@wholemeal.net) X-VirusChecked: Checked X-Env-Sender: greg@wholemeal.net X-Msg-Ref: server-5.tower-9.messagelabs.com!1164660497!25246908!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [212.135.210.82] Received: (qmail 8639 invoked from network); 27 Nov 2006 20:48:17 -0000 Received: from dsl-212-135-210-82.dsl.easynet.co.uk (HELO warprecords.com) (212.135.210.82) by server-5.tower-9.messagelabs.com with SMTP; 27 Nov 2006 20:48:17 -0000 Received: from [192.168.100.40] (HELO [192.168.0.10]) by warprecords.com (CommuniGate Pro SMTP 5.0.10) with ESMTPS id 6994983; Mon, 27 Nov 2006 20:48:16 +0000 In-Reply-To: <456B4901.5000500@centtech.com> References: <69404A94-8EBC-4978-8EA6-32E3DB1FA6A6@wholemeal.net> <456B4901.5000500@centtech.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <614F741C-5AF0-4E72-B77E-FD85311FAD9A@wholemeal.net> Content-Transfer-Encoding: 7bit From: Greg Eden Date: Mon, 27 Nov 2006 20:48:14 +0000 To: Eric Anderson X-Mailer: Apple Mail (2.752.2) 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 21:15:17 -0000 On 27 Nov 2006, at 20:22, Eric Anderson wrote: > 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. OK. I had a feeling fsck wasn't going to save me this time :( > 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. Do you have any specific recommendations? a search of freshports.org revealed 'magicrescue' and 'foremost' as likely looking rescue utilities. Is there anything else? Thanks for the pointers! best. greg.