fmII
Tue, Nov 18th home | browse | articles | contact | chat | submit | faq | newsletter | about | stats | scoop 20:27 UTC
in
Section
login «
register «
recover password «
[Project] add release | add branch | add screenshot | broken links | change owner | email subscribers | update project | update branch (urls) [Project]

 GNU ddrescue 1.9-rc1 (Development)
Section: Unix

 

Added: Thu, Aug 12th 2004 11:22 UTC (4 years, 3 months ago) Updated: Tue, Nov 18th 2008 09:20 UTC (today)


Screenshot About:
GNU ddrescue is a data recovery tool. It copies data from one file or block device (hard disc, cdrom, etc) to another, trying hard to rescue data in case of read errors. GNU 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 GNU ddrescue is fully automatic. That is, you don't 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 GNU 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.

Release focus: Code cleanup

Changes:
Verbosity control of user messages has been simplified.

Author:
Antonio Diaz Diaz [contact developer]

Rating:
8.75/10.00 (7 votes)

Homepage:
http://www.gnu.org/software/ddrescue/ddrescue.html
Tar/GZ:
http://download.savannah.gnu.org/[..]eleases/ddrescue/ddrescue-1.9-rc2.tar.lz
Tar/BZ2:
http://download.savannah.gnu.org/[..]leases/ddrescue/ddrescue-1.9-rc2.tar.bz2
Mailing list archive:
http://lists.gnu.org/mailman/listinfo/bug-ddrescue

Trove categories: [change]
[Development Status]  5 - Production/Stable
[Environment]  Console (Text Based)
[Intended Audience]  Advanced End Users
[License]  OSI Approved :: GNU General Public License v3
[Operating System]  OS Independent
[Programming Language]  C++
[Topic]  System :: Recovery Tools

Dependencies: [change]
Lzip (optional)
[download links]

 
Project admins: [change]
» Antonio Diaz Diaz (Owner)

» Rating: 8.75/10.00 (Rank N/A)
» Vitality: 11.16% (Rank 32)
» Popularity: 5.83% (Rank 555)

project statsdownload stats
(click to enlarge graphs)
   Record hits: 60,606
   URL hits: 21,830
   Subscribers: 156

Other projects from the same categories:
SuperRescue CD
unrm
dd_rescue
dirsplit
samdump

Users who subscribed to this project also subscribed to:
Python
Jinzora
FlightGear
WebIssues
The Distribulator


Add comment · Rate this project · Subscribe to new releases · Ignore this project · Email this project to a friend · Project record in XML

 Branches

Branch Version Last release License URLs
Stable 1.9 18-Nov-2008 GNU General Public License v3 Homepage Tar/GZ
Development 1.9-rc2 12-Nov-2008 GNU General Public License v3 Homepage Tar/GZ

 Releases

Version Focus Date
1.9-rc2 Minor feature enhancements 12-Nov-2008 22:43
1.9-rc1 Code cleanup 30-Sep-2008 14:21
1.9-pre1 Major feature enhancements 09-Sep-2008 17:56
1.8-pre3 Major feature enhancements 24-Jan-2008 01:24
1.8-pre2 Minor feature enhancements 10-Jan-2008 19:25
1.8-pre1 Minor feature enhancements 10-Jan-2008 00:57
1.7-pre2 Major feature enhancements 17-Dec-2007 16:15
1.7-pre1 Major feature enhancements 22-Nov-2007 20:38
1.6-rc5 Minor feature enhancements 29-Oct-2007 14:42
1.6-rc4 Minor feature enhancements 25-Oct-2007 23:27

 Comments

[»] Using ddrescue and SpinRite together
by rtpdave - Sep 20th 2005 13:40:30

I've created a "Quick and Dirty" Perl program which reads a GNU ddrescue 1.0 "logfile" (sector list file), and generates a DOS .bat file of SpinRite 6.0 commands to try to recover the unrecovered regions. After SpinRite has completed its work, you can run ddrescue 1.0 again to add the recovered data to the recovery image. You can get my little Perl program here: http://www.burtonsys.com/download/ddr2sr.zip

Note #1: This little Perl program can be run under any system that supports Perl 4 or 5 (Linux, DOS, Windows, etc.). For tiny compatible Perl 4 implementations for DOS and Windows, see: http://www.burtonsys.com/auxil/#tinyperls

