Synology_HDD_db: Samsung 970 listed as incompatible on 1621+ when trying to create storage pool
I’ve run the script (and tried running it again):
Samsung SSD 970 EVO Plus 2TB already exists in ds1621+_host_v7.db
Samsung SSD 970 EVO Plus 2TB already exists in ds1621+_host_v7.db.new
Is there a different database that gets checked for the new feature in DSM 7.2 where creating storage pools from NVME drives is supported in the 1621+?
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 25 (10 by maintainers)
This is actually something I can test myself as I have a DS1821+. I was reluctant to try DSM 7.2 beta but I now I have a reason to try it to see how Synology is blocking 3rd party NVMe drives. It might take me a few days to figure out.
@inkpool @ctrlaltdelete007 @linguowei @MarkErik
v2.0.35 just released and now, thanks to @nicolerenee, allows creating the storage pool and volume from Storage Manager, for any M.2 drive(s).
FYI: No problems doing the upgrade from 7.2 Beta to 7.2 RC. All the SSD volumes that I had created were still there working. edit. However the inconsistent speed/performance still persists.
works fine with 7.2 beta.
I just tested the new version since my second NVMe showed up today and it worked perfectly.
I was able to create a new 3rd party NVMe volume in the GUI after running the script in this repo and then running the following command:
For my NVMe drive. I only have one right now so I only ran it for that drive, once I get my other one I’ll test what it required for it if anything.
enabling storage pool is not synlogy with ssd: https://xpenology.com/forum/topic/67961-use-nvmem2-hard-drives-as-storage-pools-in-synology/
support_m2_pool=“yes” is already set on models that support M.2 volumes. And on models that don’t officially support M.2 volumes my script sets it to yes, or adds the line if it’s missing.
Yes.