On Sun, 2013-06-16 at 22:34 +1200, Chris Bannister wrote: > On Sat, Jun 15, 2013 at 01:14:47PM -0400, To Ro wrote: > > I started testing one of the recovered files, with a binary file editor can > > se a long sequence of zeros at the very beginning of it, took some > > precautions, and here is what I see > > > > ls -lh > > total 5.8G > > -r-------- 1 xyz xyz 5.8G Jun 14 17:52 inode_17000 > > > > tried gunzip, djview, tar -x, mplayer, etc, thinking of the possible files > > that I had of that size. Nothing comes up. By the way, did bcrypt disappear > > from wheezy? > > > > Any ideas what else could be done? > > Just an idea, but what does > "file inode_17000" say?
I experienced recovering ext4 files as nearly impossible, some can be recovered, but most is lost when trying to recover it with tools doing it automatically, however, IIRC _all_ (at least most) tools provide an option to recover lost directories and files as directories and files in a human readable way. Take a look at THE_COMMAND_YOU_USE --help or man THE_COMMAND_YOU_USE ;). Hth, Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1371380058.886.4.camel@archlinux
