Synology_M2_volume VS Synology_HDD_db

DSM won't let you create a storage pool on drives in a PCIe adapter card so for the NVMe drives in the E10M20-T1 I used my https://github.com/007revad/Synology_M2_volume script to create the storage pool.

For more information and to download see: https://github.com/007revad/Synology_M2_volume

So I got my DS423+ and love the NAS and ecosystem so far!! I also have a WD RED SN700 unfortunately I at first could not create a storage pool out if it as Synology only supports their own NVME ssds. my WD RED SN700 with 2TB is cheaper than the Synology one which just has 400gb. Luckily I was able to create a storage pool on the WD using this https://github.com/007revad/Synology_M2_volume !!!

DS916+, DS920+ and DS1522+ all working well with 3rd party RAM. Yes, it moans about it, but no issues. NVMe as a volume is also working on the DS920+ and DS1522+ (https://github.com/007revad/Synology_M2_volume) although I did have to recreate the volumes (I have always make sure I back them up with Hyper-Backup anyway).

Probably something like this but if the OP can't articulate what they did probably also didn't read the "Important" paragraph:

You will need to use the SSH scripts to turn up NVMe as a storage pool on 3rd party drives - https://github.com/007revad/Synology_M2_volume

You could have done it without all that typing by using https://github.com/007revad/Synology_M2_volume

If you do end up having to wipe the drives and decide you want to try again, I’d recommend using this https://github.com/007revad/Synology_M2_volume it’s way easier than running all the commands yourself and super simple. It’s how I made my nvme pool and it worked great.

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