Unrar Checksum Error on Password Protected RAR Files

Encountering a "checksum error" (or CRC failure) while extracting password-protected RAR archives using the unrar command-line utility is a common issue. This article explains why this specific error occurs—ranging from incorrect password entries and corrupted data blocks to version incompatibilities and missing multi-part volumes—and outlines direct methods to diagnose and resolve the problem.

1. Incorrect Password Entry

The most frequent cause of a checksum error on an encrypted RAR archive is entering the wrong password. Unlike modern formats that can verify a password before attempting extraction, certain RAR archives (particularly older RAR4 formats or archives created without encrypted file headers) do not store a separate hash to validate passwords.

When you enter an incorrect password, unrar still uses that key to decrypt the payload. Because the decryption key is wrong, the output produces scrambled, invalid data. When unrar checks the resulting data against the stored CRC32 or BLAKE2 checksum, the hashes do not match, triggering a checksum error.

2. Archive Data Corruption

Physical corruption of the file will also cause a checksum failure, even if the password is correct:

  • Incomplete Downloads: Network drops or browser interruptions can truncate the archive or drop packets, corrupting the encrypted byte stream.
  • Storage Degradation: Bad disk sectors, failing flash drives, or file transfer interruptions can flip bits in the archive.
  • Corrupted Recovery Records: If the archive contains a damaged built-in recovery record, extraction attempts may fail during integrity validation.

3. Outdated unrar Utility Versions

There are two distinct RAR extraction utilities often present in Linux/Unix environments: the open-source unrar-free package and the official, proprietary unrar utility provided by RARLAB.

  • unrar-free Limitations: The open-source unrar-free utility has limited or buggy support for modern RAR5 formats and modern AES encryption schemes, frequently throwing false checksum errors.
  • RAR4 vs. RAR5: Older builds of the proprietary unrar cannot handle the updated encryption and compression algorithms introduced with RAR5.

4. Broken or Missing Multi-Part Volumes

If the file is part of a split archive (e.g., archive.part1.rar, archive.part2.rar), the checksum error can occur if:

  • One or more volume files are missing from the working directory.
  • One individual part was corrupted during transit.
  • The parts were renamed inconsistently, breaking the sequence that unrar expects during decompression.

How to Fix the Error

  • Verify the Password: Check for accidental whitespace, caps lock status, or special character escaping issues in the terminal. Wrap the password in single quotes when passing it to the command:
    unrar x -p'YourPasswordHere' archive.rar
  • Switch to the Official RARLAB Package: Remove unrar-free and install the non-free, proprietary unrar package directly from your distribution's repositories or compile the latest source from RARLAB.
  • Test the Archive Integrity: Run the test command to isolate where the failure occurs without writing files to disk:
    unrar t -p archive.rar
  • Attempt Built-In Repair: If the archive was created with a recovery record, run the repair command:
    unrar r archive.rar
  • Keep Broken Files: If data extraction is critical and minor corruption in the output is acceptable (such as in certain video or audio streams), force the extraction of the damaged payload:
    unrar x -kb -p archive.rar