Date: Sun, 30 Oct 2005 08:53:46 -0500 From: Bill Vermillion <bv@wjv.com> To: Arne =?unknown-8bit?Q?W=F6rner?= <arne_woerner@yahoo.com> Cc: freebsd-fs@freebsd.org Subject: Re: disklabel recovery Message-ID: <20051030135346.GA78577@wjv.com> In-Reply-To: <20051030130605.35720.qmail@web30302.mail.mud.yahoo.com> References: <fac025520510300455n4a670825g9bdbafb19c17cc93@mail.gmail.com> <20051030130605.35720.qmail@web30302.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Arne Wörner, the prominent pundit, on Sun, Oct 30, 2005 at 05:06 while half mumbling, half-witicized: > --- Gal Ben-Haim <gbenhaim@gmail.com> wrote: > > meanwhile I did a 'dd' image of the drive to a network drive and > > formatted the hd, I needed the system up again. > > > > what can I do with that 'dd' image in order to restore atleast > > some of the data on that drive ? > > > 1. You could just dd the image back to the freshly sliced disc and > then do a "fsck -f" (forced check even if it is marked clean). > 2. You could try to fsck the image via > # mdconfig -a -t vnode -f <network image> > # fsck -f /dev/md<unit number> > # mount /dev/md<unit number> /mnt > # ls /mnt/. If the data is important he might try 'lazarus' from TCT - The Coroners Toolkit. But it can be tedious. It examines the drive and tried to determine what is data, and then puts it in small files. 'TCT' also comes with a program called 'unrm' but that works on a drive that has a FS intact, as 'unrm' is similar to 'dd' but only copies block that aren't allocated. You wind up with thousands of files. It has an HTML mode so that you can examine the found data with a brower. I'd try this only as last resort and only if the files are that important, becaus as I said above, it is tedious. Bill -- Bill Vermillion - bv @ wjv . com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051030135346.GA78577>