Synology_HDD_db VS synology-wireguard

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

Try here: https://github.com/runfalk/synology-wireguard

It seems like your model is based out of the v1000 platform. See if this can help: https://github.com/runfalk/synology-wireguard/issues/61

Anyone knows how to do this. I installed runfalk/synology-wireguard with complied .spk file, I managed setup macOS client and hand shake is successful. I added /etc/sysctl.conf with net.ipv4.ip_forward=1 as stated in this. But no success, the Synology is reachable via wireguard tunnel but not internet,

But you could try this, if your NAS is supported: https://github.com/runfalk/synology-wireguard

not native but this has worked well for me for creating a server endpoint