virtual-dsm VS Synology_enable_Deduplication

According to the GitHub, you want to pass in the actual device, not the mounted path. You probably should/need to unmount it in unassigned devices. https://github.com/vdsm/virtual-dsm

If you’re feeling adventurous you can run the synology dsm os in a vm (qemu/kvm in my case). You use tinycore[0] as a boot loader to bootstrap the official Synology image[1]

It can be a bit of a pain to setup but once it’s up and running you can run all synology apps, including photos and even their nvr software, backup your home pcs to it, etc. If you pass through pci sata controllers you can bypass any disk virtualization layer and let synology manage raw disks exactly like a metal install in one of their nas machines would do. You could even swap the disks into an official nas later on if you wanted. The synology apps are highly polished and worth the setup imo.

There’s also a docker image that makes it all trivial, but it’s too many layers of abstraction for my tastes[2]

0. https://github.com/pocopico/tinycore-redpill

1. https://www.wundertech.net/how-to-install-xpenology-on-proxm...

2. https://github.com/kroese/virtual-dsm

If you want to participate in development or report some issues, the source code is available at https://github.com/kroese/virtual-dsm to see.

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.