Packed file is corrupt

Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.

I tried to open my repository today and it came up with no commit history. Everything I tried git status, git log, git checkout I researched this problem online and found the article by Linus Torvalds, but got lost at the point where he found the broken link ID: none of my file IDs, tree or blob, match the culprit ID thrown by the error message.

I then returned to the article on recovering "git objects damaged by hard disk failure" and after moving the culprit object out of the way worked my way through until. So my question s is are , was I supposed to have made a backup ooh, newbie alert , or was that what happened when I unpacked the.

And is the "culprit" I'm copying back actually a clean file, i. I think it only fair to tell you that I was initially confused by a simple dash in Torvalds' file between the "git" and "fsck. Okay, so. We can see from the second error message that the corrupt object which you moved was a commit. HEAD was pointing to it!

Unfortunately, this means that it's hard to manually repair it. By "hard" I mean likely impossible unless you can remember exactly what the commit message was and what time you made the commit. Fortunately, this does mean that it's easy to resurrect a new commit with the same file contents - you'll just have to write a new message for it.

Before you start, have a look at the contents of. First, we need to figure out what the parent of this commit should've been. It should look something like this:. Now, there's some question here about what should've happened to your branches. If HEAD was pointing to a branch say master which in turn pointed to the corrupted commit, we definitely want to fix that up:. If there are other branches which contained the corrupted commit, you'll have to do some restoration on them too - let me know if you need help with that.

FWIW, here's an answer that is more practical than a lot of the hopelessly optimistic ones on other questions about corrupted git repos - most of which make the baseless assumption that the poor OP can 'just re-clone from the remote origin! Wait a second. What if I am the origin? The story begins when an attempt to run a simple git gc --aggressive revealed that, unbeknownst to me, at some point my - completely local - git repo had somehow gotten completely hosed: It was unable to log anything beyond a few months ago, thereby losing the majority of its history, and screamed gutturally whenever asked to git fsck --full grep -v dangling.

Several objects were identified as lost by git fsck. After panicking and finding lots of questions with over-voted poor answers just saying 'just re-clone from the remote origin! That helped reduce the amount of horror reported by git fsck --full grep -v dangling.

But things beyond the middle of August were still unreachable. In particular, this all seemed to centre around one commit that couldn't be retrieved. How could I recover it? Searching Stack Overflow wasn't much help! Here's where I was lucky enough to have a backup from the end of November. You take backups, right? In my case, it was a manual zip of the repo my daily backup routine is some horrible incremental tar thing that I've never actually tested It hadn't suffered whatever indignity had afflicted my live repo.

But the missing object didn't seem to be simply stored in this backup's. That's probably because it was a commit, not a file. I don't know! I just needed a fix, fast. Isn't that why we're all here? Covered by US Patent. Come for the solution, stay for everything else. Welcome to our community! I installed win98 on a new drive using my win98 startup disk. Do I have a bad disk? Also when Win98 installs I get windows that say it can't find a file and to put in the win98 cdrom, which of course is already in there.

Would this be part of my original problem? My overall concern is that somewhere in finding and setting up these "can't find files' I might have miised something. Join our community to see this answer! Unlock 1 Answer and 7 Comments. Log in. Sign up. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations.

Click here to join today! JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. Packed File Is Corrupt. Total voters 0 Poll closed Jan 27, Status This thread has been Locked and is not open to further replies.

The original thread starter may use the Report button to request it be reopened but anyone else with a similar issue should start a New Thread. Watch our Welcome Guide to learn how to use this site. Joined Jan 17, Messages 1. Joined Aug 17, Messages 7, Have you wiped the entire Drive? If so, possibly you have an infected Master Boot Record oryou are infecting the computer by using an infected Floppy. Run it.