starred/Synology_HDD_db
1
0
Fork 0
mirror of https://github.com/007revad/Synology_HDD_db.git synced 2026-04-25 21:55:59 +03:00
Code Issues 102 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #520] M.2 NVMe's through M2D20 seems not to be added to compatibility list on DS1825+ running DSM 7.3-81180 #179

New issue
Open
opened 2026-03-07 19:16:46 +03:00 by kerem · 9 comments
kerem commented 2026-03-07 19:16:46 +03:00
Owner
Copy link

Originally created by @kennydm00 on GitHub (Oct 27, 2025).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/520

I have successfully added the M2D20 to my DS1825+ running DSM 7.3-81180 using your new version of syno_enable_m2_card.sh script.
But now I have trouble getting the connected WD_Black SSDs to be added to the compatibility list using your syno_hdd_db.sh script.
Therefore I have trouble creating a storage pool or volume using the DSM storage manager.
I can however start the syno_hdd_db.sh script with the -f parameter to disable the compatibility check and create the storage pool and volume then, but with disabling the check I loose the ability to create the TRIM scheduler entry for any of the SSDs (the only storage pool setting is the description).

Output of the syno_hdd_db.sh script:

Synology_HDD_db v3.6.111
DS1825+ x86_64 DSM 7.3-81180
StorageManager 1.0.0-01026

ds1825+_host_v7 version 8008

Using options: -nr
Running from: /volume2/homes/kenny/Synology_HDD_db-main/syno_hdd_db.sh

WARNING Don't store this script on an NVMe volume!

HDD/SSD models found: 2
Red SA500 2.5 4TB,540500WD,4000 GB
ST28000NM003K-3TE133,SE02,28001 GB

M.2 drive models found: 2
WD_BLACK SN7100 1TB,7615M0WD,1000 GB
WD Red SN700 2000GB,112000WD,2000 GB

M.2 PCIe card models found: 1
M2D20

No Expansion Units found

Red SA500 2.5 4TB already exists in ds418play_host.db
Red SA500 2.5 4TB already exists in ds418play_host_v7.db
Red SA500 2.5 4TB already exists in ds1825+_host_v7.db
Red SA500 2.5 4TB already exists in ds418play_host.db.new
ST28000NM003K-3TE133 already exists in ds418play_host.db
ST28000NM003K-3TE133 already exists in ds418play_host_v7.db
ST28000NM003K-3TE133 already exists in ds1825+_host_v7.db
ST28000NM003K-3TE133 already exists in ds418play_host.db.new
WD_BLACK SN7100 1TB already exists in ds418play_host.db
WD_BLACK SN7100 1TB already exists in ds418play_host_v7.db
WD_BLACK SN7100 1TB already exists in ds1825+_host_v7.db
WD_BLACK SN7100 1TB already exists in ds418play_host.db.new
Added WD_BLACK SN7100 1TB to ds1825+_m2d20_v7.db
WD_BLACK SN7100 1TB already exists in ds418play_m2d20_v7.db
WD Red SN700 2000GB already exists in ds418play_host.db
WD Red SN700 2000GB already exists in ds418play_host_v7.db
WD Red SN700 2000GB already exists in ds1825+_host_v7.db
WD Red SN700 2000GB already exists in ds418play_host.db.new
Added WD Red SN700 2000GB to ds1825+_m2d20_v7.db
WD Red SN700 2000GB already exists in ds418play_m2d20_v7.db

M2D20 NVMe already enabled for DS1825+
M2D20 already exists in model.dtb

Support disk compatibility already enabled.

Max memory already set to 32 GB.

NVMe support already enabled.

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.

Screenshot of storage manager errors and disabled settings option:

Image Image

Thank you again for your help for the M2D20 issue and I'm sorry to bother you again...

