Date: Sun, 23 Jun 2002 12:55:54 -0400 (EDT) From: Chad Ziccardi <ziccardi@digitalfreaks.org> To: Hans Lambermont <hans@lambermont.dyndns.org> Cc: vadim@e-complex.ru, <freebsd-stable@freebsd.org>, <freebsd-fs@freebsd.org> Subject: Re: File system failure! URGENT Help needed! Message-ID: <20020623125321.A90926-100000@digitalfreaks.org> In-Reply-To: <20020623114405.A42706@moya.lambermont.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
begin quote from Hans Lambermont <hans@lambermont.dyndns.org> written...: > vadim@e-complex.ru wrote: > > ... > > booted it writed identical information onto both of that drivers > ... > > It is obvious, that the part of inodes was lost. How can we restore > > it? May be, it is possible to recover that by info what is in the > > files? > > I leave the inode magic to someone else, but for your filedata; I'd > start with making a binary file copy of the whole drive (dd using raw > device) so that you can dig trough it, maybe even copy the data parts > that you need from it. > > If you have a spare drive that is exactly the same type you could make a > binary copy of the disk to it, and don't need to worry about making the > prolem worse while recovering the data with inode magic. > > Hope this helps you a bit. > > Hans Lambermont > On one of the spare disks put the data on with dd, here's two utils that will help: /usr/ports/sysutils/ffsrecov /usr/ports/sysutils/gpart As well as TCT. -- Chad Ziccardi, Professional Slacker cz@digitalfreaks.org "Some cause happiness wherever they go; others whenever they go." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020623125321.A90926-100000>