mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #405] Still getting Detected non-Synology recommended memory module configurations after running script #143
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#143
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 @crazyazz on GitHub (Dec 25, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/405
Still can't get rid of , even with it disabled via the script. Any ideas?
Detected non-Synology recommended memory module configurations. You may have
Please select authentic Synology memory modules for better system reliability.
@007revad commented on GitHub (Dec 25, 2024):
Did you run the script with the -r or --ram option?
@crazyazz commented on GitHub (Dec 25, 2024):
Hi , ran as this:
sudo ./syno_hdd_db.sh -nr
Using options: -nr
Running from: /volume1/homes/XXXXX/Synology_HDD_db-main/syno_hdd_db.sh
HDD/SSD models found: 2
ST4000VN000-1H4168,SC44,4000 GB
WD30PURZ-85AKKY0,80.00B80,3000 GB
No M.2 drives found
No M.2 PCIe cards found
No Expansion Units found
ERROR Unknown database type ds3622xs+_host_v7.db!
ERROR Unknown database type dva3221_host_v7.db!
ST4000VN000-1H4168 already exists in dva3221_host_v7.db.new
ERROR Unknown database type ds3622xs+_host_v7.db!
ERROR Unknown database type dva3221_host_v7.db!
WD30PURZ-85AKKY0 already exists in dva3221_host_v7.db.new
Re-enabled support disk compatibility.
Support memory compatibility already disabled.
Max memory is set to 32 GB.
Drive db auto updates already disabled.
DSM successfully checked disk compatibility.
You may need to reboot the Synology to see the changes.
@007revad commented on GitHub (Dec 27, 2024):
This is a bigger concern than the incompatible memory.
What Synology (xpe) model is it? Which DSM version?
What do these commands return:
And these commands:
And these:
@gglanzer commented on GitHub (Mar 17, 2025):
Here is the same, pls help us:
which syno_mem_check
/usr/syno/bin/syno_mem_check
@bennytheshap commented on GitHub (Dec 10, 2025):
Seeing same issue here when run with
-nr@007revad commented on GitHub (Dec 11, 2025):
Please try version 3.6.113
https://github.com/007revad/Synology_HDD_db/releases
@bennytheshap commented on GitHub (Dec 30, 2025):
@007revad still getting this error with 3.6.116 on DSM 7.3.1-86003-1
Using
/usr/syno/bin/syno_mem_checkNeither invocation of
synogetkeyvaluemakes any output.@007revad commented on GitHub (Dec 30, 2025):
Which Synology model?
@bennytheshap commented on GitHub (Dec 31, 2025):
@007revad DS1618+
@007revad commented on GitHub (Dec 31, 2025):
Strange that a DS1618+ is giving you non-Synology memory warnings. Normally it's only business and enterprise models.
What does the following command return?
And this one?
I'm not sure what support_memory_limitation does. I suspect it limits the maximum amount of memory.
Can you try this:
Then reboot.
If that didn't work can you tell me what this returns?
@007revad commented on GitHub (Dec 31, 2025):
Also what does this command return?
@007revad commented on GitHub (Jan 2, 2026):
@bennytheshap
???