Originally created by @kennydm00 on GitHub (Oct 27, 2025). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/520 I have successfully added the **M2D20** to my **DS1825+** running **DSM 7.3-81180** using your new version of **syno_enable_m2_card.sh** script. But now I have trouble getting the connected **WD_Black** SSDs to be added to the compatibility list using your **syno_hdd_db.sh** script. Therefore I have trouble creating a storage pool or volume using the DSM storage manager. I can however start the **syno_hdd_db.sh** script with the **-f** parameter to disable the compatibility check and create the storage pool and volume then, but with disabling the check I loose the ability to create the TRIM scheduler entry for any of the SSDs (the only storage pool setting is the description). Output of the syno_hdd_db.sh script: ``` Synology_HDD_db v3.6.111 DS1825+ x86_64 DSM 7.3-81180 StorageManager 1.0.0-01026 ds1825+_host_v7 version 8008 Using options: -nr Running from: /volume2/homes/kenny/Synology_HDD_db-main/syno_hdd_db.sh WARNING Don't store this script on an NVMe volume! HDD/SSD models found: 2 Red SA500 2.5 4TB,540500WD,4000 GB ST28000NM003K-3TE133,SE02,28001 GB M.2 drive models found: 2 WD_BLACK SN7100 1TB,7615M0WD,1000 GB WD Red SN700 2000GB,112000WD,2000 GB M.2 PCIe card models found: 1 M2D20 No Expansion Units found Red SA500 2.5 4TB already exists in ds418play_host.db Red SA500 2.5 4TB already exists in ds418play_host_v7.db Red SA500 2.5 4TB already exists in ds1825+_host_v7.db Red SA500 2.5 4TB already exists in ds418play_host.db.new ST28000NM003K-3TE133 already exists in ds418play_host.db ST28000NM003K-3TE133 already exists in ds418play_host_v7.db ST28000NM003K-3TE133 already exists in ds1825+_host_v7.db ST28000NM003K-3TE133 already exists in ds418play_host.db.new WD_BLACK SN7100 1TB already exists in ds418play_host.db WD_BLACK SN7100 1TB already exists in ds418play_host_v7.db WD_BLACK SN7100 1TB already exists in ds1825+_host_v7.db WD_BLACK SN7100 1TB already exists in ds418play_host.db.new Added WD_BLACK SN7100 1TB to ds1825+_m2d20_v7.db WD_BLACK SN7100 1TB already exists in ds418play_m2d20_v7.db WD Red SN700 2000GB already exists in ds418play_host.db WD Red SN700 2000GB already exists in ds418play_host_v7.db WD Red SN700 2000GB already exists in ds1825+_host_v7.db WD Red SN700 2000GB already exists in ds418play_host.db.new Added WD Red SN700 2000GB to ds1825+_m2d20_v7.db WD Red SN700 2000GB already exists in ds418play_m2d20_v7.db M2D20 NVMe already enabled for DS1825+ M2D20 already exists in model.dtb Support disk compatibility already enabled. Max memory already set to 32 GB. NVMe support already enabled. 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. ``` Screenshot of storage manager errors and disabled settings option: <img width="2289" height="496" alt="Image" src="https://github.com/user-attachments/assets/a0fc4eac-0ed3-4d65-ae59-90a8d759708a" /> <img width="918" height="121" alt="Image" src="https://github.com/user-attachments/assets/145e393c-d110-469b-96f8-190754dc2c50" /> Thank you again for your help for the M2D20 issue and I'm sorry to bother you again...
kerem commented 2026-03-07 19:16:47 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Oct 27, 2025):

Do you run syno_hdd_db with the -n option? You should always run it with the -n option. This prevents DSM from updating the db files.

Did you migrate the HDDs from a DS418play?

Lets remove those old ds418play db files.

sudo for f in /var/lib/disk-compatibility/ds418play*; do rm "$f"; done
<!-- gh-comment-id:3453568547 --> @007revad commented on GitHub (Oct 27, 2025): Do you run syno_hdd_db with the -n option? You should always run it with the -n option. This prevents DSM from updating the db files. Did you migrate the HDDs from a DS418play? Lets remove those old ds418play db files. ``` sudo for f in /var/lib/disk-compatibility/ds418play*; do rm "$f"; done ```
kerem commented 2026-03-07 19:16:47 +03:00
Author
Owner
Copy link

@kennydm00 commented on GitHub (Oct 28, 2025):

Yes I'm running the script with the -n option and I have migrated from an DS418play.
In the /var/lib/disk-compatibility/ folder are many other entries of diskstations, should these also be deleted?

