title: How can I fix a corrupted Git repository?
body: <p>I tried cloning my repository which I keep in my <a href="https://en.wikipedia.org/wiki/Ubuntu_One#Features" rel="noreferrer">Ubuntu One</a> folder to a new machine, and I got this:</p>
  <pre><code>cd ~/source/personal
  git clone ~/Ubuntu\ One\ Side\ Work/projects.git/
  
  Cloning into 'projects'...
  done.
  fatal: unable to read tree 29a422c19251aeaeb907175e9b3219a9bed6c616
  </code></pre>
  <p>So I tried looking at the many other questions like this that have been asked here and most of them say to run <code>git fsck --full</code> and then I get this when I try that.</p>
  <pre><code>cd ~/Ubuntu\ One\ Side\ Work/projects.git
  git fsck --full
  
  Checking object directories: 100% (256/256), done.
  Checking objects: 100% (447/447), done.
  broken link from  commit 235ae1f48701d577d71ebd430344a159e5ba4881
                to  commit 984c11abfc9c2839b386f29c574d9e03383fa589
  broken link from    tree 632a9cf0ef9fccea08438b574e2f1c954f4ff08b
                to    blob 25a742dff0a403b2b3884f2ffddf63eb45721fac
  broken link from    tree 632a9cf0ef9fccea08438b574e2f1c954f4ff08b
                to    blob dd4e97e22e159a585b20e21028f964827d5afa4e
  broken link from    tree 632a9cf0ef9fccea08438b574e2f1c954f4ff08b
                to    tree 29a422c19251aeaeb907175e9b3219a9bed6c616
  broken link from    tree 632a9cf0ef9fccea08438b574e2f1c954f4ff08b
                to    tree 8084e8e04d510cc28321f30a9646477cc50c235c
  broken link from    tree 774b5b4157b4caae1c6cad96c8eaf5d4eba2c628
                to    blob a0daa0c1567b55d8de2b4d7a3bc010f58c047eab
  broken link from    tree 774b5b4157b4caae1c6cad96c8eaf5d4eba2c628
                to    blob e9052d35bfb6d30065b206fc43f4200a04d5281b
  broken link from    tree 774b5b4157b4caae1c6cad96c8eaf5d4eba2c628
                to    blob 1a3a5e4dd2502ac121c22f743c4250e254a94eeb
  broken link from    tree 4aa336dc1a5838e8918e03b85580069d83f4ad09
                to    tree 8cc55ec952dc192a233e062201d1e7e873ac3db0
  broken link from    tree e5674a91a53e15575a1f3bf5786bc5cc719fb483
                to    blob 4a994e1e7bb7ce28dcec98bad48b9a891d7dec51
  broken link from    tree e5674a91a53e15575a1f3bf5786bc5cc719fb483
                to    blob ac033bf9dc846101320c96a5ce8aceb8c96ec098
  broken link from    tree 252ab84542264e1589576b6ee51e7a31e580a0e2
                to    tree 2069041cd5950e529e2991d37b7290ec021d90d4
  broken link from    tree 2d4964aa4d4f5d8c7228518ce72ef6a63f820c6d
                to    blob d83690e1b9a6bdd8a08754b38231799acefcb2ab
  broken link from    tree c7192e82fc581bd6448bda1a25e8729bdac5f4ff
                to    blob 30d54d47ae82add1917ca173d42e58b396df580b
  broken link from    tree 7c66306901fc71389623286936cef172d4ffe408
                to    blob bc7e05d705401273b1df4e939de0f540597c0931
  broken link from    tree 0940f5fd227d4c84d6e6749d872db50a4522ae3a
                to    tree 923767594ac22023e824948d65622fe5b407d1a1
  broken link from    tree 8eadcd2a971e8357d24f0d80f993d2963452209f
                to    blob 2598bde3dc8cb80ee49510b8159344004b88645f
  broken link from    tree ffa302dd0d969172ef23caeefe856ab2f57a4e4d
                to    blob d6925fa431be1ac585bf9a481e98f75107a6e6fb
  broken link from    tree 7045b8870a49ce30a2027537a96d73d162bda773
                to    blob 25688652dea26f61f576ca1b52b9d1a18fbfd01d
  broken link from    tree 37e4705d34bd440ce681ae32ae9a180a13256d72
                to    tree 246f564d4cee53339b8a4244f3173b61caa518eb
  missing blob d6925fa431be1ac585bf9a481e98f75107a6e6fb
  missing blob ac033bf9dc846101320c96a5ce8aceb8c96ec098
  missing tree 29a422c19251aeaeb907175e9b3219a9bed6c616
  missing tree 8084e8e04d510cc28321f30a9646477cc50c235c
  missing blob 30d54d47ae82add1917ca173d42e58b396df580b
  missing tree 8cc55ec952dc192a233e062201d1e7e873ac3db0
  missing blob e9052d35bfb6d30065b206fc43f4200a04d5281b
  dangling tree 4b26e95db542c72ac4a22ec25abe38fb2de79752
  missing blob d83690e1b9a6bdd8a08754b38231799acefcb2ab
  missing blob 25a742dff0a403b2b3884f2ffddf63eb45721fac
  missing tree 923767594ac22023e824948d65622fe5b407d1a1
  missing blob 25688652dea26f61f576ca1b52b9d1a18fbfd01d
  missing blob 2598bde3dc8cb80ee49510b8159344004b88645f
  dangling tree 3a683869f1bb0c1634de75700c316b3b36570dbd
  dangling blob 4098d30843380d798a811f1aa9a02994f0dbbb27
  missing tree 2069041cd5950e529e2991d37b7290ec021d90d4
  missing blob 4a994e1e7bb7ce28dcec98bad48b9a891d7dec51
  missing blob 1a3a5e4dd2502ac121c22f743c4250e254a94eeb
  missing blob a0daa0c1567b55d8de2b4d7a3bc010f58c047eab
  dangling tree 6c7b5162aa7a303fa3fe8dc393c5da564e309521
  missing commit 984c11abfc9c2839b386f29c574d9e03383fa589
  missing blob bc7e05d705401273b1df4e939de0f540597c0931
  missing blob dd4e97e22e159a585b20e21028f964827d5afa4e
  missing tree 246f564d4cee53339b8a4244f3173b61caa518eb
  dangling commit a01f5c1e5315dc837203d6dee00d3493be9c5db9
  </code></pre>
  <p>That looks really bad. When I do a <code>git log | head</code> I get this</p>
  <pre><code>git log | head
  
  error: Could not read 984c11abfc9c2839b386f29c574d9e03383fa589
  fatal: Failed to traverse parents of commit 235ae1f48701d577d71ebd430344a159e5ba4881
  commit 2fb0d2d0643b445440f01b164f11ee9ee71fca48
  Author: christopher &lt;christopher@christopher.christopher&gt;
  Date:   Wed Aug 7 15:51:42 2013 -0400
  
      finishing chapter 7
  </code></pre>
  <p>Other questions here have said to look at <code>./git/refs/heads/master</code>. It's a bare repo and <code>refs/heads/</code> exists but <code>refs/heads/master</code> does not. HEAD in the bare repository says <code>ref: refs/heads/master</code> though.</p>
  <p><code>packed-refs</code> does say this though</p>
  <pre><code># pack-refs with: peeled
  2fb0d2d0643b445440f01b164f11ee9ee71fca48 refs/heads/master
  </code></pre>
  <p>Still other questions have suggested running <code>git reflog</code> and no output shows up when I run that.</p>
  <p>So I really have no idea what to do here. What strategy should be taken? Is it possible to reset head to this last commit on Aug 7?</p>
  <p>Doing a <code>git log</code> and going to the bottom of the screen output shows this:</p>
  <pre><code>commit 996e03b949aea176238e3c7a8452700bbb987ac9
  Author: christopher &lt;christopher@christopher&gt;
  Date:   Wed Jul 3 23:00:44 2013 -0400
  
      many many changes
  error: Could not read 984c11abfc9c2839b386f29c574d9e03383fa589
  fatal: Failed to traverse parents of commit 235ae1f48701d577d71ebd430344a159e5ba4881
  </code></pre>
  <p>That seems to be preventing the Git prune from working.</p>