Note #2: ddrescue runs under Linux, and SpinRite runs under MS-DOS or FreeDOS. So (obviously) some rebooting will be required.

Note #3: You must use Antonio Diaz's GNU ddrescue 1.0: http://freshmeat.net/projects/addrescue/ You cannot use ddrescue 0.9 or earlier, nor can you use Garloff's dd_rescue (which is an entirely different program).

Note #4: Gibson Spinrite will set you back U.S. $89. I think it is well worth it (and I have no connection to Gibson, other than as a satisfied SpinRite user). Get it here: http://www.grc.com/sr/spinrite.htm

-Dave

--
dave316 at burtonsys dot com but please no spam

[reply] [top]


[»] Fast, effective, and flexible!
by rtpdave - May 16th 2005 18:32:16

I compared the speed of Antonio's ddrescue 0.9 to the speed of dd_rescue for copying error-free data on a PC with ATA/EIDE drives, and Antonio's ddrescue ran nearly twice as fast as dd_rescue.

Since dying hard disk drives tend to get sicker and sicker as time goes on, I think speed it is important, to improve the success rate of the rescue. ddrescue's better speed could also help with "freezer-based" hard disk drive recovery. Sometimes a dying hard disk drive can be coaxed into working again, briefly, by sealing it in a plastic bag and freezing it in the freezer overnight. (I'm now 1-for-3 recovering hard disk drives with this technique.) But, of course, when you take it out of the freezer and plug it into your computer it starts warming up. You may only have a few minutes to recover your data before the drive warms up and starts failing again. So a faster ddrescue improves your chances of getting all the data off before the drive gets too warm.

The new 1.0pre1 is a gigantic improvement over 0.9! I've not benchmarked it, but I assume that the speed is about the same. However, the new logfile format has many advantages!

The most important advantage is that it enables you to do multiple ddrescue passes to recover your data. For example:

# first, grab most of the error-free areas in a hurry:
ddrescue -B -n /dev/hdd rescued.ima rescued.log
# then try to recover as much of the dicy areas as possible:
ddrescue -B -r 1 /dev/hdd rescued.ima rescued.log
(the "-r 1" is necessary to make it retry the failed areas)

Then put the drive in the freezer overnight (or run SpinRite on it), and then try again:

