-
-
Notifications
You must be signed in to change notification settings - Fork 337
Description
Model: DS1525+ (x86_64)
DSM version: 7.2.2-72806 Update 5
Script version: 3.6.111 (fresh download from main branch, November 24 2025)
Disk: Seagate IronWolf ST8000VN004-3CP101 (SC60 firmware)
Problem:
The script always exits with ERROR 4 Host db file not found! even when the host db file exists and all possible symlinks are created.
Important note:
Everything worked perfectly on the same DS1525+ before updating to DSM 7.2.2-72806 Update 5. After this exact update the host db file simply disappeared and the script can no longer find/create it.
What I already tried (nothing helped):
-
Fresh download of the script + syno_hdd_vendor_ids.txt is present
-
Manually created
/usr/syno/etc.defaults/ds1525+_host.dbwith correct CSV format -
Created every possible symlink:
/usr/syno/etc.defaults/hdddb → ds1525+_host.db
/usr/syno/etc.defaults/DS1525+_host.db → ds1525+_host.db
/usr/syno/etc/hdddb → ds1525+_host.db
/etc.defaults/hdddb → ds1525+_host.db
/etc/hdddb → ds1525+_host.db -
Permissions 644, owner root
-
Ran with every combination:
-n -i -f -I --showedits,-n -i -f,-n, etc. → always ERROR 4
Expected behaviour:
The script should either find the existing ds1525+_host.db or create it automatically when missing (as it successfully does on older models and on DS1522+/DS1823xs+ in other issues).
Why this is critical for 2025+ series:
Starting exactly with DSM 7.2.2-72806 Update 5 on DS1525+ (and probably DS925+, DS1825+, etc.) Synology stopped creating the host db file at all - this is the new aggressive vendor-lock. The only 100 % working workaround right now is setting support_disk_compatibility=no in synoinfo.conf, but that defeats the whole purpose of the script.
Request:
Please add automatic creation of the host db file for 2025+ models (DS1525+, DS925+, DS1825+, etc.) when it is not found, or at least make the script log the exact path/name it expects for the DS1525+.
This regression appeared exactly with 72806-5 — previous DSM builds on the same NAS worked fine with the script.
Thank you so much for this life-saving script — it has helped thousands of people, and the 2025+ models just broke the old detection logic.
Best regards!