Free recover data software for linux

Recover is a utility which automates some steps as described in the Ext2fs-Undeletion howto in order to recover a lost file.
Recover (ie. console version) is no longer under active development since bug reports have become rare (thus stable), newer and better FSs are coming up and I dont really know how recover could be improved. (suggestions are still welcome!)
If you want to undelete files on a non-ext2 linux partition, you should try it the UNIX-way!
Recover automates some steps as described in the ext2-undeletion howto. This means it seeks all the deleted inodes on your hard drive with debugfs. When all the inodes are indexed, recover asks you some questions about the deleted file. These questions are:
- Hard disk device name
- Year of deletion
- Month of deletion
- Weekday of deletion
- First/Last possible day of month
- Min/Max possible file size
- Min/Max possible deletion hour
- Min/Max possible deletion minute
- User ID of the deleted file
- A text string the file included (can be ignored)
If recover found any fitting inodes, he asks to give a directory name and dumps the inodes into the directory. Finally he asks you if you want to filter the inodes again (in case you typed some wrong answers).
We hope you will never need recover, but in case, its better to install this program anyway. Once a file is deleted, everytime something is written to disk, theres a change it will overwrite the old deleted file. You will never be able to restore it.

The gzip Recovery Toolkit attempts to automate the recovery of data from corrupted gzip files (including tarballs) through a program called gzrecover. gzip Recovery Toolkit package is still very experimental at this point.
99% of "corrupted" gzip archives are caused by transferring the file via FTP in ASCII mode instead of binary mode. Please re-transfer the file in the correct mode first before attempting to recover from a file you believe is corrupted.
This program is provided AS IS with absolutely NO WARRANTY. It is not guaranteed to recover anything from your file, nor is what it does recover guaranteed to be good data. The bigger your file, the more likely that something will be extracted from it. Also keep in mind that this program gets faked out and is likely to "recover" some bad data. Everything should be manually verified.
Usage:
Run gzrecover on a corrupted .gz file. Anything that can be read from the file will be written to a file with the same name, but with a .recovered appended (any .gz is stripped). You can override this with the -o option.
To get a verbose readout of exactly where gzrecover is finding bad bytes, use the -v option to enable verbose mode. This will probably overflow your screen with text so best to redirect output to a file.
Once gzrecover has finished, you will need to manually verify any data recovered as it is quite likely that our output file is corrupt and has some garbage data in it. If your archive is a tarball, read on.
For tarballs, the tar program will choke because GNU tar cannot handle errors in the file format. Fortunately, GNU cpio (tested at version 2.5 or higher) handles corrupted files out of the box.
Heres an example:
$ ls *.gz
my-corrupted-backup.tar.gz
$ gzrecover my-corrupted-backup.tar.gz
$ ls *.recovered
my-corrupted-backup.tar.recovered
$ cpio -F my-corrupted-backup.tar.recovered -i -v
If you have a previous release, please note that the patches to GNU tar have been discontinued. They were only marginally successful at best and GNU cpio does what is needed out of the box and does it far better.
Enhancements:
- Documentation updates, including a man page, plus code cleanup to better enable inclusion in GNU/Linux packages and eliminate compilation warnings.

Secure Data Manager project is a manager for passwords and other private data.
Secure Data Manager (SDM) is a full-featured password manager application written entirely in Java (so it can run on Unix or Windows). It encrypts logins and other private information for Web sites, computers, credit cards, etc.
Main features:
- Many great features and more coming each month based on user feedback!
- No limit to how you use the product or how often!
- Trusted since you and everyone else can see the code that protects your passwords -- keeping the application clear of any trojans or bad business practices.
- Open source -- so if you know how to write code, you can add any feature you want!
- Free.

myrescue is a program to rescue the still-readable data from a damaged harddisk. The project is similiar in purpose to dd_rescue, but it tries to quickly get out of damaged areas to first handle the not yet damaged part of the disk and return later.

Note:

This tools is no replacement for a professional data recovery service! If you do have the latter option, dont even think of using myrescue, as it may further damage your disk. This tool is provided only for the case that you are absolutely desperate and definitely cannot afford a professional data recovery. Or in case you know what you are doing, e.g. if you know that it is the aging of the magnetisation layer that is causing your problem.

The usual GPL disclaimer applies. Especially the NON-WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE. Dont blame (or sue) me if it fails to recover or further damages your data.

How it works

The program tries to copy the device blockwise to a file and keeps a table ("block bitmap") noting whether a block has been successfully copied, not yet handled or has had errors. This block bitmap can be used in successive runs to concentrate on the not yet rescued blocks.

The program has a special skip mode to handle read errors. Usually harddisk surface defects cover more than just one block and continuous reading in defect areas can damage the surface, the heads and (by permanent recalibration) the drive mechanics. If this happens, the chances of rescuing the remaining undamaged data drop dramatically. So in skip mode, myrescue tries to get out of damaged areas quickly by exponentially increasing the stepsize. The skipped blocks are marked as unhandled in the block bitmap and can be retried later.

Finally, the program has an option to multiply try to read a block before considering it damaged.

File::Data is a Perl module as a interface to file data.

Wraps all the accessing of a file into a convenient set of calls for reading and writing data, including a simple regex interface.

Note that the file needs to exist prior to using this module!

See new()

SYNOPSIS

use strict;

use File::Data;

my $o_dat = File::Data->new(./t/example);

$o_dat->write("complete file contentsn");

$o_dat->prepend("first linen"); # line 0

$o_dat->append("original second (last) linen");

$o_dat->insert(2, "new second linen"); # inc. zero!

$o_dat->replace(line, LINE);

print $o_dat->READ;

Or, perhaps more seriously :-}

my $o_sgm = File::Data->new(./sgmlfile);

print "new SGML data: ".$o_sgm->REPLACE(
s*((?s).*)s* ,
qq| key="val" |,
) if $o_sgm;

See METHODS and EXAMPLES.

IMPORTANT

lowercase method calls return the object itself, so you can chain calls.

my $o_obj = $o_dat->read; # ! READ; # !<<less