ddrescue -B -r 1 /dev/hdd rescued.ima rescued.log
(it won't recopy the already copied areas)

You can also run it on just part of the disk, e.g., to try extra hard to recover the most important areas. This example retries extra hard (10x) to recover any bad areas in the first 50 MB of the drive:

ddrescue -B -r 10 -s 52428800 rescued.ima rescued.log

Each time you run it, ddrescue updates the logfile to show which areas of the disk drive or file were successfully copied, which failed to copy, and which are yet to be attempted. It also updates the logfile when you halt it with Ctrl-C, and also saves it every 30 seconds during normal operation (in case of a crash).

When you are done, the logfile also serves as a nice, concise ASCII record of where the good and bad areas are in the copy of the drive or file. I can envision tools and scripts which use that information to identify the damaged files on a rescued disk drive, or which consolidate the good areas of the two copies of the FAT on a FAT16 or FAT32 drive, or which identify the damaged areas that are in "free space" and just mark them as "good" (because their contents don't matter), etc., etc..

ddrescue 1.0pre1 is a wonderful little utility, and (thanks to the simple, well-documented ASCII logfile format) it is nicely extensible.

Great job, Antonio!

-Dave

--
dave316 at burtonsys dot com but please no spam

[reply] [top]


[»] recoverdm
by Folkert van Heusden - Dec 28th 2004 12:18:40

Looks a lot like recoverdm which can also merge multiple recover attempt images (and features a special mode for damaged cd-roms).

--
------------------------ Folkert van Heusden [ www.vanheusden.com ] ------------------------

[reply] [top]


    [»] Re: recoverdm
    by Antonio Diaz Diaz - Dec 29th 2004 06:39:42


    > Looks a lot like recoverdm which can also merge multiple recover attempt

    > images (and features a special mode for damaged cd-roms).

    I think recoverdm is more like a specialized dd.

    Gnu ddrescue tries to copy the non-damaged part of the file as soon as possible. Recoverdm copies data linearly, like dd, and loses too much time trying to read bad sectors.

    Recoverdm is specialized for linux (all functions in dev.c are no-ops except for linux).

    Gnu ddrescue is so much more efficient "merging" backups than recoverdm + mergebad that I have had to change the description of what ddrescue does to make this efficiency clear to the user.

    [reply] [top]


[»] Deją vue
by Kurt Garloff - Aug 12th 2004 15:10:15

There must be an error in the matrix: http://freshmeat.net/projects/ddrescue/

--
Kurt Garloff

[reply] [top]


    [»] Re: Deją vue
    by Antonio Diaz Diaz - Aug 12th 2004 15:43:24


    > There must be an error in the matrix: http://freshmeat.net/projects/ddrescue/


    No, there is not. Simply this is my own version of dd_rescue (as there are many versions of every *nix tool out there).
    It should have been released months ago, but I am yet waiting for Savannah.


    Regards, Antonio Diaz.

    [reply] [top]


      [»] Re: Deją vue
      by vade79 - Aug 12th 2004 17:20:30

      probably none of my business; but there is having many people making programs that do the same thing, and then there is using virtually the exact same name. things like this make for confusion.

      [reply] [top]


      [»] Re: Deją vue
      by Kurt Garloff - Aug 12th 2004 23:29:09


      > No, there is not. Simply this is my own

      > version of dd_rescue (as there are many

      > versions of every *nix tool out there).

      > It should have been released months ago,

      > but I am yet waiting for Savannah.

      Hmm, it is normally considered best if improvements are
      contributed back to the original program. Any specific reason
      why this can't be done here?

      --
      Kurt Garloff

      [reply] [top]


        [»] Re: Deją vue
        by Antonio Diaz Diaz - Aug 13th 2004 08:54:21


        > Hmm, it is normally considered best if improvements are contributed back to the original program.

        >Any specific reason why this can't be done here?

        Yes, the size of the change is far larger than the program itself.
        It makes sense to contribute some hundred lines to a big project like gcc or linux. But Diaz's dd_rescue does the same job (with better integration) that Garloff's dd_rescue + dd_rhelp, and is one order of magnitude smaller.
        Would you accept such a change to your program and still call it _your_ program?

        [reply] [top]


          [»] Re: Deją vue
          by Kurt Garloff - Aug 14th 2004 04:53:05


          > Yes, the size of the change is far

          > larger than the program itself.

          > It makes sense to contribute some

          > hundred lines to a big project like gcc

          > or linux. But Diaz's dd_rescue does the

          > same job (with better integration) that

          > Garloff's dd_rescue + dd_rhelp, and is

          > one order of magnitude smaller.

          > Would you accept such a change to your

          > program and still call it _your_

          > program?

          OK, a new project makes sense then.

          --
          Kurt Garloff

          [reply] [top]


          [»] Re: Deją vue
          by Dag Wieers - Sep 3rd 2004 15:01:16


          > Yes, the size of the change is far

          > larger than the program itself.

          > It makes sense to contribute some

          > hundred lines to a big project like gcc

          > or linux. But Diaz's dd_rescue does the

          > same job (with better integration) that

          > Garloff's dd_rescue + dd_rhelp, and is

          > one order of magnitude smaller.

          > Would you accept such a change to your

          > program and still call it _your_

          > program?

          And how would you want packagers to package a tool with completely the same name (and an older version) ??

          Please take another name for the project, or consider your program obsoleted by Kurt's version at any time.

          [reply] [top]


            [»] Re: Deją vue
            by Antonio Diaz Diaz - Sep 3rd 2004 17:01:16


            > And how would you want packagers to package a tool with completely the same name (and an older version) ??

            >

            > Please take another name for the project, or consider your program obsoleted by Kurt's version at any time.

            The names are no more the same. Mine is ddrescue, Garloff's is dd_rescue. But even if they were, it is in the interest of packagers to diferentiate them if they want to deliver a better, faster and smaller program.

            [reply] [top]




© Copyright 2008 SourceForge, Inc., All Rights Reserved.
About freshmeat.net •  Privacy Statement •  Terms of Use •  Trademark Guidelines •  Advertise •  Contact Us • 
ThinkGeek •  Slashdot  •  Linux.com •  SourceForge.net  •  Jobs