<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: reiserfs and dd_rescue for data recovery</title>
	<atom:link href="http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf/feed" rel="self" type="application/rss+xml" />
	<link>http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=dd_rescue_and_reiserf</link>
	<description>random musings</description>
	<lastBuildDate>Sun, 22 May 2011 14:02:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Audrey Phillips</title>
		<link>http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf/comment-page-1#comment-191190</link>
		<dc:creator>Audrey Phillips</dc:creator>
		<pubDate>Wed, 26 May 2010 01:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://javier.rodriguez.org.mx/?p=69#comment-191190</guid>
		<description>Data Recovery is a very costly option that is why you should always check your storage media for any signs of wear and tear.,:&#039;</description>
		<content:encoded><![CDATA[<p>Data Recovery is a very costly option that is why you should always check your storage media for any signs of wear and tear.,:&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jharris1993</title>
		<link>http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf/comment-page-1#comment-184485</link>
		<dc:creator>jharris1993</dc:creator>
		<pubDate>Mon, 14 Dec 2009 19:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://javier.rodriguez.org.mx/?p=69#comment-184485</guid>
		<description>When running dd_rescue - don&#039;t forget the &quot;-r&quot; option! (reverse copy)

What you can do is this - try it running dd_rescue the &quot;normal&quot; way and then - when it finishes (or hangs, or whatever) and you have bad blocks, try running the same command again with the &quot;-r&quot; option.  It will take the same drive, the same output file, the same bad-block file, etc - and do the whole job again filling in the places where it was able to get good data.

example:  A failing 20 gig partition on a 60 gig drive - copying to a file (so I can loop-mount and extract data before using the failed hard drive as a target for my 12 gage shotgun!)

Viz: dd_rescue -v -l 60gigp1log.txt -o 60gigp1bb.txt /dev/sdg1 ./60gigp1.bin

-v = verbose output (tell me a LOT about what you&#039;re doing)
-l = name of logfile to write output to (important!)
-o = name of bad-block file - where the locations of potentially bad blocks are found (*very* important!)
/dev/sdg1 (the drive that is failing)
./60gigp1.bin = the binary &quot;image&quot; being made by dd_rescue.

I ran the dd_rescue command shown above, and it went through the drive about 1/3 of the way and then just bogged-down.  I cancelled out with a ctl-C and re-ran the same command with &quot;-r&quot;

Viz:  dd_rescue -r -v -l 60gigp1log.txt -o 60gigp1bb.txt /dev/sdg1 ./60gigp1.bin

It then started attacking the drive from the &quot;other side&quot;.

A couple of repetitions of this and I had a complete binary with no bad-blocks.  Of course, I have not yet loop-mounted the binary so I don&#039;t know what kind of trouble the actual filesystem might be in - but once you have a &quot;clean&quot; (or nearly clean) binary image of the partition, you are in a position to let the file system&#039;s own recovery tools (as noted in the previous post) do their job.

What say ye?

Jim</description>
		<content:encoded><![CDATA[<p>When running dd_rescue &#8211; don&#8217;t forget the &#8220;-r&#8221; option! (reverse copy)</p>
<p>What you can do is this &#8211; try it running dd_rescue the &#8220;normal&#8221; way and then &#8211; when it finishes (or hangs, or whatever) and you have bad blocks, try running the same command again with the &#8220;-r&#8221; option.  It will take the same drive, the same output file, the same bad-block file, etc &#8211; and do the whole job again filling in the places where it was able to get good data.</p>
<p>example:  A failing 20 gig partition on a 60 gig drive &#8211; copying to a file (so I can loop-mount and extract data before using the failed hard drive as a target for my 12 gage shotgun!)</p>
<p>Viz: dd_rescue -v -l 60gigp1log.txt -o 60gigp1bb.txt /dev/sdg1 ./60gigp1.bin</p>
<p>-v = verbose output (tell me a LOT about what you&#8217;re doing)<br />
-l = name of logfile to write output to (important!)<br />
-o = name of bad-block file &#8211; where the locations of potentially bad blocks are found (*very* important!)<br />
/dev/sdg1 (the drive that is failing)<br />
./60gigp1.bin = the binary &#8220;image&#8221; being made by dd_rescue.</p>
<p>I ran the dd_rescue command shown above, and it went through the drive about 1/3 of the way and then just bogged-down.  I cancelled out with a ctl-C and re-ran the same command with &#8220;-r&#8221;</p>
<p>Viz:  dd_rescue -r -v -l 60gigp1log.txt -o 60gigp1bb.txt /dev/sdg1 ./60gigp1.bin</p>
<p>It then started attacking the drive from the &#8220;other side&#8221;.</p>
<p>A couple of repetitions of this and I had a complete binary with no bad-blocks.  Of course, I have not yet loop-mounted the binary so I don&#8217;t know what kind of trouble the actual filesystem might be in &#8211; but once you have a &#8220;clean&#8221; (or nearly clean) binary image of the partition, you are in a position to let the file system&#8217;s own recovery tools (as noted in the previous post) do their job.</p>
<p>What say ye?</p>
<p>Jim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diego</title>
		<link>http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf/comment-page-1#comment-69999</link>
		<dc:creator>Diego</dc:creator>
		<pubDate>Wed, 08 Aug 2007 03:43:15 +0000</pubDate>
		<guid isPermaLink="false">http://javier.rodriguez.org.mx/?p=69#comment-69999</guid>
		<description>Please forgive my total lack of patience, the process ended just fine:

327035 directory entries were hashed with &quot;r5&quot; hash.
        &quot;r5&quot; hash is selected
Flushing..finished
        Read blocks (but not data blocks) 103806568
                Leaves among those 116376
                Objectids found 324508

Pass 1 (will try to insert 116376 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished
0%....20%....40%....60%....80%....100%
Flushing..finished
        116376 leaves read
                116176 inserted
                        - pointers in indirect items pointing to metadata 7 (zeroed)
                200 not inserted
        non-unique pointers in indirect items (zeroed) 2984
####### Pass 2 #######

Pass 2:
0%....20%....40%....60%vpf-10260: The file we are inserting the new item (134320 14974 0xae532001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
....80%....100%
Flushing..finished
        Leaves inserted item by item 200
Pass 3 (semantic):
####### Pass 3 #########
vpf-10680: The file [249620 343697] has the wrong block count in the StatData (1414608) - corrected to (1403248)
vpf-10680: The file [335046 335060] has the wrong block count in the StatData (23448) - corrected to (22904)
vpf-10680: The file [241839 243017] has the wrong block count in the StatData (64) - corrected to (56)
Flushing..finished
        Files found: 285283
        Directories found: 33617
        Symlinks found: 4426
        Others: 1167
Pass 3a (looking for lost dir/files):
####### Pass 3a (lost+found pass) #########
Looking for lost directories:
Flushing..finished
Pass 4 - finished
        Deleted unreachable items 2
Flushing..finished
Syncing..finished
###########
reiserfsck finished at Wed Aug  8 13:18:34 2007
###########


No i am on a &quot;dd if=/dev/zero of=/dev/sda bs=1M&quot; run to the original drive and see if it can be rescued ;)</description>
		<content:encoded><![CDATA[<p>Please forgive my total lack of patience, the process ended just fine:</p>
<p>327035 directory entries were hashed with &#8220;r5&#8243; hash.<br />
        &#8220;r5&#8243; hash is selected<br />
Flushing..finished<br />
        Read blocks (but not data blocks) 103806568<br />
                Leaves among those 116376<br />
                Objectids found 324508</p>
<p>Pass 1 (will try to insert 116376 leaves):<br />
####### Pass 1 #######<br />
Looking for allocable blocks .. finished<br />
0%&#8230;.20%&#8230;.40%&#8230;.60%&#8230;.80%&#8230;.100%<br />
Flushing..finished<br />
        116376 leaves read<br />
                116176 inserted<br />
                        &#8211; pointers in indirect items pointing to metadata 7 (zeroed)<br />
                200 not inserted<br />
        non-unique pointers in indirect items (zeroed) 2984<br />
####### Pass 2 #######</p>
<p>Pass 2:<br />
0%&#8230;.20%&#8230;.40%&#8230;.60%vpf-10260: The file we are inserting the new item (134320 14974 0xae532001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped<br />
&#8230;.80%&#8230;.100%<br />
Flushing..finished<br />
        Leaves inserted item by item 200<br />
Pass 3 (semantic):<br />
####### Pass 3 #########<br />
vpf-10680: The file [249620 343697] has the wrong block count in the StatData (1414608) &#8211; corrected to (1403248)<br />
vpf-10680: The file [335046 335060] has the wrong block count in the StatData (23448) &#8211; corrected to (22904)<br />
vpf-10680: The file [241839 243017] has the wrong block count in the StatData (64) &#8211; corrected to (56)<br />
Flushing..finished<br />
        Files found: 285283<br />
        Directories found: 33617<br />
        Symlinks found: 4426<br />
        Others: 1167<br />
Pass 3a (looking for lost dir/files):<br />
####### Pass 3a (lost+found pass) #########<br />
Looking for lost directories:<br />
Flushing..finished<br />
Pass 4 &#8211; finished<br />
        Deleted unreachable items 2<br />
Flushing..finished<br />
Syncing..finished<br />
###########<br />
reiserfsck finished at Wed Aug  8 13:18:34 2007<br />
###########</p>
<p>No i am on a &#8220;dd if=/dev/zero of=/dev/sda bs=1M&#8221; run to the original drive and see if it can be rescued ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diego</title>
		<link>http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf/comment-page-1#comment-69994</link>
		<dc:creator>Diego</dc:creator>
		<pubDate>Wed, 08 Aug 2007 02:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://javier.rodriguez.org.mx/?p=69#comment-69994</guid>
		<description>Dude, the dd_rescue processs has finished succesfully:

dd_rescue: (info): /dev/sdb2 (480320047.5k): EOF
Summary for /dev/sdb2 -&gt; /dev/sda1:
dd_rescue: (info): ipos: 480320047.5k, opos: 480320047.5k, xferd: 480320047.5k
                   errs:    168, errxfer:        84.0k, succxfer: 480319963.5k
             +curr.rate:      832kB/s, avg.rate:     9812kB/s, avg.load: -2.9%

But now i am worried about the fsck, because it has hanged at 40%, just like with the original Hard Drive:

Will rebuild the filesystem (/dev/sda1) tree
Will put log info to &#039;stdout&#039;

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Replaying journal..
Reiserfs journal &#039;/dev/sda1&#039; in blocks [18..8211]: 0 transactions replayed
###########
reiserfsck --rebuild-tree started at Wed Aug  8 08:02:26 2007
###########

Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 103818443 blocks marked used
Skipping 11875 blocks (super block, journal, bitmaps) 103806568 blocks will be read
0%....20%....40%


It hasnt finished yet, but i fear a bad outcome; if the problem is no physical is there anything i can do to fix this?

Regards my friend...</description>
		<content:encoded><![CDATA[<p>Dude, the dd_rescue processs has finished succesfully:</p>
<p>dd_rescue: (info): /dev/sdb2 (480320047.5k): EOF<br />
Summary for /dev/sdb2 -&gt; /dev/sda1:<br />
dd_rescue: (info): ipos: 480320047.5k, opos: 480320047.5k, xferd: 480320047.5k<br />
                   errs:    168, errxfer:        84.0k, succxfer: 480319963.5k<br />
             +curr.rate:      832kB/s, avg.rate:     9812kB/s, avg.load: -2.9%</p>
<p>But now i am worried about the fsck, because it has hanged at 40%, just like with the original Hard Drive:</p>
<p>Will rebuild the filesystem (/dev/sda1) tree<br />
Will put log info to &#8216;stdout&#8217;</p>
<p>Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes<br />
Replaying journal..<br />
Reiserfs journal &#8216;/dev/sda1&#8242; in blocks [18..8211]: 0 transactions replayed<br />
###########<br />
reiserfsck &#8211;rebuild-tree started at Wed Aug  8 08:02:26 2007<br />
###########</p>
<p>Pass 0:<br />
####### Pass 0 #######<br />
Loading on-disk bitmap .. ok, 103818443 blocks marked used<br />
Skipping 11875 blocks (super block, journal, bitmaps) 103806568 blocks will be read<br />
0%&#8230;.20%&#8230;.40%</p>
<p>It hasnt finished yet, but i fear a bad outcome; if the problem is no physical is there anything i can do to fix this?</p>
<p>Regards my friend&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diego</title>
		<link>http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf/comment-page-1#comment-69851</link>
		<dc:creator>Diego</dc:creator>
		<pubDate>Mon, 06 Aug 2007 22:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://javier.rodriguez.org.mx/?p=69#comment-69851</guid>
		<description>As always, my friend codehead to the rescue; i know this is the second time this happens to me and the second i bother you for help... You know it will also be to your benefit when we sync our multimedia collections ;)

A hug from the Land down Under!</description>
		<content:encoded><![CDATA[<p>As always, my friend codehead to the rescue; i know this is the second time this happens to me and the second i bother you for help&#8230; You know it will also be to your benefit when we sync our multimedia collections ;)</p>
<p>A hug from the Land down Under!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin</title>
		<link>http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf/comment-page-1#comment-1659</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Wed, 19 Jul 2006 10:50:47 +0000</pubDate>
		<guid isPermaLink="false">http://javier.rodriguez.org.mx/?p=69#comment-1659</guid>
		<description>It is good to see prople sharing their experinces like this which would give some knowledge about what to do in case of a possible data loss in thier system. I have seen most of the people loose thier data just because of the fact they are unaware that there is something called Data recovery with which they can recover most of their data without allmost all the files to be intact. I got my data recovered from a service provider Disk doctors Labs and after sent most of the people i sent to disk doctors gave me good and positive response</description>
		<content:encoded><![CDATA[<p>It is good to see prople sharing their experinces like this which would give some knowledge about what to do in case of a possible data loss in thier system. I have seen most of the people loose thier data just because of the fact they are unaware that there is something called Data recovery with which they can recover most of their data without allmost all the files to be intact. I got my data recovered from a service provider Disk doctors Labs and after sent most of the people i sent to disk doctors gave me good and positive response</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: javier</title>
		<link>http://javier.rodriguez.org.mx/index.php/2006/07/16/dd_rescue_and_reiserf/comment-page-1#comment-1649</link>
		<dc:creator>javier</dc:creator>
		<pubDate>Tue, 18 Jul 2006 07:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://javier.rodriguez.org.mx/?p=69#comment-1649</guid>
		<description>¡Saludos tocayo!

Hace un tiempo encontré tu blog, aunque lamentablemente no he tenido tiempo de seguirlo. Me ha parecido interesante por muchas cosas: tivo, mutuo interés por tecnología, somos de la misma institución (tec), tus imágenes de la misma me sirvieron mucho...

En fin, espero darme una vuelta más seguido.

javier.</description>
		<content:encoded><![CDATA[<p>¡Saludos tocayo!</p>
<p>Hace un tiempo encontré tu blog, aunque lamentablemente no he tenido tiempo de seguirlo. Me ha parecido interesante por muchas cosas: tivo, mutuo interés por tecnología, somos de la misma institución (tec), tus imágenes de la misma me sirvieron mucho&#8230;</p>
<p>En fin, espero darme una vuelta más seguido.</p>
<p>javier.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

