Ddrescue - Revision history

Bkoenig: Migrated.

2014-06-27T20:18:58Z

Migrated.

Psullivan at 19:08, 28 March 2014

2014-03-28T19:08:39Z

Sarah.walker at 22:55, 1 August 2013

2013-08-01T22:55:58Z

Paulm at 18:39, 23 May 2013

2013-05-23T18:39:34Z

Paulm at 18:35, 23 May 2013

2013-05-23T18:35:15Z

Paulm at 20:14, 4 April 2013

2013-04-04T20:14:35Z

Paulm: Created page with "When disk fail or start failing you should back it up by making a copy of the hard drive '''then''' running the backup process. in simple cases the `dd` command can …"

2013-04-04T20:04:02Z

Created page with "When disk fail or start failing you should back it up by making a copy of the hard drive '''then''' running the backup process. in simple cases the <code>dd</code> command can …"

New page

When disk fail or start failing you should back it up by making a copy of the hard drive '''then''' running the backup process.

in simple cases the <code>dd</code> command can be use but it will often choke on failing drives.

GNU <code>ddrescue</code> is a much better tool to use, it will do a very good job of getting a data off a failing disk. Beware it can take a very long time to do so if a drive is really bad. It should not be confused with <code>dd_rescue</code>. Though both do a similar job GNU <code>ddrescue</code> is the superior tools.

to run it you need to do:

<code>sudo ddrescue /hard/drescue output.dd log.file</code>

e.g.
<code>sudo ddrescue /dev/sda1 99999.dd 99999.log</code>

Use the ticket number to name the output file and log. Including the log is very important. <code>ddresuce</code> will run with out it but the log file enables the process to resume if it is interrupted for any reason.

Note it is possible to make a copy of the whole disc, rather than individual partitions (if for instance, there are multiple partitions to backup) but it makes it a little trickier to read the resulting image.

<code>ddrescue</code> tries very hard to rescue the data* and even it can't read it will rescue the remaining data in such a way as to preserve the file system structure (it leaves the unreadble parts blank but this won't affect other files).

The full manual is here:
[[https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html]]

*Rather than try to read data in a linear fashion it divides the disk up into sections. If it has trouble reading a section it divides it again, splitting it up until it finds the smallest unreadable section.

← Older revision		Revision as of 20:18, 27 June 2014
Line 1:		Line 1:
−	{{~~Migrate~~}}	+	{{Migrated}}
		+	[https://docs.google.com/document/d/1pD9evN0e3xJQ-u_iztLdVupH9SeQzNW7f73l3pIb4is/edit?usp=sharing Link]
		+

	When disk fail or start failing you should back it up by making a copy of the hard drive '''then''' running the backup process.		When disk fail or start failing you should back it up by making a copy of the hard drive '''then''' running the backup process.

← Older revision		Revision as of 19:08, 28 March 2014
Line 1:		Line 1:
		+	{{Migrate}}
		+
	When disk fail or start failing you should back it up by making a copy of the hard drive '''then''' running the backup process.		When disk fail or start failing you should back it up by making a copy of the hard drive '''then''' running the backup process.

← Older revision		Revision as of 18:39, 23 May 2013
Line 13:		Line 13:

	Use the ticket number to name the output file and log. Including the log is very important. <code>ddresuce</code> will run with out it but the log file enables the process to resume if it is interrupted for any reason.		Use the ticket number to name the output file and log. Including the log is very important. <code>ddresuce</code> will run with out it but the log file enables the process to resume if it is interrupted for any reason.
		+
		+	'''Make sure to note which drive you put the files on.''' They are labeled IDE1, SATA1, IDE2 etc.

	Note it is possible to make a copy of the whole disc, rather than individual partitions (if for instance, there are multiple partitions to backup) but it makes it a little trickier to read the resulting image.		Note it is possible to make a copy of the whole disc, rather than individual partitions (if for instance, there are multiple partitions to backup) but it makes it a little trickier to read the resulting image.

← Older revision		Revision as of 18:35, 23 May 2013
Line 28:		Line 28:

	1. Rather than try to read data in a linear fashion it divides the disk up into sections. If it has trouble reading a section it divides it again, splitting it up until it finds the smallest unreadable section.		1. Rather than try to read data in a linear fashion it divides the disk up into sections. If it has trouble reading a section it divides it again, splitting it up until it finds the smallest unreadable section.
		+
		+
		+	[[Category:Tech support]]

@@ Line 11: / Line 11: @@
 e.g.
 <code>sudo ddrescue /dev/sda1 99999.dd 99999.log</code>
 Use the ticket number to name the output file and log. Including the log is very important. <code>ddresuce</code> will run with out it but the log file enables the process to resume if it is interrupted for any reason.

@@ Line 1: / Line 1: @@
 When disk fail or start failing you should back it up by making a copy of the hard drive '''then''' running  the backup process.
-in simple cases the <code>dd</code> command can be use but it will often choke on failing drives.
+in simple cases the <code>dd</code> command can be used but it will often choke on failing drives.
-GNU <code>ddrescue</code> is a much better tool to use, it will do a very good job of getting a data off a failing disk. Beware it can take a very long time to do so if a drive is really bad. It should not be confused with <code>dd_rescue</code>. Though both do a similar job GNU <code>ddrescue</code> is the superior tools.
+GNU <code>ddrescue</code> is a much better tool to use, it will do a very good job of getting a data off a failing disk. N.B. it can take a very long time to do so if a drive is really bad. It should not be confused with <code>dd_rescue</code>. Though both do a similar job GNU <code>ddrescue</code> is the superior tool.
 to run it you need to do:
-<code>sudo ddrescue /hard/drescue output.dd log.file</code>
+<code>sudo ddrescue /hard/drive output.dd log.file</code>
 e.g.
@@ Line 17: / Line 17: @@
-<code>ddrescue</code> tries very hard to rescue the data* and even it can't read it will rescue the remaining data in such a way as to preserve the file system structure (it leaves the unreadble parts blank but this won't affect other files).
+GNU <code> ddrescue</code> will work with any block device e.g. cdroms, usb thumb drives, not just hard drives.
 The full manual is here:
-[[https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html]]
+https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
-*Rather than try to read data in a linear fashion it divides the disk up into sections. If it has trouble reading a section it divides it again, splitting it up until it finds the smallest unreadable section.
+. Rather than try to read data in a linear fashion it divides the disk up into sections. If it has trouble reading a section it divides it again, splitting it up until it finds the smallest unreadable section.