mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #441] DS1522+ DSM 7.2.2 - 72806 Update 3 Issue with WD Red SN700 1TB NVMe Drives on DS1522+: Still Incompatible #656
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#656
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Aquilasfx on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/441
Hi everyone,
I’m facing an issue with my WD Red SN700 1TB NVMe drives on my DS1522+ NAS. Despite trying various configurations and options, the drives are still reported as incompatible.
Here’s what I’ve tried so far:
Using the syno_hdd_db.sh script with various options:
-r
-i
-f
-w
Rebooting the NAS after applying changes.
The script returns the following output:
`Synology_HDD_db v3.6.111
DS1522+ x86_64 DSM 7.2.2-72806-3
StorageManager 1.0.0-00502
ds1522+_host_v7 version 8044
Using options: -r -i -f -w
Running from: /volume1/scripts/syno_hdd_db.sh
HDD/SSD models found: 1
HDP725050GLA360,GM4OA5CA,500 GB
M.2 drive models found: 1
WD Red SN700 1000GB,111150WD,1000 GB
No M.2 PCIe cards found
No Expansion Units found
HDP725050GLA360 already exists in ds1522+_host_v7.db
WD Red SN700 1000GB already exists in ds1522+_host_v7.db
Disabled support disk compatibility.
Support memory compatibility already disabled.
Max memory is set to 32 GB.
NVMe support already enabled.
M.2 volume support already enabled.
Drive db auto updates already enabled.
Support WDDA already disabled.
DSM successfully checked disk compatibility.
You may need to reboot the Synology to see the changes.
`
Despite these changes, I continue to get the compatibility error for the WD Red SN700 drives.
I’m asking:
Do I need to run another script, such as Synology_enable_M2_volume, to fix this issue?
Is it necessary to apply a Scheduled Task for the changes to take effect, or is running the script manually enough?
Is there any other configuration or solution I can try to resolve the issue?
Thank you in advance for your help!
@007revad commented on GitHub (Mar 7, 2025):
Don't run Synology_enable_M2_volume
Try this:
syno_hdd_db.sh --restorethen reboot.syno_hdd_db.sh -n -wthen reboot.@Aquilasfx commented on GitHub (Mar 7, 2025):
Thank @007revad I tried as you suggested and after the second reboot, when I choose Add drive for storage expansion and choose NEXT choosing my actual storage pool it continue to say: "Cannot perform this action. No drives are available or meet the requirements." as you can see from the image attached.
@007revad commented on GitHub (Mar 7, 2025):
When you click on "View drive requirements" what does it say?
@Aquilasfx commented on GitHub (Mar 7, 2025):
It seys this as attached.
@007revad commented on GitHub (Mar 7, 2025):
Try scheduling syno_hdd_db.sh to run at boot, with the -n -w options, then reboot twice.
@Aquilasfx commented on GitHub (Mar 7, 2025):
@007revad I tried as suggested scheduling syno_hdd_db.sh to run at boot, with the -n -w options, but the system continue to say compatibility error for the WD Red SN700 drives
@Aquilasfx commented on GitHub (Mar 10, 2025):
Dear @007revad I understand you previously advised not to use "Synology_enable_M2_volume" script, but given the current situation, do you think it might be worth trying at this point? Or is there another approach you’d recommend?
I really appreciate your time and help, and I’d be grateful for any further guidance you can provide.
Thanks again!
@007revad commented on GitHub (Mar 10, 2025):
With your current situation you might as well try the Synology_enable_M2_volume script.
@Aquilasfx commented on GitHub (Mar 10, 2025):
Thank you for your help, I really appreciate it! 🙌
I'll give the Synology_enable_M2_volume script a try. Do you think this issue could be related to that specific NVMe model, the WD Red SN700? I bought them because they were recommended on Reddit, but I'm wondering if they might be causing the problem.
Thanks again for your time! 😊
@007revad commented on GitHub (Mar 11, 2025):
WD Red SN700 are good NVMe drives. They work well as a cache or a volume.
@sandros94 commented on GitHub (Apr 6, 2025):
Having similar issues with a
WDS100T3X0C-00SJG0(WD BLACK SN750), everything works with Synology_enable_M2_volume script tho.@anschluss-org commented on GitHub (May 25, 2025):
I‘ve seen this happen to me with WD SN700 drives on DS723+ and DS923+. My remedy is to run syno_hdd_db in a loop from a terminal session while I set up the new storage pool and volume.
@kaktuspalme commented on GitHub (Jul 30, 2025):
I had the same error. Doing echo 1 > m2_pool_support in /run/synostorage/disks/ in the corresponding disk folder, in my case /run/synostorage/disks/nvme0n1 resolved the issue for me.
Edit: I did run Synology_M2_volume script before but cancelled at step 4 as I didn't want to create a new storage pool, I'm not sure the script did anything already, but in case it did, it might have fixed it as well.
@seederp2p commented on GitHub (Jan 13, 2026):
This was the fix for me after running the syno_hdd_db.sh script....
@007revad commented on GitHub (Jan 19, 2026):
I've updated the script to run
echo -n 1 > m2_pool_support in /run/synostorage/disks/nvmeNn1at the end of the script, after forcing DSM to check drive compatability to try to prevent NVMe drives still showing as incompatible for some people.https://github.com/007revad/Synology_HDD_db/releases/tag/v3.6.118