Synology_HDD_db VS Synology_enable_Deduplication

I used my https://github.com/007revad/Synology_HDD_db script to add them to DSM's compatible drive database and allow creating NVMe storage pool.

The bash script is here: https://github.com/007revad/Synology_HDD_db/blob/develop/syno_hdd_db.sh

You should probably schedule those commands to run at start-up in case a DSM update undoes your changes. See how_to_schedule (replace that command with the two command lines above).

Update: I managed to fix it by running this script. One tip is to save your script in a place that doesn't have spaces in the location path. Part of me wonders if I should have just stayed on DSM 6 since if it isn't broke don't fix it.

Or better yet, just schedule my Synology_HDD_db script to run at boot-up. https://github.com/007revad/Synology_HDD_db

I've just done the update and had a similar experience. Drives blacklisted but storage pool still up and available. Ran the script from https://github.com/007revad/Synology_HDD_db

I could make my Synology think the HDDs are SSDs but then I really wouldn't trust it deduplicating my data. I've had deduplication working on my DS1821+ on an NVMe volume.

If they have SATA SSD drives and want to run data deduplication they'd need to run the script without the -f. I have another script that enables data deduplication.

I did write a script to enable btrfs data deduplication on other models, and without Synology drives. https://github.com/007revad/Synology_enable_Deduplication

There is also Synology_enable_Deduplication that enables data deduplication for non-Synology SSDs and unsupported NAS models.