Free hard disk data recovery software for linux

Hard Disk Temperature Monitor is my first superkaramba theme, it uses the package hddtemp, please verify if your system has it installed.

I modify this image(http://www.kde-look.org/content/show.php?content=28748)

And made the Icon, from 2 images from the web.

The entire theme is in spanish, but you can translate to any language.

I really apreciate your comments!

Thank you so much, and greetings from Medellin-Colombia!

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.

Cascade Historian software is an event driven data storage program used to maintain persistent time-sequence data sets derived from process data.

Features and Benefits

In addition to providing storage the Historian also offers a historical query facility suitable for generating graphs and tabular output for export to other analysis programs. Other programs can also send data to the Cascade Historian by linking the API library and making the appropriate function calls.

The data storage mechanism within the Cascade Historian will maintain any number of simultaneous time histories, one for each configured process point.

The data for each point is maintained in one or more files, allowing for removal of stale data or offline archival of old data. These files are either numbered in increasing numerical order, or dated. When using dated files, the Cascade Historian automatically begins logging to a new file at midnight.

Data logging by event

The Cascade Historian records data by event. If no data change event occurs for a point, no data is written to disk. This saves disk space when the process point is idle, and captures even very short duration events when the point is changing. This is both more efficient and more accurate than a sampling historian. It is possible to place both a time and value deadband on each point to reduce storage for points whose values are constantly changing by insignificant amounts. The Cascade Historian will not reorder out of sequence data.

Data is stored on disk in fixed length binary records to minimize disk space, with a time resolution of nanoseconds. These files can be easily read by any custom program as well as by the Cascade Historian.

Any process may request data from the Cascade Historian. The Cascade Historian maintains a configurable in-memory cache for each point being recorded so that queries of recent data will not require disk access. If the request cannot be satisfied from the in-memory cache, then the disk files related to the point will be consulted for the data to satisfy the request. The requests can take one of the following forms:

Raw Data - Simply returns all recorded events for the data point, reported vs. time.
Periodic Data - Performs linear interpolation on the data to produce a data set at an even time interval. This produces the same result that a sampling historian would produce.
Relative Interpolation - Performs interpolation of one data point against another to produce a Y vs. X data set. Interpolation is performed on Y to produce (X,Y) pairs at the times of known values of X.
Periodic Relative Interpolation - Performs interpolation of one data point against another to produce a Y vs. X data set. Interpolation is performed on both X and Y to produce (X,Y) pairs at an even time interval.

The Cascade Historian has been built to allow quick addition of other forms of historical query.

FDMS-3 Ripper is a Perl program for extracting the tracks from the FDMS-3 filesystem. I recently bought a Fostex FD-8 multitrack hard disk recorder for recording music. It works great, but I was disappointed to discover that, although it uses a standard external SCSI hard disk, there was no way to "rip" the recorded tracks from the hard drive to my PC over the SCSI port. The alternatives were to use the analog-out to re-record each track using my soundcard (resulting in loss of quality and loss of synch between tracks), or buying a $500 ADAT card for my PC.

I decided that I would try to figure out a way to rip the music directly over the SCSI port. The FD-8 uses a proprietary Fostex filesystem, FDMS-3. I decided to hook it up to my PC and probed the drive. I was able to figure out the basic layout of the filesystem pretty quickly. Note: this is designed to hard disks formatted in the FDMS-3 "Mastering" mode, which stores the audio data in uncompressed format.

In order to use the program, you will need to take the hard disk that has the FDMS-3 filesystem on it and hook it up to your PC (mine is a SCSI drive -- dont know if this will work with one of the internal IDE drives you can hook up to the FD-8). Make sure that Linux can see the drive (dont try to mount it, though!). You might want to have a look at SCSI-2.4-HOWTO to get the drive recognized. My external hard disk is located at "/dev/sda", but yours could end up elsewhere.

Next, you need to make sure you have the following on your system: perl, sox and fileutils (for the "dd" utility). Security Warning Unfortunately, this program presents significant security issues, so be careful with it. The script needs to be able to access the hard disk directly, so you can either run it as root (not safe), or change the permissons for the hard disk device (in my case, "/dev/sda"). Run the program with "./fdms3rip /dev/sda" (substituting the actual location of your hard disk).

This will list all of the programs present on the hard disk. Then, run it again with the number of the program you want to fetch off the hard disk: "./fdms3rip /dev/sda 5" to get all of the recorded tracks for program number 5. After waiting a bit, you should now have a bunch of WAV files on your Linux machine. Warning This program will create and erase files with the names "dir" and "header" in the directory it is run from. It would be best to run this program from a clean directory, just to make sure there are no problems.

GNU ddrescue is a data recovery tool. GNU ddrescue copies data from one file or block device (cdrom, hard disc, etc) to another, trying hard to rescue data in case of read errors.
Ddrescue does not truncate the output file if not asked to. So, every time you run it on the same output file, it tries to fill in the gaps.
The basic operation of ddrescue is fully automatic. That is, you dont have to wait for an error, stop the program, read the log, run it in reverse mode, etc.
If you use the logfile feature of ddrescue, the data is rescued very efficiently (only the needed blocks are read). Also you can interrupt the rescue at any time and resume it later at the same point.
Automatic merging of backups: If you have two or more damaged copies of a file, cdrom, etc, and run ddrescue on all of them, one at a time, with the same output file, you will probably obtain a complete and error-free file.
This is so because the probability of having damaged areas at the same places on different input files is very low. Using the logfile, only the needed blocks are read from the second and successive copies.
The logfile is periodically saved to disc. So in case of a crash you can resume the rescue with little recopying.
Also, the same logfile can be used for multiple commands that copy different areas of the file, and for multiple recovery attempts over different subsets.
Ddrescue aligns its I/O buffer to the sector size so that it can be used to read from raw devices. For efficiency reasons, also aligns it to the memory page size if page size is a multiple of sector size.
Whats New in 1.5 Stable Release:
- The license has been updated to GPL version 3 or later.
Whats New in 1.6-pre2 Development Release:
- Support for sparse writes to the output file has been added.

SystemRescueCd is a Linux system available from a bootable CDROM that provides an easy way to perform administrative tasks on your computer, such as creating and editing the partitions of the hard disk or backing up data.
System Rescue CD contains a lot of system utilities (such as parted, partimage, and fstools), and basic programs (such as editors, midnight commander, and network tools).
It also includes QtParted, a Partition Magic clone that makes editing partitons easy with its Qt graphical user interface. This CDROM aims to be very easy to use and accessible to everybody.
Main features:
- GNU Parted is the best tool for editing your disk partitions under linux
- QtParted is a Partition Magic clone for Linux.
- Partimage is a Ghost/Drive-image clone for Linux
- File systems tools (e2fsprogs, reiserfsprogs, xfsprogs, jfsutils, ntfsprogs, dosfstools): they allow you to format, resize, debug an existing partition of your hard disk
- Sfdisk allows you to backup and restore your partition table

AppleII::Disk is a Perl module for block-level access to Apple II disk image files.

SYNOPSIS

use AppleII::Disk;
my $disk = AppleII::Disk->new(image.dsk);
my $data = $disk->read_block(1); # Read block 1
$disk->write_block(1, $data); # And write it back :-)

AppleII::Disk provides block-level access to the Apple II disk image files used by most Apple II emulators. (For information about Apple II emulators, try the Apple II Emulator Page at http://www.ecnet.net/users/mumbv/pages/apple2.shtml.) For a higher-level interface, use the AppleII::ProDOS module.
AppleII::Disk provides the following methods:

$disk = AppleII::Disk->new($filename, [$mode])

Constructs a new AppleII::Disk object. $filename is the name of the image file. The optional $mode is a string specifying how to open the image. It can consist of the following characters (case sensitive):

r Allow reads (this is actually ignored; you can always read)
w Allow writes
d Disk image is in DOS 3.3 order
p Disk image is in ProDOS order

If you dont specify d or p, then the format is guessed from the filename. .PO and .HDV files are ProDOS order, and anything else is assumed to be DOS 3.3 order.

If you specify w to allow writes, then the image file is created if it doesnt already exist.

$size = $disk->blocks([$newsize])

Gets or sets the size of the disk in blocks. $newsize is the new size of the disk in blocks. If $newsize is omitted, then the size is not changed. Returns the size of the disk image in blocks.

This refers to the logical size of the disk image. Blocks outside the physical size of the disk image read as all zeros. Writing to such a block will expand the image file.

When you create a new image file, you must use blocks to set its size before writing to it.

$contents = $disk->read_block($block)

Reads one block from the disk image. $block is the block number to read.
$contents = $disk->read_blocks(@blocks)

Reads a sequence of blocks from the disk image. @blocks is a reference to an array of block numbers. As a special case, block 0 cannot be read by this method. Instead, it returns a block full of 0 bytes. This is how sparse files are implemented. If you want to read the actual contents of block 0, you must call $disk->read_block(0) directly.

$contents = $disk->read_sector($track, $sector)

Reads one sector from the disk image. $track is the track number, and $sector is the DOS 3.3 logical sector number. This is currently implemented only for DOS 3.3 order images.

$disk->fully_allocate()

Expands the the physical size of the disk image file to match the logical size of the disk image. It will be expanded as a sparse file if the filesystem containing the image file supports sparse files.

$disk->write_block($block, $contents, [$pad])

Writes one block to the disk image. $block is the block number to write. $contents is the data to write. The optional $pad is a character to pad the block with (out to 512 bytes). If $pad is omitted or null, then $contents must be exactly 512 bytes.

$disk->write_blocks(@blocks, $contents, [$pad])

Writes a sequence of blocks to the disk image. @blocks is a reference to an array of block numbers to write. $contents is the data to write. It is broken up into 512 byte chunks and written to the blocks. The optional $pad is a character to pad the data with (out to a multiple of 512 bytes). If $pad is omitted or null, then $contents must be exactly 512 bytes times the number of blocks.

As a special case, block 0 cannot be written by this method. Instead, that block of $contents is just skipped. This is how sparse files are implemented. If you want to write the contents of block 0, you must call $disk->write_block directly.

$disk->write_sector($track, $sector, $contents, [$pad])

Writes one sector to the disk image. $track is the track number, and $sector is the DOS 3.3 logical sector number. $contents is the data to write. The optional $pad is a character to pad the sector with (out to 256 bytes). If $pad is omitted or null, then $contents must be exactly 256 bytes. This is currently implemented only for DOS 3.3 order images.

$padded = AppleII::Disk::pad_block($data, [$pad, [$length]])

Pads $data out to $length bytes with $pad. Returns the padded string; the original is not altered. Dies if $data is longer than $length. The default $pad is " ", and the default $length is 512 bytes.

If $pad is the null string (not undef), just checks to make sure that $data is exactly $length bytes and returns the original string. Dies if $data is not exactly $length bytes.

pad_block is a subroutine, not a method, and is not exported. You probably dont need to call it directly anyway, because the write_XXX methods will call it for you.

bak2disc is a disc-based backup script aimed at being easy to use and powerful. bak2discs most notable feature is the way it groups common files and directories together to preserve structure when data is divided into disc volumes.

This functionality is a tunable threshold that lets you control the balance between data contiguity and effective disc usage.

In addition, bak2disc also features multi-session support that lets you stop the writing cycle between volumes and resume it later. Burning is done on-the-fly, with growisofs for DVDs and cdrecord for CDs.