[GH-ISSUE #2] Error: Cannot find hostdb file - DS1817+ running DSM6 #504

Closed
opened 2026-03-11 11:23:53 +03:00 by kerem · 7 comments
Owner

Originally created by @sthulin on GitHub (Feb 26, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/2

I have a DS1817+ running DSM6, after listing my disks i get the following error:

ERROR: /var/lib/disk-compatibility/ds1817+-j_host.db not found!

when i run "cat /proc/sys/kernel/syno_hw_version" i get back "ds1817+-j" so perhaps the last 2 characters need to be trimmed off in your script?

Originally created by @sthulin on GitHub (Feb 26, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/2 I have a DS1817+ running DSM6, after listing my disks i get the following error: ERROR: /var/lib/disk-compatibility/ds1817+-j_host.db not found! when i run "cat /proc/sys/kernel/syno_hw_version" i get back "ds1817+-j" so perhaps the last 2 characters need to be trimmed off in your script?
kerem 2026-03-11 11:23:53 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@007revad commented on GitHub (Feb 27, 2023):

Did you migrate the HDDs from a J model to the 1817+ ?

Do the following also include -j after ds1817+ ?

get_key_value /etc/synoinfo.conf unique
get_key_value /etc.defaults/synoinfo.conf unique

<!-- gh-comment-id:1445550813 --> @007revad commented on GitHub (Feb 27, 2023): Did you migrate the HDDs from a J model to the 1817+ ? Do the following also include -j after ds1817+ ? `get_key_value /etc/synoinfo.conf unique` `get_key_value /etc.defaults/synoinfo.conf unique`
Author
Owner

@sthulin commented on GitHub (Feb 27, 2023):

Did you migrate the HDDs from a J model to the 1817+ ?

Do the following also include -j after ds1817+ ?

get_key_value /etc/synoinfo.conf unique get_key_value /etc.defaults/synoinfo.conf unique

No i bought this new and put new drives in it back in 2018. I have DX517 attached to it as well if that makes a difference. Output for both of those commands are: "synology_avoton_1817+"

<!-- gh-comment-id:1445552827 --> @sthulin commented on GitHub (Feb 27, 2023): > Did you migrate the HDDs from a J model to the 1817+ ? > > Do the following also include -j after ds1817+ ? > > `get_key_value /etc/synoinfo.conf unique` `get_key_value /etc.defaults/synoinfo.conf unique` No i bought this new and put new drives in it back in 2018. I have DX517 attached to it as well if that makes a difference. Output for both of those commands are: "synology_avoton_1817+"
Author
Owner

@007revad commented on GitHub (Feb 27, 2023):

What about: cat /proc/cmdline

<!-- gh-comment-id:1445555020 --> @007revad commented on GitHub (Feb 27, 2023): What about: `cat /proc/cmdline`
Author
Owner

@sthulin commented on GitHub (Feb 27, 2023):

that also says "syno_hw_version=DS1817+" along with a bunch of other stuff

<!-- gh-comment-id:1445556101 --> @sthulin commented on GitHub (Feb 27, 2023): that also says "syno_hw_version=DS1817+" along with a bunch of other stuff
Author
Owner

@007revad commented on GitHub (Feb 27, 2023):

Very strange. I'll need to dig deeper into where cat /proc/cmdline and cat /proc/sys/kernel/syno_hw_version get the model number from.

In the meantime I'll add a check for -j at the end of the model number and remove it.

<!-- gh-comment-id:1445563709 --> @007revad commented on GitHub (Feb 27, 2023): Very strange. I'll need to dig deeper into where `cat /proc/cmdline` and `cat /proc/sys/kernel/syno_hw_version` get the model number from. In the meantime I'll add a check for -j at the end of the model number and remove it.
Author
Owner

@007revad commented on GitHub (Feb 27, 2023):

I've just updated the script with a change to remove "'-j" from the model.

<!-- gh-comment-id:1445579046 --> @007revad commented on GitHub (Feb 27, 2023): I've just updated the script with a change to remove "'-j" from the model.
Author
Owner

@sthulin commented on GitHub (Feb 27, 2023):

that worked and the script ran. It added my HDDs.

<!-- gh-comment-id:1445586175 --> @sthulin commented on GitHub (Feb 27, 2023): that worked and the script ran. It added my HDDs.
Sign in to join this conversation.
No milestone
No project
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#504
No description provided.