[GH-ISSUE #567] M.2 SATA SSD in M2D18 is treated as internal SSD #210

New issue

Closed

opened 2026-03-07 19:17:04 +03:00 by kerem · 3 comments

kerem commented

2026-03-07 19:17:04 +03:00

Owner

Originally created by @steinreiter on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/567

I purchased a DS1517+ (DSM 7.3.2) with an M2D18 PCIe card as a backup device. The DS1517+ only supports M.2 SATA SSDs in the M2D18 slot. The system incorrectly attempts to configure these m.2 SATA Drives using Write-Mostly. An error message also appears beforehand because the nvme command is not available on the DS1517+ due to a lack of support. It would be helpful to check if the nvme tool is present before running it.

Here is the log of the execution (drive data anonymized):

Synology_HDD_db v3.6.123
DS1517+-j x86_64 DSM 7.3.2-86009-1

Using model: ds1517+
- StorageManager 1.0.1-1100
- SynoOnlinePack_v2 version 99991038
- ds1517+_host_v7 version 8052

Using options: --noupdate --ram --email -S
Running from: /volume1/scripts/syno_hdd_db/syno_hdd_db.sh
Running via task scheduler
/volume1/scripts/syno_hdd_db/syno_hdd_db.sh: line 976: nvme: command not found
/volume1/scripts/syno_hdd_db/syno_hdd_db.sh: line 976: nvme: command not found

HDD/SSD models found: 2
XXXXXSATASSD
YYYYYSATAHDD

M.2 drive models found: 1
ZZZZZM2SATASSD

M.2 PCIe card models found: 1
M2D18

No Expansion Units found

XXXXXSATASSD (ABC) already exists in ds1517+_host_v7.db
YYYYYSATAHDD (DEF) already exists in ds1517+_host_v7.db
ZZZZZM2SATASSD (GHI) already exists in ds1517+_host_v7.db
ZZZZZM2SATASSD (GHI) already exists in ds1517+_m2d18_v7.db

M2D18 NVMe already enabled for DS1517+
M2D18 SATA already enabled for DS1517+

Setting internal HDDs state to write_mostly
YYYYYSATAHDD
/volume1/scripts/syno_hdd_db/syno_hdd_db.sh: line 709: /sys/block/md0/md/dev-sdbp1/state: No such file or directory
sdb DSM partition: cat: /sys/block/md0/md/dev-sdbp1/state: No such file or directory
/volume1/scripts/syno_hdd_db/syno_hdd_db.sh: line 715: /sys/block/md1/md/dev-sdbp2/state: No such file or directory
sdb Swap partition: cat: /sys/block/md1/md/dev-sdbp2/state: No such file or directory

Support disk compatibility already enabled.

Max memory already set to 16 GB.

M.2 volume support already enabled.

Drive db auto updates already disabled.

Creating pool in UI on drives in M.2 adaptor card already enabled.

DSM successfully checked disk compatibility.

You may need to reboot the Synology to see the changes.

Originally created by @steinreiter on GitHub (Feb 20, 2026). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/567 I purchased a DS1517+ (DSM 7.3.2) with an M2D18 PCIe card as a backup device. The DS1517+ only supports M.2 SATA SSDs in the M2D18 slot. The system incorrectly attempts to configure these m.2 SATA Drives using Write-Mostly. An error message also appears beforehand because the nvme command is not available on the DS1517+ due to a lack of support. It would be helpful to check if the nvme tool is present before running it. Here is the log of the execution (drive data anonymized): ``` Synology_HDD_db v3.6.123 DS1517+-j x86_64 DSM 7.3.2-86009-1 Using model: ds1517+ - StorageManager 1.0.1-1100 - SynoOnlinePack_v2 version 99991038 - ds1517+_host_v7 version 8052 Using options: --noupdate --ram --email -S Running from: /volume1/scripts/syno_hdd_db/syno_hdd_db.sh Running via task scheduler /volume1/scripts/syno_hdd_db/syno_hdd_db.sh: line 976: nvme: command not found /volume1/scripts/syno_hdd_db/syno_hdd_db.sh: line 976: nvme: command not found HDD/SSD models found: 2 XXXXXSATASSD YYYYYSATAHDD M.2 drive models found: 1 ZZZZZM2SATASSD M.2 PCIe card models found: 1 M2D18 No Expansion Units found XXXXXSATASSD (ABC) already exists in ds1517+_host_v7.db YYYYYSATAHDD (DEF) already exists in ds1517+_host_v7.db ZZZZZM2SATASSD (GHI) already exists in ds1517+_host_v7.db ZZZZZM2SATASSD (GHI) already exists in ds1517+_m2d18_v7.db M2D18 NVMe already enabled for DS1517+ M2D18 SATA already enabled for DS1517+ Setting internal HDDs state to write_mostly YYYYYSATAHDD /volume1/scripts/syno_hdd_db/syno_hdd_db.sh: line 709: /sys/block/md0/md/dev-sdbp1/state: No such file or directory sdb DSM partition: cat: /sys/block/md0/md/dev-sdbp1/state: No such file or directory /volume1/scripts/syno_hdd_db/syno_hdd_db.sh: line 715: /sys/block/md1/md/dev-sdbp2/state: No such file or directory sdb Swap partition: cat: /sys/block/md1/md/dev-sdbp2/state: No such file or directory Support disk compatibility already enabled. Max memory already set to 16 GB. M.2 volume support already enabled. Drive db auto updates already disabled. Creating pool in UI on drives in M.2 adaptor card already enabled. DSM successfully checked disk compatibility. You may need to reboot the Synology to see the changes. ```

kerem closed this issue

2026-03-07 19:17:04 +03:00

kerem commented

2026-03-07 19:17:05 +03:00

Author

Owner

@007revad commented on GitHub (Feb 20, 2026):

Thanks. The script should not be trying to set write_mostly for any M.2 drives, or trying to get the vendor id for SATA M.2 drives using the nvme comand.

Does this command show the M.2 SATA drive as well as the HDDs? You don't have to mask the model numbers. Only drive serials should be masked - and this command does not show the serial numbers.

synodisk --enum

@007revad commented on GitHub (Feb 20, 2026): Thanks. The script should not be trying to set write_mostly for any M.2 drives, or trying to get the vendor id for SATA M.2 drives using the nvme comand. Does this command show the M.2 SATA drive as well as the HDDs? You don't have to mask the model numbers. Only drive serials should be masked - and this command does not show the serial numbers. ``` synodisk --enum ```

kerem commented

2026-03-07 19:17:05 +03:00

Author

Owner

@007revad commented on GitHub (Feb 20, 2026):

This version should have fixed both errors.
https://github.com/007revad/Synology_HDD_db/releases/tag/v3.6.124

@007revad commented on GitHub (Feb 20, 2026): This version should have fixed both errors. https://github.com/007revad/Synology_HDD_db/releases/tag/v3.6.124

kerem commented

2026-03-07 19:17:05 +03:00

Author

Owner

@steinreiter commented on GitHub (Feb 22, 2026):

Thanks. The script should not be trying to set write_mostly for any M.2 drives, or trying to get the vendor id for SATA M.2 drives using the nvme comand.

Does this command show the M.2 SATA drive as well as the HDDs? You don't have to mask the model numbers. Only drive serials should be masked - and this command does not show the serial numbers.
synodisk --enum

No, this command does not show the M.2 SATA drives.

This version should have fixed both errors. https://github.com/007revad/Synology_HDD_db/releases/tag/v3.6.124

Thanks, this version fixed it.

@steinreiter commented on GitHub (Feb 22, 2026): > Thanks. The script should not be trying to set write_mostly for any M.2 drives, or trying to get the vendor id for SATA M.2 drives using the nvme comand. > > Does this command show the M.2 SATA drive as well as the HDDs? You don't have to mask the model numbers. Only drive serials should be masked - and this command does not show the serial numbers. > > ``` > synodisk --enum > ``` No, this command does not show the M.2 SATA drives. > This version should have fixed both errors. https://github.com/007revad/Synology_HDD_db/releases/tag/v3.6.124 Thanks, this version fixed it.

kerem referenced this issue

2026-03-07 19:17:45 +03:00

[PR #210] [MERGED] Develop #320

kerem referenced this issue

2026-03-07 19:17:48 +03:00

[PR #221] [MERGED] sync from main #327

kerem referenced this issue

2026-03-12 17:44:36 +03:00

[PR #210] [MERGED] Develop #978

kerem referenced this issue

2026-03-12 17:45:09 +03:00

[PR #221] [MERGED] sync from main #990