Synology_HDD_db VS Synology_SHR_switch

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

If you buy an enterprise Synology and want SHR you can use my Synology_RAID-F1_SHR_switch script to enable SHR and disable RAID F1 (or vice versa). https://github.com/007revad/Synology_RAID-F1_SHR_switch

You can easily enable RAID F1, at the expense of SHR, by changing settings in a config file but it probably won't do anything on a model that doesn't already include support RAID F1.

Do you know that I have a script to switch between SHR and RAID-F1

You can enable SHR with my Synology_RAID-F1_SHR_switch script.

Run my Synology_RAID-F1_SHR_switch to enable RAID F1 (which also disables SHR).