[GH-ISSUE #96] Synology keeps drive compatibility information for drives after forcefully disabling compatibility flag #24

New issue

Open

opened 2026-03-07 19:10:06 +03:00 by kerem · 0 comments

kerem commented

2026-03-07 19:10:06 +03:00

Owner

Originally created by @Ubsefor on GitHub (May 23, 2025).
Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/96

Just as the name states, there's a certain problem after enabling deduplication and/or disabling support_drive_compatibility in synoinfo.conf.
This can be sometimes needed, when using nvme or sas drives as volumes. The culprits are certain files in /run/synostorage, which store information about nvme/sas drives compatibility even after support_drive_compatibility gets disabled, so this information doesn't seem to update on itself and nvme/sas drive becomes "unsupported for deduplication".

I suggest looking into libhwcontrol.so to patch this behavior or delete sys_not_support lock files for NVME/SAS drives in your scripts, when certain flag is present.

P.S. I understand, that this issue also linked with Synology_HDD_db, but the problem occurs with enabling deduplication on non-synology NVME drives, so here we are.

Originally created by @Ubsefor on GitHub (May 23, 2025). Original GitHub issue: https://github.com/007revad/Synology_enable_Deduplication/issues/96 Just as the name states, there's a certain problem after enabling deduplication and/or disabling ```support_drive_compatibility``` in ```synoinfo.conf```. This can be sometimes needed, when using nvme or sas drives as volumes. The culprits are certain files in ```/run/synostorage```, which store information about nvme/sas drives compatibility even after ```support_drive_compatibility``` gets disabled, so this information doesn't seem to update on itself and nvme/sas drive becomes "unsupported for deduplication". I suggest looking into ```libhwcontrol.so``` to patch this behavior or [delete ```sys_not_support```](https://kb.synology.com/en-us/DSM/tutorial/Allocation_status_not_supported_by_DSM_version_DSMUC) lock files for NVME/SAS drives in your scripts, when certain flag is present. P.S. I understand, that this issue also linked with [Synology_HDD_db](https://github.com/007revad/Synology_HDD_db), but the problem occurs with enabling deduplication on non-synology NVME drives, so here we are.