NAS Codex › Synology › Synology "checksum mismatch" errors: what they mean and what to do
Synology "checksum mismatch" errors: what they mean and what to do
A checksum mismatch notification comes from the Btrfs file system on a Synology NAS. Btrfs stores checksums so it can detect silent data corruption, and it can repair some corrupted data on its own. Synology says a checksum mismatch error means the file system found damaged data that it could not repair.
Written against: DSM 7 (Synology KB articles last updated Aug 30, 2023, Aug 21, 2024 and Nov 11, 2026; DSM 7 help: Data Scrubbing, Log Center Logs). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Open Log Center > Logs to see which files are affected. Synology says data that Btrfs could not restore is inaccessible, and it can only be recovered from a backup kept at an offsite location from before the corruption. Then run a memory test, because faulty or non-Synology memory is one of the causes Synology names.
What the error means
Synology says the Btrfs file system uses checksums to ensure data integrity. It can automatically detect corrupted data and use its self-healing feature to recover it. When you get a checksum mismatch error, Synology's diagnosis is that the Btrfs file system cannot repair the damaged data.
Find the affected files
Synology says to check the logs in Log Center > Logs to find out which files are affected. On that page you can view, search for and export logs:
- Use Keyword to find log messages that contain a word. Wildcards (
*for zero or more characters,?for exactly one) and the operators AND, OR and NOT are supported. - You can also filter by Date Range, Level, Host name, Program and Category, then click Search.
- To keep a record, click the arrow next to Export and choose HTML or CSV. Synology notes the CSV file is UTF-8 encoded.
Can the files be recovered?
Synology says that if Btrfs fails to restore the corrupted data, the data will be inaccessible. You can only recover it if you backed it up to an offsite location before the corruption happened.
Synology also warns that an onsite backup may not help. If the data was already corrupted, a copy made with Snapshot Replication or Synology Drive may be corrupted too, because the backed-up or synchronized data can carry the same damage.
Why it happens
Synology says checksum mismatch errors have many causes, including:
- defective drives;
- faulty memory modules;
- non-Synology memory modules.
If non-Synology memory is installed, Synology says to remove it to prevent further data loss, and notes that memory not compatible with your model can cause other unexpected system errors.
Run a memory test
Synology recommends running the test three times to make sure the memory is normal.
- Download and install Synology Assistant from the Download Center.
- Launch it, click the upper-right icon, tick Memory Test and click OK.
- Select the NAS. Make sure its status is Ready, then click Memory Test and follow the wizard.
The NAS reboots and is unavailable during the test, and its status shows Performing memory test (x%). Don't close Synology Assistant. Synology says to reserve 1 to 1.5 hours per test for models with 16 GB of memory or less, and 1.5 to 3 hours for 32 GB or more. Keep at least one built-in LAN port connected.
If the test fails, the message "One or more errors have been found by the memory diagnostic test" appears, which means the memory may be defective. The status still shows Ready even after a failure, so read the result. Synology strongly recommends returning the NAS for repair if it is still under warranty.
Is self-healing turned on for your folders?
Synology says File self-healing, available since DSM 6.1, only protects shared folders that meet all of these conditions:
- The folder is on a Btrfs volume using RAID 1, RAID 5, RAID 6, RAID TP, RAID 10, RAID F1, or SHR/SHR-2 with more than one drive.
- Enable data checksum for advanced data integrity was ticked when the shared folder was created. It can't be changed afterwards. To check it, go to Control Panel > Shared Folder, select the folder and click Edit > Advanced.
Self-healing is not available during a repair or parity consistency check, on a degraded volume, or for data stored on VDSM or VMM. Files on iSCSI LUNs created on a Btrfs volume are not protected by it.
Prevent it from happening again
- Run data scrubbing regularly. Synology says it is supported on Btrfs volumes or storage pools using SHR with three or more drives, RAID 5, RAID 6 or RAID F1. To start it, go to Storage Manager's Storage page, click the storage pool and click Run Now under Data Scrubbing, or use Schedule Data Scrubbing to set a schedule. Folders without data checksum enabled can't be checked and repaired, because they have no checksums.
- Avoid non-Synology memory modules.
- Back up periodically, including a copy kept offsite.
When to stop and get help
If the memory test reports errors, Synology strongly recommends returning the NAS for repair if it is within the warranty period.
Questions
What does checksum mismatch mean on a Synology NAS?
Synology says the Btrfs file system detected corrupted data that it could not repair. Check Log Center > Logs to see which files are affected.
Can I recover files after a Synology checksum mismatch error?
Synology says data that Btrfs fails to restore is inaccessible and can only be recovered from a backup kept offsite from before the corruption. Onsite copies such as Snapshot Replication or Synology Drive may be corrupted too.
What causes Synology checksum mismatch errors?
Synology names defective drives, faulty memory modules and non-Synology memory modules among the causes, and recommends running a memory test with Synology Assistant three times.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.