ds1825+_e10m20-t1_v7.db          rx1211rp_v7.version
 ds1825+_e10m20-t1_v7.release     rx1211rp.version
 ds1825+_e10m20-t1_v7.version     rx1211_v7.db
 ds1825+_host_v7.db               rx1211_v7.db.bak
 ds1825+_host_v7.db.bak           rx1211_v7.release
 ds1825+_host_v7.release          rx1211_v7.version
 ds1825+_host_v7.version          rx1211.version
 ds1825+_m2d17_v7.db              rx1213sas.db
 ds1825+_m2d17_v7.release         rx1213sas_v7.db
 ds1825+_m2d17_v7.version         rx1213sas_v7.db.bak
 ds1825+_m2d18_v7.db              rx1213sas_v7.release
 ds1825+_m2d18_v7.release         rx1213sas_v7.version
 ds1825+_m2d18_v7.version         rx1213sas.version
 ds1825+_m2d20_v7.db              rx1214.db
 ds1825+_m2d20_v7.db.bak          rx1214rp.db
 ds1825+_m2d20_v7.release         rx1214rp_v7.db
 ds1825+_m2d20_v7.version         rx1214rp_v7.db.bak
 ds418play_e10m20-t1_v7.db        rx1214rp_v7.release
 ds418play_e10m20-t1_v7.release   rx1214rp_v7.version
 ds418play_e10m20-t1_v7.version   rx1214rp.version
 ds418play_host.db                rx1214_v7.db
 ds418play_host.db.bak            rx1214_v7.db.bak
 ds418play_host.db.new            rx1214_v7.release
 ds418play_host.db.new.bak        rx1214_v7.version
 ds418play_host.release           rx1214.version
 ds418play_host_v7.db             rx1216sas.db
 ds418play_host_v7.db.bak         rx1216sas_v7.db
 ds418play_host_v7.release        rx1216sas_v7.db.bak
 ds418play_host_v7.version        rx1216sas_v7.db.new
 ds418play_host.version           rx1216sas_v7.release
 ds418play_m2d17_v7.db            rx1216sas_v7.version
 ds418play_m2d17_v7.release       rx1216sas.version
 ds418play_m2d17_v7.version       rx1217.db
 ds418play_m2d18_v7.db            rx1217rp.db
 ds418play_m2d18_v7.release       rx1217rp_v7.db
 ds418play_m2d18_v7.version       rx1217rp_v7.db.bak
 ds418play_m2d20_v7.db            rx1217rp_v7.release
 ds418play_m2d20_v7.db.bak        rx1217rp_v7.version
 ds418play_m2d20_v7.release       rx1217rp.version
 ds418play_m2d20_v7.version       rx1217sas.db
 dx1211.db                        rx1217sas_v7.db
 dx1211_v7.db                     rx1217sas_v7.db.bak
 dx1211_v7.db.bak                 rx1217sas_v7.release
 dx1211_v7.release                rx1217sas_v7.version
 dx1211_v7.version                rx1217sas.version
 dx1211.version                   rx1217_v7.db
 dx1215.db                        rx1217_v7.db.bak
 dx1215ii_v7.db                   rx1217_v7.release
 dx1215ii_v7.db.bak               rx1217_v7.version
 dx1215ii_v7.db.new               rx1217.version
 dx1215ii_v7.release              rx1222sas_v7.db
 dx1215ii_v7.version              rx1222sas_v7.db.bak
 dx1215_v7.db                     rx1222sas_v7.db.new
 dx1215_v7.db.bak                 rx1222sas_v7.release
 dx1215_v7.db.new                 rx1222sas_v7.version
 dx1215_v7.release                rx1223rp_v7.db
 dx1215_v7.version                rx1223rp_v7.db.bak
 dx1215.version                   rx1223rp_v7.db.new
 dx1222_v7.db                     rx1223rp_v7.release
 dx1222_v7.db.bak                 rx1223rp_v7.version
 dx1222_v7.db.new                 rx1224rp_v7.db
 dx1222_v7.release                rx1224rp_v7.db.bak
 dx1222_v7.version                rx1224rp_v7.version
 dx213.db                         rx1225rp_v7.db
 dx213_v7.db                      rx1225rp_v7.db.bak
 dx213_v7.db.bak                  rx1225rp_v7.db.new
 dx213_v7.release                 rx1225rp_v7.release
 dx213_v7.version                 rx1225rp_v7.version
 dx213.version                    rx2417sas.db
 dx510.db                         rx2417sas_v7.db
 dx510_v7.db                      rx2417sas_v7.db.bak
 dx510_v7.db.bak                  rx2417sas_v7.release
 dx510_v7.release                 rx2417sas_v7.version
 dx510_v7.version                 rx2417sas.version
 dx510.version                    rx410.db
 dx513.db                         rx410_v7.db
 dx513_v7.db                      rx410_v7.db.bak
 dx513_v7.db.bak                  rx410_v7.release
 dx513_v7.release                 rx410_v7.version
 dx513_v7.version                 rx410.version
 dx513.version                    rx415.db
 dx517.db                         rx415_v7.db
 dx517_v7.db                      rx415_v7.db.bak
 dx517_v7.db.bak                  rx415_v7.release
 dx517_v7.db.new                  rx415_v7.version
 dx517_v7.release                 rx415.version
 dx517_v7.version                 rx418.db
 dx517.version                    rx418_v7.db
 dx525_v7.db                      rx418_v7.db.bak
 dx525_v7.db.bak                  rx418_v7.db.new
 dx525_v7.db.new                  rx418_v7.release
 dx525_v7.release                 rx418_v7.version
 dx525_v7.version                 rx418.version
 dx5.db                           rx426_v7.db
 dx5_v7.db                        rx426_v7.release
 dx5_v7.db.bak                    rx426_v7.version
 dx5_v7.release                   rx4.db
 dx5_v7.version                   rx4_v7.db
 dx5.version                      rx4_v7.db.bak
 eunit_rule.db                    rx4_v7.release
 eunit_rule.db.bak                rx4_v7.version
 eunit_rule.db.new                rx4.version
 eunit_rule.version               rx6022sas_v7.db
 fax224_v7.db                     rx6022sas_v7.db.bak
 fax224_v7.db.bak                 rx6022sas_v7.db.new
 fax224_v7.version                rx6022sas_v7.release
 fx2421_v7.db                     rx6022sas_v7.version
 fx2421_v7.db.bak                 rx6025sas_v7.db
 fx2421_v7.db.new                 rx6025sas_v7.db.bak
 fx2421_v7.release                rx6025sas_v7.db.new
 fx2421_v7.version                rx6025sas_v7.release
 fx2424dn_v7.db                   rx6025sas_v7.version
 fx2424dn_v7.version              rxd1215sas.db
 host.db                          rxd1215sas_v7.db
 host.db.bak                      rxd1215sas_v7.db.bak
 host.db.new                      rxd1215sas_v7.db.new
 host_rule.db                     rxd1215sas_v7.release
 host_rule.db.bak                 rxd1215sas_v7.version
 host_rule.db.new                 rxd1215sas.version
 host_rule.version                rxd1219sas.db
 host.version                    'rxd1219sas module_v7.db'
 pax224_v7.db                    'rxd1219sas module_v7.db.bak'
 pax224_v7.db.bak                'rxd1219sas module_v7.release'
 pax224_v7.db.new                'rxd1219sas module_v7.version'
 pax224_v7.version                rxd1219sas_v7.db
 rules                            rxd1219sas_v7.db.bak
 rx1211.db                        rxd1219sas_v7.db.new
 rx1211rp.db                      rxd1219sas_v7.release
 rx1211rp_v7.db                   rxd1219sas_v7.version
 rx1211rp_v7.db.bak               rxd1219sas.version
 rx1211rp_v7.release
