Synology_HDD_db VS Synology_Config_Backup

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

Synology_Config_Backup

If you have SSH enabled and can connect via SSH you could use my script to backup the system config: https://github.com/007revad/Synology_Config_Backup

I have a daily schedule that runs a script I wrote to backup the system config (and optionally copy it to another server). https://github.com/007revad/Synology_Config_Backup

If you are trying to copy a file from a local device to a remote device use SCP with SSH keys already setup. See my script here: https://github.com/007revad/Synology_Config_Backup/blob/main/synology_config_backup.sh