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.