<!-- gh-comment-id:3454876305 --> @kennydm00 commented on GitHub (Oct 28, 2025): Yes I'm running the script with the -n option and I have migrated from an DS418play. In the /var/lib/disk-compatibility/ folder are many other entries of diskstations, should these also be deleted? ``` ds1825+_e10m20-t1_v7.db rx1211rp_v7.version ds1825+_e10m20-t1_v7.release rx1211rp.version ds1825+_e10m20-t1_v7.version rx1211_v7.db ds1825+_host_v7.db rx1211_v7.db.bak ds1825+_host_v7.db.bak rx1211_v7.release ds1825+_host_v7.release rx1211_v7.version ds1825+_host_v7.version rx1211.version ds1825+_m2d17_v7.db rx1213sas.db ds1825+_m2d17_v7.release rx1213sas_v7.db ds1825+_m2d17_v7.version rx1213sas_v7.db.bak ds1825+_m2d18_v7.db rx1213sas_v7.release ds1825+_m2d18_v7.release rx1213sas_v7.version ds1825+_m2d18_v7.version rx1213sas.version ds1825+_m2d20_v7.db rx1214.db ds1825+_m2d20_v7.db.bak rx1214rp.db ds1825+_m2d20_v7.release rx1214rp_v7.db ds1825+_m2d20_v7.version rx1214rp_v7.db.bak ds418play_e10m20-t1_v7.db rx1214rp_v7.release ds418play_e10m20-t1_v7.release rx1214rp_v7.version ds418play_e10m20-t1_v7.version rx1214rp.version ds418play_host.db rx1214_v7.db ds418play_host.db.bak rx1214_v7.db.bak ds418play_host.db.new rx1214_v7.release ds418play_host.db.new.bak rx1214_v7.version ds418play_host.release rx1214.version ds418play_host_v7.db rx1216sas.db ds418play_host_v7.db.bak rx1216sas_v7.db ds418play_host_v7.release rx1216sas_v7.db.bak ds418play_host_v7.version rx1216sas_v7.db.new ds418play_host.version rx1216sas_v7.release ds418play_m2d17_v7.db rx1216sas_v7.version ds418play_m2d17_v7.release rx1216sas.version ds418play_m2d17_v7.version rx1217.db ds418play_m2d18_v7.db rx1217rp.db ds418play_m2d18_v7.release rx1217rp_v7.db ds418play_m2d18_v7.version rx1217rp_v7.db.bak ds418play_m2d20_v7.db rx1217rp_v7.release ds418play_m2d20_v7.db.bak rx1217rp_v7.version ds418play_m2d20_v7.release rx1217rp.version ds418play_m2d20_v7.version rx1217sas.db dx1211.db rx1217sas_v7.db dx1211_v7.db rx1217sas_v7.db.bak dx1211_v7.db.bak rx1217sas_v7.release dx1211_v7.release rx1217sas_v7.version dx1211_v7.version rx1217sas.version dx1211.version rx1217_v7.db dx1215.db rx1217_v7.db.bak dx1215ii_v7.db rx1217_v7.release dx1215ii_v7.db.bak rx1217_v7.version dx1215ii_v7.db.new rx1217.version dx1215ii_v7.release rx1222sas_v7.db dx1215ii_v7.version rx1222sas_v7.db.bak dx1215_v7.db rx1222sas_v7.db.new dx1215_v7.db.bak rx1222sas_v7.release dx1215_v7.db.new rx1222sas_v7.version dx1215_v7.release rx1223rp_v7.db dx1215_v7.version rx1223rp_v7.db.bak dx1215.version rx1223rp_v7.db.new dx1222_v7.db rx1223rp_v7.release dx1222_v7.db.bak rx1223rp_v7.version dx1222_v7.db.new rx1224rp_v7.db dx1222_v7.release rx1224rp_v7.db.bak dx1222_v7.version rx1224rp_v7.version dx213.db rx1225rp_v7.db dx213_v7.db rx1225rp_v7.db.bak dx213_v7.db.bak rx1225rp_v7.db.new dx213_v7.release rx1225rp_v7.release dx213_v7.version rx1225rp_v7.version dx213.version rx2417sas.db dx510.db rx2417sas_v7.db dx510_v7.db rx2417sas_v7.db.bak dx510_v7.db.bak rx2417sas_v7.release dx510_v7.release rx2417sas_v7.version dx510_v7.version rx2417sas.version dx510.version rx410.db dx513.db rx410_v7.db dx513_v7.db rx410_v7.db.bak dx513_v7.db.bak rx410_v7.release dx513_v7.release rx410_v7.version dx513_v7.version rx410.version dx513.version rx415.db dx517.db rx415_v7.db dx517_v7.db rx415_v7.db.bak dx517_v7.db.bak rx415_v7.release dx517_v7.db.new rx415_v7.version dx517_v7.release rx415.version dx517_v7.version rx418.db dx517.version rx418_v7.db dx525_v7.db rx418_v7.db.bak dx525_v7.db.bak rx418_v7.db.new dx525_v7.db.new rx418_v7.release dx525_v7.release rx418_v7.version dx525_v7.version rx418.version dx5.db rx426_v7.db dx5_v7.db rx426_v7.release dx5_v7.db.bak rx426_v7.version dx5_v7.release rx4.db dx5_v7.version rx4_v7.db dx5.version rx4_v7.db.bak eunit_rule.db rx4_v7.release eunit_rule.db.bak rx4_v7.version eunit_rule.db.new rx4.version eunit_rule.version rx6022sas_v7.db fax224_v7.db rx6022sas_v7.db.bak fax224_v7.db.bak rx6022sas_v7.db.new fax224_v7.version rx6022sas_v7.release fx2421_v7.db rx6022sas_v7.version fx2421_v7.db.bak rx6025sas_v7.db fx2421_v7.db.new rx6025sas_v7.db.bak fx2421_v7.release rx6025sas_v7.db.new fx2421_v7.version rx6025sas_v7.release fx2424dn_v7.db rx6025sas_v7.version fx2424dn_v7.version rxd1215sas.db host.db rxd1215sas_v7.db host.db.bak rxd1215sas_v7.db.bak host.db.new rxd1215sas_v7.db.new host_rule.db rxd1215sas_v7.release host_rule.db.bak rxd1215sas_v7.version host_rule.db.new rxd1215sas.version host_rule.version rxd1219sas.db host.version 'rxd1219sas module_v7.db' pax224_v7.db 'rxd1219sas module_v7.db.bak' pax224_v7.db.bak 'rxd1219sas module_v7.release' pax224_v7.db.new 'rxd1219sas module_v7.version' pax224_v7.version rxd1219sas_v7.db rules rxd1219sas_v7.db.bak rx1211.db rxd1219sas_v7.db.new rx1211rp.db rxd1219sas_v7.release rx1211rp_v7.db rxd1219sas_v7.version rx1211rp_v7.db.bak rxd1219sas.version rx1211rp_v7.release ```
kerem commented 2026-03-07 19:16:47 +03:00
Author
Owner
Copy link

