/[clonezilla-sysresccd]/trunk/www/2doc/doc/recover.html
ViewVC logotype

Annotation of /trunk/www/2doc/doc/recover.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 52 - (hide annotations)
Thu May 20 16:24:26 2010 UTC (10 years, 6 months ago) by sng
File MIME type: text/html
File size: 20757 byte(s)
renaming html2offline to html2doc, fixing minor offline things, and updating oggline docs
1 sng 49 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2     <html>
3     <head>
4     <link rel="alternate" type="application/rss+xml" title="RSS" href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd.rss">
5     <link rel="shortcut icon" href="favicon.ico">
6 sng 52 <title>Clonezilla-SysRescCD - Offline Documentation: Data Recovery</title>
7 sng 49 <style type="text/css">
8     body { font-family: Arial, 'sans serif'; color: black; font-size: 12pt; background : url(null) fixed no-repeat; background-color: #333333; padding: 0; margin: 0; margin-top: 5px; margin-bottom: 5px; }
9    
10    
11    
12     #header {position:relative; display: block; width: 980px; height: 121px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/header.png');clear:both;}
13     #header h2{ color: #FFE6BC; font-weight: bold; font-size: 2.2em; margin:0; padding:0; padding-left: 10px; padding-top: 7px; text-shadow: #333333 2px 2px 4px;}
14     #header h3{ color: #FFE6BC; font-weight: bold; font-size: 1.8em; margin:0; padding: 0; padding-left: 10px; text-shadow: #333333 2px 2px 4px;}
15     #header h4{ color: #FFE6BC; font-weight: bold; font-size: 1.2em; margin:0; padding: 0; padding-left: 10px; padding-right: 10px; text-shadow: #333333 2px 2px 4px;}
16     #header a {text-decoration:none;}
17    
18     #contarea {display: block; width: 980px; margin: auto; padding: auto; background-color: #FFF2DD; clear:both;}
19    
20     #linkline { width: 980px; height: 29px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/linkline.png');clear:both; }
21     #linkline a{float: left; color: #FFE6BC; font-weight: bold; font-size: 0.8em; text-decoration: none; text-shadow: #333333 2px 2px 4px; padding-left: 10px; padding-right: 10px; padding-top: 5px;}
22     #linkline a:visited{color: #FFE6BC;}
23     #linkline a:hover{color: #333333;}
24     #linkline a.here {color: #333333; text-decoration: none;}
25    
26     #lastupdate {float: right; display: block; text-align: right; margin: 0; margin-top: -1.2em; padding: 0; padding-right: 15px;}
27    
28     #rss { float: right; text-align: right; padding-top: 3px;}
29    
30     #docline-top { float: right; padding-right: 40px; text-align: right; }
31     #docline-bottom { float: right; padding-right: 40px; text-align: right; font-size: 0.8em; padding-top: 15px; }
32     #docline-bottom a{ padding-left: 10px; padding-right: 10px; }
33    
34     #menu { float: right; display: block; width: 170px; margin: auto; padding: 15px; font-size: 0.8em; font-weight: bold; background-color: #FFE6BC;}
35     #menu h1 {color: #990000; font-size: 1.8em;text-shadow: gray 2px 2px 4px;}
36     #menu a,a:visited{ color: black; text-decoration: none; font-weight: normal;}
37     #menu a:hover{ text-decoration: underline;}
38     #menu p{ margin-bottom: 10px;}
39    
40     #content { float: left; display: block; width: 950px; margin: auto; padding: 15px;}
41    
42    
43     #footer {display: block; width: 980px; height: 100px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/footer.png');clear:both;text-shadow: #333333 2px 2px 4px;}
44     #footer p{color: #FFE6BC; font-weight: bold; padding:15px; padding-left: 10px;}
45     #footer a,a:visited{color: #FFE6BC; font-weight: bold; text-decoration:none;}
46     #footer a:hover{ color: #333333; text-decoration: none;}
47    
48    
49     #content H1,H2,H3,H4{color: #990000; text-align: left;}
50     #content H2{margin-top: 2em;}
51     #content H3{margin-top: 1.5em}
52     #content H4{margin-top: 1em}
53     #content li { margin-top: 1em;}
54     #content a,a:active,a:visited{text-decoration: none; color: #4075CA; font-weight: normal;}
55     #content a:hover{text-decoration: underline; font-weight: normal;}
56     #content .hidden{ display:none; }
57     #content p,td,table,tr,li { font-family: Arial, 'sans serif'; }
58     #content .nav{margin-left: 0pt;}
59     #content .newcode{font-family : "Courier New", Courier, monospace; font-weight: bold; background-color: #F2F2F2; border: solid 1px #DEDEDE;padding: 20pt;}
60     #content .note{margin-top: 30pt; margin-bottom: 30pt; text-align: left; background-color: #FFEFEF; border: double 3px; border-color: #FFD5D5;}
61     #content hr{color: Black; background-color: Black; height: 1px; border: none;}
62     #content .header-news{margin-top: 2em; margin-left: 25pt; font-weight: bold; color: #990000;}
63     #content .item-news{margin-left: 45pt; margin-right: 45pt;}
64     #content .otherpage{border: solid 1px darkgoldenrod; padding: 20pt; background-color: lemonchiffon;}
65     #content IMG {display: block; margin-left: auto; margin-right: auto; }
66     #content .red{color: white; background-color: Red; font-weight: bold;}
67     #lphp{text-align: right; padding-left: 10px; padding-right: 10px; padding-top: 50px; float: right;}
68     #lphp a{padding-left: 5px;}
69     </style>
70     <META NAME="Keywords" CONTENT="multiboot Multi Boot bootable cd rescue clonezilla sysresccd backup restore samba">
71     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
72    
73     </head>
74    
75     <body>
76     <div id="header">
77     <div id="lphp" style=""><a target="_blank" href="onepage.html"><img src="images/chain.png" border="0" /></a><a target="_blank" href="printable.php"><img src="images/print_it.png" border="0" /></a></div>
78     <H2>Clonezilla-SysRescCD</H2>
79 sng 52 <H3>Offline Documentation: Data Recovery</H3>
80 sng 49 <div style="margin:0; padding: 3px; width: 980; position relative;">
81     <div style="position: absolute; left: 0px;"><H4>26/03/2010 - v 3.1.0</H4></div>
82     <div style="position: absolute; right: 0px;"><H4>Last update: 18/05/2010</H4></div>
83     </div>
84     </div>
85     <div id="linkline">
86    
87    
88     <!-- <a href="features.html">Features</a>-->
89 sng 52 <a class="here" href="../README.html">Offline Documentation</a>
90 sng 49
91    
92    
93    
94    
95     <div id="rss">
96     <a href="clonezilla-sysresccd.rss"><img src="images/rss-orange-11.png" width="30" height="14" border="0"/></a>
97     </div>
98     <!-- docline-top-->
99     <div id="docline-top"> <a href="partitions.html">&lt; PREV</a> <a href="../README.html">UP</a> <a href="own-scripts.html">NEXT &gt;</a> </div>
100     </div>
101     <div id="contarea">
102     <div id="content">
103     <a name="recover-top"></a>
104    
105     <!-- On the CD -->
106    
107     <H2 style="margin-top: 0;"><a name="recover-intro"></a>Intro <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H2>
108    
109     <p>Deleted or "lost" files can be recovered from failed or formatted drives and partitions, cdroms and memory cards using the software available in <b>SystemRescueCD</b>.
110    
111     Unless you can rule out hardware failure, you must not write to the failed device. The following software will passively try to recover your data from failed or failing hardware. If your data is not replaceable, do not attempt to write to the failed device if the following applications do not work but seek professional advice instead.<br>
112     <br>
113     If your device is damaged, it is advisable to image the device and work on the image file for data recovery. If hardware failure is not the problem, you can recover data directly from the device.<br>
114     <br>
115     To recover data from a failed device, you will need another device of equal or greater storage capacity onto which to save your data. If you need to make an image of the failed device, you will need yet another quantity of space.<br>
116     <br>
117     I should state here, that I haven't used any of these tools recently (other than plain and simple <b>dd</b>, a long time ago, which I found to be very slow), so I couldn't recommend any of them. Any comments on a tool's usability found in this page, is just what I found on the Net.</p>
118    
119    
120     <!-- Partition recovery -->
121     <H2><a name="recover-dr"></a>Partition recovery <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H2>
122    
123     <p>If you made a mistake while partitioning and the partition no longer appears in the partition table, so long as you have not written data in that space, all your data is still there and can be restored.</p>
124    
125     <p>When changing the partition table on your hard drive, you must ensure that no partition on the disk is mounted. This includes swap space. In order to restore your partition, execute:</p>
126    
127     <p class="newcode">swapoff -a<br>
128     parted /dev/old_disk</p>
129    
130     <p>Then, use the rescue option:</p>
131    
132     <p class="newcode">rescue START END</p>
133    
134     <p>where <b>START</b> is the area of the disk where you believe the partition began and <b>END</b> is it's end. If parted finds a potential partition, it will ask you if you want to add it to the partition table.</p>
135    
136     <p><b>Note:</b> <a href="#recover-testdisk">TestDisk</a> can also be used to recover a "lost" partition.</p>
137    
138     <!-- Disk recovery -->
139     <H2><a name="recover-dr"></a>Disk / files recovery <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H2>
140    
141     <!-- dd -->
142     <H3><a name="recover-dd"></a>Using dd <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H3>
143    
144     <p>In order to duplicate a disk to another disk, execute</p>
145    
146     <p class="newcode">dd if=/dev/old_disk of=/dev/new_disk conv=noerror,sync</p>
147    
148     <p>or to create an image file</p>
149    
150     <p class="newcode">dd if=/dev/old_disk of=image_file conv=noerror</p>
151    
152     <p>Be careful, if you are copying a disk, the destination must also be a disk, not a partition. If you are copying a partition, the destination partition must be large enough. Copying the whole disk is recommended.<br>
153     <br>
154     To speed up the copy process, you can append <b>bs=8k</b>, it will read/write the disk by 16 sectors at a time.</p>
155    
156    
157     <!-- dd_rescue -->
158     <H3><a name="recover-dd-rescue"></a>Using dd_rescue <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H3>
159    
160     <p>Like dd, <a href="http://www.garloff.de/kurt/linux/ddrescue/" target="_blank">dd_rescue</a> does copy data from one file or block device to another. You can specify file positions (called seek and skip in dd). There are several differences:</p>
161    
162     <ul>
163     <li>dd_rescue does not provide character conversions.</li>
164     <li>The command syntax is different. Call <b>dd_rescue -h</b>.</li>
165     <li>dd_rescue does not abort on errors on the input file, unless you specify a maximum error number. Then dd_rescue will abort when this number is reached.</li>
166     <li>dd_rescue does not truncate the output file, unless asked to.</li>
167     <li>You can tell dd_rescue to start from the end of a file and move backwards.</li>
168     <li>It uses two block sizes, a large (soft) block size and a small (hard) block size. In case of errors, the size falls back to the small one and is promoted again after a while without errors.</li>
169     <li>It does not (yet) support non-seekable in- or output.</li>
170     </ul>
171    
172     <p>In order to duplicate a disk to another disk, execute</p>
173    
174     <p class="newcode">dd_rescue -A -v /dev/old_disk /dev/new_disk</b></p>
175    
176     <p>or to create an image file</p>
177    
178     <p class="newcode">dd_rescue -A -v /dev/old_disk image_file</b></p>
179    
180     <p>The copying should go very quickly until it hits a bad sector and then it will slow down to take smaller chunks of data. People have reported very good results with this technique.</p>
181    
182    
183     <!-- GNU ddrescue -->
184     <H3><a name="recover-gnu-ddrescue"></a>Using GNU ddrescue <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H3>
185    
186     <p>The GNU site describes GNU ddrescue as a data recovery tool, and lists these features:</p>
187    
188     <ul>
189     <li>It copies data from one file or block device (hard disc, CD-ROM, etc) to another, trying hard to rescue data in case of read errors.</li>
190     <li>It 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.</li>
191     <li>It is designed to be fully automatic.</li>
192     <li>If you use the log file 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.</li>
193     <li>The log file is periodically saved to disc. So in case of a crash you can resume the rescue with little recopying.</li>
194     <li>If you have two or more damaged copies of a file, CD-ROM, etc, and run GNU ddrescue on all of them, one at a time, with the same output file, you will probably obtain a complete and error-free file. The probability of having damaged areas at the same places on different input files is very low. Using the log file, only the needed blocks are read from the second and successive copies.</li>
195     <li>The same log file can be used for multiple commands that copy different areas of the file, and for multiple recovery attempts over different subsets.</li>
196     </ul>
197    
198     <p>The algorithm of GNU ddrescue is as follows:</p>
199    
200     <ol>
201     <li>Optionally read a log file describing the status of a multi-part or previously interrupted rescue.</li>
202     <li>Read the non-damaged parts of the input file, skipping the damaged areas, until the requested size is reached, or until interrupted by the user.</li>
203     <li>Try to read the damaged areas, splitting them into smaller pieces and reading the non-damaged pieces, until the hardware block size is reached, or until interrupted by the user.</li>
204     <li>Try to read the damaged hardware blocks until the specified number of retries is reached, or until interrupted by the user.</li>
205     <li>Optionally write a log file for later use.</li>
206     </ol>
207    
208     <p><b>Note:</b> GNU ddrescue is considered to be the best recovery tool available.</p>
209    
210     <p>In order to duplicate a disk to another disk, execute</p>
211    
212     <p class="newcode">ddrescue -vr3 /dev/old_disk /dev/new_disk logfile</b></p>
213    
214     <p>or to create an image file</p>
215    
216     <p class="newcode">ddrescue -vr3 /dev/old_disk image_file logfile</b></p>
217    
218     <p>If the disk is failing fast and you want to get the most data out of it on the first try, you should probably use "<b>-n</b>" on the first run. This will avoid splitting error areas. Subsequent runs can use "<b>-r1</b>" or "<b>-r3</b>", without "<b>-n</b>", to retry those error areas.</p>
219    
220     <p>To summarise, we execute:</p>
221    
222     <p class="newcode">ddrescue -vn /dev/old_disk image_file logfile<br>
223     ddrescue -v -r3 -C /dev/old_disk image_file logfile</p>
224    
225     <p><b>Note:</b> When working with CD-ROMs you should probably specific "<b>-b 2048</b>"</p>
226    
227    
228     <!-- Foremost -->
229     <H3><a name="recover-foremost"></a>Using Foremost <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H3>
230    
231     <p><a href="http://foremost.sourceforge.net/" target="_blank">Foremost</a> is a console program to recover files based on their headers, footers, and internal data structures. This process is commonly referred to as data carving. Foremost can work on image files, such as those generated by dd, Safeback, Encase, etc, or directly on a drive. The headers and footers can be specified by a configuration file or you can use command line switches to specify built-in file types. These built-in types look at the data structures of a given file format allowing for a more reliable and faster recovery.</p>
232    
233     <p>It can be run on an image file created with any of the above tools, to extract files:</p>
234    
235     <p class="newcode">foremost -i image -o /recovery/foremost</p>
236    
237     <p>Foremost can be instructed to recover only specific file types, using the <b>-t</b> command line parameter. In the following example Foremost will extract only jpg files:</p>
238    
239     <p class="newcode">foremost -t jpg -i image -o /recovery/foremost</p>
240    
241     <p>Available types are: jpg, gif, png, bmp, avi, exe (Windows binaries and DLLs), wav, riff, wmv (will extract wma also), mov, pdf, ole (will extract any file using the OLE file structure; this includes PowerPoint, Word, Excel, Access, and StarWriter), doc, zip (will extract .jar files and Open Office docs as well; this includes SXW, SXC, SXI, and SX? for undetermined OpenOffice files), rar, html and cpp.</p>
242    
243     <!-- TestDisk -->
244     <H3><a name="recover-testdisk"></a>Using TestDisk <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H3>
245    
246     <p><a href="http://www.cgsecurity.org/wiki/TestDisk" target="_blank">TestDisk</a> was primarily designed to help <b>recover "lost" partitions</b> and/or <b>make non-booting disks bootable again</b> <i>when</i> these symptoms are caused by <i>faulty software</i>, certain types of <i>viruses</i> or <i>human error</i> (such as <i>accidentally</i> deleting a Partition Table). Partition table recovery using TestDisk is really easy.<br>
247     <br>
248     TestDisk can</p>
249    
250     <ul>
251     <li> Fix partition table, recover deleted partition</li>
252     <li> Recover FAT32 boot sector from its backup</li>
253     <li> Rebuild FAT12/FAT16/FAT32 boot sector</li>
254     <li> Fix FAT tables</li>
255     <li> Rebuild NTFS boot sector</li>
256     <li> Recover NTFS boot sector from its backup</li>
257     <li> Fix MFT using MFT mirror</li>
258     <li> Locate ext2/ext3 Backup SuperBlock</li>
259     </ul>
260    
261     <p>Some great tutorials are available at TestDisk's site: "<a href="http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step" target="_blank">TestDisk Step By Step</a>", "<a href="http://www.cgsecurity.org/wiki/Running_TestDisk" target="_blank">Running TestDisk</a>", "<a href="http://www.cgsecurity.org/wiki/Data_Recovery_Examples" target="_blank">Data Recovery Examples</a>" etc.
262     </p>
263    
264     <!-- PhotoRec -->
265     <H3><a name="recover-photorec"></a>Using PhotoRec <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H3>
266    
267     <p><a href="http://www.cgsecurity.org/wiki/PhotoRec" target ="_blank">PhotoRec</a> is file data recovery software designed to recover "lost" files including video, documents and archives from Hard Disks and CDRom and "lost" pictures (thus, its 'Photo Recovery' name) from digital camera memory. PhotoRec ignores the filesystem and goes after the underlying data, so it will still work even if your media's filesystem has been severely damaged or re-formatted.<br>
268     <br>
269     For more safety, PhotoRec uses read-only access to handle the drive or memory support you are about to recover "lost" data from.<br>
270     <br>
271     <b>Important</b>: As soon as a pic or file is accidentally deleted, or you discover any missing, do NOT save any more pics or files to that memory device or hard disk drive; otherwise you may overwrite your "lost" data. This means that even using PhotoRec, you must not choose to write the recovered files to the same partition they were stored on.<br>
272     <br>
273     A great tutorial titled "<a href="http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step" target="_blank">PhotoRec Step By Step</a>" can be found at PhotoRec's site.</p>
274    
275    
276    
277     <!-- Links -->
278     <H2><a name="recover-links"></a>Links &amp; resources <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H2>
279    
280     <p>This page is a compilation of the following pages:</p>
281    
282     <p>DataRecovery<br>
283     &nbsp;&nbsp;&nbsp;&nbsp;<a href="https://help.ubuntu.com/community/DataRecovery" target="_blank">https://help.ubuntu.com/community/DataRecovery</a></p>
284    
285     <p>Hard Drive Recovery, Ubuntu-Style<br>
286     &nbsp;&nbsp;&nbsp;&nbsp;<a href="http://blogs.sun.com/superpat/tags/ddrescue" target="_blank">http://blogs.sun.com/superpat/tags/ddrescue</a></p>
287    
288     <p>Recover Data and (deleted) Partition with Linux from Hard Drives, CD-ROMs or DVDs<br>
289     &nbsp;&nbsp;&nbsp;&nbsp;<a href="http://sysblogd.wordpress.com/2008/01/05/data-recovery-with-linux-from-hard-drives-cd-roms-or-dvds/" target="_blank">http://sysblogd.wordpress.com/2008/01/05/data-recovery-with-linux-from-hard-drives-cd-roms-or-dvds/</a></p>
290    
291     <p>dd_rescue<br>
292     &nbsp;&nbsp;&nbsp;&nbsp;<a href="http://www.garloff.de/kurt/linux/ddrescue/" target="_blank">http://www.garloff.de/kurt/linux/ddrescue/</a></p>
293    
294     <p>gddrescue: a tool for recovering data from damaged media<br>
295     &nbsp;&nbsp;&nbsp;&nbsp;<a href="http://debaday.debian.net/2007/12/12/gddrescue-a-tool-for-recovering-data-from-damaged-media/" target="_blank">http://debaday.debian.net/2007/12/12/gddrescue-a-tool-for-recovering-data-from-damaged-media/</a></p>
296    
297     <p>Foremost<br>
298     &nbsp;&nbsp;&nbsp;&nbsp;<a href="http://foremost.sourceforge.net/" target="_blank">http://foremost.sourceforge.net/</a></p>
299    
300     <p>TestDisk<br>
301     &nbsp;&nbsp;&nbsp;&nbsp;<a href="http://www.cgsecurity.org/wiki/TestDisk" target="_blank">http://www.cgsecurity.org/wiki/TestDisk</a></p>
302    
303     <p>PhotoRec<br>
304     &nbsp;&nbsp;&nbsp;&nbsp;<a href="http://www.cgsecurity.org/wiki/PhotoRec" target="_blank">http://www.cgsecurity.org/wiki/PhotoRec</a></p>
305    
306    
307     </div>
308    
309    
310    
311     <!--<a name="template-top"></a>-->
312    
313     <div id="footer">
314     <div id="docline-bottom"> <a href="partitions.html">&lt; PREV</a> <a href="../README.html">UP</a> <a href="own-scripts.html">NEXT &gt;</a> </div>
315     <p>Copyright: &#169; <a href="mailto:&#115;&#110;&#103;&#064;&#104;&#101;&#108;&#108;&#117;&#103;&#046;&#103;&#114;?subject=About Clonezilla-SysRescCD v 3.1.0">Spiros Georgaras</a>, 2007-2010<br /><br/>
316     Hosted by <a href="http://www.hellug.gr" target="_blank" title="Hellenic Linux User Group">HEL.L.U.G.</a></p>
317     </div>
318     </div>
319     </body>
320     </html>

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26