How to Fix 'Corrupt loose object' Error in Local Git Repositories

✨ Quick Answer

The critical Git error error: object file .git/objects/... is empty or corrupt loose object occurs after a sudden power outage, disk failure, or forced shutdown of the machine while Git was writing metadata to the local object database of your repository.

Quick Diagnostics

Cause

Corrupted loose Git object caused by sudden power loss or disk failure

Solution

Identify and delete corrupted object in .git/objects/ and git fetch

Cause

Branch ref pointing to a non-existent commit object

Solution

Run git fsck --full to locate exact damaged object

The critical Git error error: object file .git/objects/... is empty or corrupt loose object occurs after a sudden power outage, disk failure, or forced shutdown of the machine while Git was writing metadata to the local object database of your repository.

Step-by-Step Solution

1. 1

   Step 1: Locate and remove the corrupt object from the database

   Git will stop any operation (status, add, commit) if it encounters a corrupt object of 0 bytes size. Run a check on the repository tree to identify the damaged file:

   BASH Copy

   # Run physical integrity check on the repository
   git fsck --full
   

   (Take note of the hash path of the object flagged as empty or corrupt, for example .git/objects/8f/c3a9..., and run the command to physically delete it from the local database):

   BASH Copy

   # Delete the empty 0-byte corrupt object file
   rm .git/objects/8f/c3a9...
   

2. 2

   Step 2: Recover deleted objects from your remote copy

   Once the corrupt object has been removed, tell Git to download and rebuild the missing object indexes from your remote server in the cloud (such as GitHub or GitLab):

   BASH Copy

   # Download missing objects without altering your local working files
   git fetch --all
   

3. 3

   Step 3: Verify and rebuild the local index state

   Check the general consistency of the repository again and reconnect the pointer of your local working branch:

   BASH Copy

   # Validate that no other damaged objects exist
   git fsck --full
   
   # If a failure persists in the HEAD pointer, reset it to the remote commit
   git update-ref refs/heads/main origin/main