mirror of
https://github.com/007revad/Synology_enable_Deduplication.git
synced 2026-04-25 12:46:03 +03:00
[GH-ISSUE #107] Deduplication option not appearing for HDDs on DS925+ with 4GiB of RAM & tiny deduplication #28
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_enable_Deduplication#28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MacGyverNL on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/107
The script and
syno_hdd_db.shseems to run successfully on a DS925+ with DSM 7.3.2-86009 with 4GiB of RAM and two Western Digital Red Plus 8TB disks, with--tiny --hdd, but after rebooting and trying in a clean browser session I still cannot get the "Configure data deduplication" option to appear.Full output of
sudo -s ./syno_enable_dedupe.sh -c:The setup seems to satisfy all requirements listed in https://github.com/007revad/Synology_enable_Deduplication/issues/79#issuecomment-2255309896 -- btrfs, healthy, usage detail enabled:
And only having tiny dedup enabled shouldn't be an issue, from what I can gather from https://github.com/007revad/Synology_enable_Deduplication/issues/79#issuecomment-2265606520
But the context menu doesn't have the option:
Seems related to https://github.com/007revad/Synology_enable_Deduplication/issues/79#issuecomment-3288546177
Forked off from #97
@MacGyverNL commented on GitHub (Dec 10, 2025):
Since it was requested in a similar issue (https://github.com/007revad/Synology_enable_Deduplication/issues/88#issuecomment-2552440158), attached a zip of the ui folder including the
storage_panel.jsand its backup for storage manager 1.0.1-1100.I can confirm that the replaced
storage_manager.jsis the file being sent to the browser.storagemanager-ui.zip
@007revad commented on GitHub (Dec 11, 2025):
If you had storage manager already open you need to close it and open it again.
Which version of syno_hdd_db did you use?
@MacGyverNL commented on GitHub (Dec 11, 2025):
Before reporting I gave the NAS two reboots (with the scripts also setup to re-run at shutdown) and tested the interface in a completely clean browser session to eliminate any possibility of cache being the culprit. Did that again just now, same behaviour.
Initially used Synology_HDD_db-3.6.112. The drives no longer had any warning on them, but I see there's a .113 now, so I've updated, re-ran the HDD script, rebooted again (which re-ran both scripts again, because I forgot to disable the shutdown task), and re-tested in a clean browser session. No change.
Output from that run on reboot:
Drives (still) showing without any warnings after reboot:
But no option to configure data deduplication on the volume.
@007revad commented on GitHub (Dec 11, 2025):
I just figured out what tiny dedupe is. It's for defragging the file system. I just ran this script on my DS925+ which only has 4GB of memory.
Before running syno_enable_dedupe only my SATA SSD volume had the File System Defragmentation option.
After running syno_enable_dedupe without any options (no --tiny or --hdd), and without rebooting Storage Manager now shows the File System Defragmentation option for NVMe, HDD and SATA SSD volumes.
I'll update the script and readme to reflect that.
@MacGyverNL commented on GitHub (Dec 11, 2025):
Hmm. Then there's still a weird discrepancy with https://github.com/007revad/Synology_enable_Deduplication/issues/79#issuecomment-2265606520 with @WAdama reporting that on their 10GiB DS420+ it does allow running a dedup analysis; that's below the 16GiB threshold for normal dedup.
@MacGyverNL commented on GitHub (Dec 11, 2025):
I cannot reproduce this. I've reverted all changes the
enable_dedupscript made, rebooted the DS925+, confirmed there's no mention of any kind of dedup in/etc/synoinfo.confand/etc.default/synoinfo.conf. Storage manager shows defrag just fine. Note I have not reverted the changes that theHDD_dbscript made. Might defragmentation simply only be available for Synology-branded drives normally?What I have been able to figure out now: if I manually enable the
support_btrfs_dedupekey usingsynosetkeyvalue, the option does appear, but indeed refuses to run the dedup analyzer with the usual "system needs 16GiB of RAM" notification. Having bothsupport_tiny_btrfs_dedupeandsupport_btrfs_dedupeset toyesdoesn't change that.@007revad commented on GitHub (Dec 12, 2025):
Previously defragging was only available for enterprise models and SATA and SAS SSDs, then later only for Synology SATA or SAS SSDs. By editing a file to make storage manager skip the "is it a Synology drive" check I was able to get the defrag option to appear for 3rd party drives. By also making it skip the "is it a SSD" check I was able to get it appear for HDDs and NVMe drives. By editing synoinfo.conf I was able to get it to appear for all Synology NAS models.
The support_tiny_btrfs_dedupe option would have been added when Synology changed from ext4 to btrfs for the system partition.
In DSM 7.3.1 I just checked all 122 Synology model's synoinfo.conf and:
@MacGyverNL commented on GitHub (Dec 12, 2025):
So I guess the conclusion then is that, at least for now, no version of Synology's deduplication is available for systems with less than 16GiB after a brief stint between DSM 7.2.1 and 7.3.
One final thing I looked into: it does appear to be the case that the
synobtrfsdedupeexecutable still takesrun-lightas an argument, but I cannot for the life of me get that to work and it doesn't give any useful logs, so that seems like a dead end for now as well.Ah well. Guess I'll have to see if jdupes does the job sufficiently.
@007revad commented on GitHub (Dec 12, 2025):
I'm not sure why it worked for @WAdama with only 10GiB of memory. Maybe storage manager actually checks if there's 8GiB or more than 8GiB but shows the "16GiB is needed" message if there isn't 8GiB or more.
I only have 2GiB and 16GiB modules, plus the 4GiB that it is my DS925+. If I had another 4GiB I'd install it in the DS925+ to see what happens with 8GiB total. Or if I had an 8GiB I could try 10GiB and 12GiB.
@MacGyverNL commented on GitHub (Dec 12, 2025):
The comment I referenced was written over a year ago, so I just assume they were using one of those versions between 7.2.1 and 7.3 where
support_tiny_btrfs_dedupewas being used in DSM.@f-rakete commented on GitHub (Feb 2, 2026):
As someone with a DS1821+ , 8GB RAM and on 7.3.2-86009 Update 1, WD HDDs only
I successfully ran dedup with this script before, now on 7.3.2-86009 Update 1 i don't have the option anymore.
@007revad
Do I understand correctly that deduplication is now not possible anymore since I updated? And if i upgrade to 16GB it will be possible again?