From owner-freebsd-questions@FreeBSD.ORG Fri Nov 19 08:20:47 2010 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 D73781065674 for ; Fri, 19 Nov 2010 08:20:47 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id B85D78FC1C for ; Fri, 19 Nov 2010 08:20:47 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id oAJ8Kjv1042278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Nov 2010 00:20:46 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id oAJ8Kjmc042277; Fri, 19 Nov 2010 00:20:45 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA00751; Fri, 19 Nov 10 00:16:13 PST Date: Fri, 19 Nov 2010 00:16:14 -0800 From: perryh@pluto.rain.com To: thomas.exner@uni-konstanz.de Message-Id: <4ce6324e.0YK3+tFLmwsWGUh9%perryh@pluto.rain.com> References: <4CE4F4E4.10606@uni-konstanz.de> In-Reply-To: <4CE4F4E4.10606@uni-konstanz.de> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: disk recovery problem(s) 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: Fri, 19 Nov 2010 08:20:47 -0000 Thomas Exner wrote: > when running fsck the first error message is "ROOT INODE UNALLOCATED" > ... > Is there a chance to get the data back? Dunno about current versions, but IIRC some earlier versions of dump(8) could handle even a badly-corrupted FS. No harm in trying, since it will not try to write anything to the FS being dumped. Of course, you need to find a place to dump it to (and I would _not_ advise piping the output into restore(8) in this kind of situation -- save the dumpfile itself somewhere in case you find yourself needing to hack on restore(8) to extract files from it).