From owner-freebsd-fs@FreeBSD.ORG Sun Nov 2 07:20:21 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 093E9106568A for ; Sun, 2 Nov 2008 07:20:21 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id BF8A08FC19 for ; Sun, 2 Nov 2008 07:20:20 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r55.edvax.de (port-92-196-106-204.dynamic.qsc.de [92.196.106.204]) by mx01.qsc.de (Postfix) with ESMTP id 1D1E050927; Sun, 2 Nov 2008 08:20:17 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id mA27KH50001844; Sun, 2 Nov 2008 08:20:17 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sun, 2 Nov 2008 08:20:15 +0100 From: Polytropon To: frank@exit.com Message-Id: <20081102082015.b8d40d77.freebsd@edvax.de> In-Reply-To: <1225600923.97152.3.camel@jill.exit.com> References: <20081102050601.9fccb80f.freebsd@edvax.de> <1225600923.97152.3.camel@jill.exit.com> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD FS Subject: Re: Repairing a defective UFS 2 partition with fsck_ffs (or other means) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 07:20:21 -0000 Hi, many thanks for your quick reply. On Sat, 01 Nov 2008 21:42:03 -0700, Frank Mayhar wrote: > Check out /usr/ports/sysutils/ffs2recov. It won't repair the filesystem > but it may be able to recover some or all of your data. I've already tried this program: % mdconfig -a -t vnode -f ad1s1f.dd md0 % ffs2recov -dav /dev/md0 will create many files according to inode numbers. The file command will identify them as "data", and they are all of the same size, group-wise. I don't know what I could do with these files. Furthermore, these errors are repeatedly displayed: getinode: inode size (14199049117881519608 > 175821242368) too big, skipping. and main.c:529 memory allocation failed for inode 294970, -1693177856 with different values. I'm not sure if ffs2recov is the right tool here, or am I using it the wrong way? I've read /usr/local/share/doc/sleuthkit/ref_fs.txt carefully, but it doesn't seem to help me either. I don't want to buy expensive "Windows" software that I have to run in wine (along with the usual problems upcoming) for something that I think could be solved using FreeBSD's on-board means, or even send the disk to a recovery company for much money. I simply can't afford this. If you have any experiences regarding this special case of data recovery, please give me an advice where I should play attention. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...