@kennydm00 commented on GitHub (Oct 28, 2025):

I have moved the files and run the script again:

Image

but with the same result

<!-- gh-comment-id:3454902976 --> @kennydm00 commented on GitHub (Oct 28, 2025): I have moved the files and run the script again: <img width="570" height="781" alt="Image" src="https://github.com/user-attachments/assets/7ba6d260-3cf5-429a-a8be-0d2fa6b8f800" /> but with the same result
kerem commented 2026-03-07 19:16:47 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Oct 28, 2025):

It's normal to have 89 dx, rx and fx files. It's as if Synology decided it was easier to include db files for every expansion unit for all NAS models.

Every time you run the script does it say it's added the NVMe drives to ds1825+_m2d20_v7.db ?

Image

The 2nd time you run it it should say the NVMe drives already exist in ds1825+_m2d20_v7.db

<!-- gh-comment-id:3455473890 --> @007revad commented on GitHub (Oct 28, 2025): It's normal to have 89 dx, rx and fx files. It's as if Synology decided it was easier to include db files for every expansion unit for all NAS models. Every time you run the script does it say it's added the NVMe drives to ds1825+_m2d20_v7.db ? <img width="570" height="59" alt="Image" src="https://github.com/user-attachments/assets/6e235eb0-4868-4217-9275-7acac3f5f79c" /> The 2nd time you run it it should say the NVMe drives already exist in ds1825+_m2d20_v7.db
kerem commented 2026-03-07 19:16:47 +03:00
Author
Owner
Copy link

