Curious, aren't we?

Definitely not. As I've mentioned, the sata controller is passed through, meaning that the drives are communicating with DSM exactly as they would in a real bare metal hardware DSM...

Would you mind sending me your patched `StorageManager 1.0.0-00502` storage_component.js file to compare it to mine?

@007revad There's a different js file that's being sent to the DSM web clients than the one your script is modifying, or something like that. Because, even if the `&&e.dedup_info.show_config_btn`...

``` root@DSM1:/usr/local/packages/@appstore/StorageManager/ui# sha256sum storage_panel.js* bdab05da7e550fd4696e9e9f7a54694d40ee71f1711799ec64078a7a601d0a94 storage_panel.js bdab05da7e550fd4696e9e9f7a54694d40ee71f1711799ec64078a7a601d0a94 storage_panel.js.1.0.0-00502 9dec4942926cc8ec184c9575aa5d35cbb1ab10f7f6888d881b4c0f0ea5405e03 storage_panel.js.gz cbf8f3709fcc43f1e5cc360e726bbb6e739e8176d3fd52b41f237a9400694280 storage_panel.js.gz.bak ``` I removed the check, and made both files the same. There has to be some other place...

Oh, and maybe this will help, this is the file that Synology is sending despite having the files above modified: [storage_panel_sentBySyno.zip](https://github.com/user-attachments/files/18171125/storage_panel_sentBySyno.zip)

> Do you have syno_enable_dedupe.sh scheduled? I don't. > My real Synology NAS don't have the storage_panel.js.gz (or storage_panel.js.gz.bak) files. Oh, I didn't know that! I've tried to modify the...

> If you reboot does the storage_panel.js.gz still contain your edits? So far, yes they do. However, I suspect that updates to the loader can easily break it / revert...

I mean, this is technically solved for me, as well as anyone else that will just replace the file in the GZIP archive. Whether or not this will be natively...

idk it's looking kinda dead to me :(