<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

      <title>Comments on: How can I recover some corrupted data?</title>
      <link>http://ask.metafilter.com/23370/How-can-I-recover-some-corrupted-data/</link>
      <description>Comments on Ask MetaFilter post How can I recover some corrupted data?</description>
	  	  <pubDate></pubDate>
      <lastBuildDate></lastBuildDate>
      <language>en-us</language>
	  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
	  <ttl>60</ttl>

<item>
  	<title>Question: How can I recover some corrupted data?</title>
  	<link>http://ask.metafilter.com/23370/How-can-I-recover-some-corrupted-data</link>	
  	<description>I&apos;m hoping to recover some corrupted files that (I think) got messed up during a transfer to a Firewire drive. Could you be a lamb and step inside? About a month ago, I copied a bunch of files from by Powerbook&apos;s HD to a Firewire drive (1000 files, 3.5GB). As the copying began, my Powerbook&apos;s lid accidentally shut. When I opened it back up, the copy dialogue sat there for a while before resuming (and completing) as normal. Or so I thought. &lt;br&gt;
&lt;br&gt;
I tried accessing these files the other day, and surprise! The files cannot be read. I would think there&apos;s some sort of CRC at play that would render this closed-lid hypothesis invalid, but it seems too coincidental that it happened to precisely the two directories that were involved during the accidental laptop-shut. &lt;br&gt;
&lt;br&gt;
For what it&apos;s worth, these are Canon Camera RAW files. And while there&apos;s a lot of solutions out there for recovering deleted/undeleted image files, they unfortunately don&apos;t fit my situation -- namely because I&apos;ve already overwritten the CF card at least 20 times. I tried &lt;a href=&quot;http://www.datarescue.com/photorescue/&quot;&gt;Photorescue&lt;/a&gt; on my laptop&apos;s free HD space (and the firewire drive), but it didn&apos;t find anything. When I browse these directories with a RAW-browser, some of them have half-thumbnails, while most show nothing at all.&lt;br&gt;
&lt;br&gt;
What makes me hopeful is that the amount of data that&apos;s deemed unreadable (3.5GB) falls very much in line with how much data *should* be there. In my primitive data-management mind, this sounds promising, yet I don&apos;t want to be too optimistic. &lt;br&gt;
&lt;br&gt;
Yesterday, I opened up a corrupted and uncorrupted file side-by-side in a HEX editor, but I admittedly don&apos;t know wtf I&apos;m looking for. Interestingly, the corrupted ones seem to have more friendly/readable meta-data (exif), while the uncorrupted files rarely show anything but unreadable hex-jargon. Any suggestions you could provide would be delightful.</description>
  	<guid isPermaLink="false">post:ask.metafilter.com,2008:site.23370</guid>
  	<pubDate>Tue, 30 Aug 2005 11:01:52 -0800</pubDate>
  	<dc:creator>Hankins</dc:creator>
	
	<category>corrupted</category>
	
	<category>data</category>
	
	<category>firewire</category>
	
	<category>harddrive</category>
	
	<category>recovery</category>
	
	<category>files</category>
	
	<category>computer</category>
	
</item>

    </channel>
</rss>