@kennydm00 commented on GitHub (Oct 28, 2025):

Yes it does, for every run it says that it added the drives. I already thought that it's weird

<!-- gh-comment-id:3455705659 --> @kennydm00 commented on GitHub (Oct 28, 2025): Yes it does, for every run it says that it added the drives. I already thought that it's weird
kerem commented 2026-03-07 19:16:47 +03:00
Author
Owner
Copy link

@kennydm00 commented on GitHub (Oct 28, 2025):

Ok it seems, that the neither the WD_BLACK nor the WD Red are added to the ds1825+_m2d20_v7.db file.
The ds1825+_m2d20_v7.db file contains only:

{"disk_compatibility_info": {}, "nas_model": "ds1825+"}
<!-- gh-comment-id:3456375844 --> @kennydm00 commented on GitHub (Oct 28, 2025): Ok it seems, that the neither the **WD_BLACK** nor the **WD Red** are added to the **ds1825+_m2d20_v7.db** file. The **ds1825+_m2d20_v7.db** file contains only: ``` {"disk_compatibility_info": {}, "nas_model": "ds1825+"} ```
kerem commented 2026-03-07 19:16:48 +03:00
Author
Owner
Copy link

@kennydm00 commented on GitHub (Oct 30, 2025):

I have edited the ds1825+_m2d20_v7.db file manually and after running your script again I got:

Image

and now it's working :)

<!-- gh-comment-id:3469986241 --> @kennydm00 commented on GitHub (Oct 30, 2025): I have edited the ds1825+_m2d20_v7.db file manually and after running your script again I got: <img width="640" height="781" alt="Image" src="https://github.com/user-attachments/assets/bccc3687-b128-4763-aba1-1caec8d404a2" /> and now it's working :)
kerem commented 2026-03-07 19:16:48 +03:00
Author
Owner
Copy link

@007revad commented on GitHub (Oct 31, 2025):

If I write a debug version of the script are you willing to restore {"disk_compatibility_info": {}, "nas_model": "ds1825+"} in ds1825+_m2d20_v7.db and test the debug version so I can figure out why the script didn't edit ds1825+_m2d20_v7.db when you ran it.

It might be next week as I'm busy at the moment.

<!-- gh-comment-id:3470766286 --> @007revad commented on GitHub (Oct 31, 2025): If I write a debug version of the script are you willing to restore `{"disk_compatibility_info": {}, "nas_model": "ds1825+"}` in ds1825+_m2d20_v7.db and test the debug version so I can figure out why the script didn't edit ds1825+_m2d20_v7.db when you ran it. It might be next week as I'm busy at the moment.
kerem commented 2026-03-07 19:16:48 +03:00
Author
Owner
Copy link

@kennydm00 commented on GitHub (Oct 31, 2025):

Yes of course

<!-- gh-comment-id:3471012625 --> @kennydm00 commented on GitHub (Oct 31, 2025): Yes of course
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
develop
v3.6.125
v3.6.124
v3.6.123
v3.6.122
v3.6.121
v3.6.119
v3.6.118
v3.6.116
v3.6.115
v3.6.114
v3.6.113
v3.6.112
v3.6.111
v3.6.110
v3.6.109
v3.5.108
v3.5.107
v3.5.106
v3.5.105
v3.5.104
v3.5.103
v3.5.102
v3.5.101
v3.5.100-RC
v3.5.99-RC
v3.5.98
v3.5.97
v3.5.96
v3.5.94
v3.5.94-RC
v3.5.93
v3.5.92
v3.5.91
v3.5.90
v3.5.90-RC
v3.5.89
v3.5.88
v3.4.87
v3.4.86
v3.4.85
v3.4.84
v3.4.83
v3.4.82
v3.4.81
v3.4.80
v3.4.79
v3.4.78
v3.4.77
v3.3.73
v3.3.72
v3.3.70
v3.2.69
v3.2.68
v3.2.67-RC
v3.2.66-RC
v3.1.65
v3.1.64
v3.1.63
v3.1.62
v3.1.61
v3.1.60-RC
v3.1.59-RC
v3.1.58-RC
v3.1.57-RC
v3.0.56
v3.0.55
v2.3.54-RC
v2.3.51-RC
v2.3.49-RC
v2.3.48-RC
v2.2.47
v2.3.53-RC
v2.3.50-RC
v2.2.46
get_syno_model
v2.2.46_test
v2.2.45
v2.2.44
v2.2.43
v2.2.42
v2.2.39
v2.2.40
v2.2.41
v2.1.38
v2.1.37
v2.0.35
v1.3.34
v1.3.33
v1.3.32
v1.2.31
v1.2.30
v1.2.29
v1.2.28
v1.2.27
v1.2.25
v1.2.26
v1.2.24
v1.2.23
v1.2.22
v1.2.21
v1.2.20
v1.2.17
v1.2.16
v1.2.15
v1.1.14
v1.1.13
v1.1.12
v1.1.11
1.1.10
v1.1.9
1.1.8
v1.0.7
V1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
Labels
Clear labels   
bug

   
bug

   
bug

   
documentation

   
enhancement

   
enhancement

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
suggestion
No labels
bug
bug
bug
documentation
enhancement
enhancement
help wanted
pull-request
suggestion
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_HDD_db#179
No description provided.