mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #219] why it set maxium ram to 32GB not 64GB while i have 64GB installed? #586
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#586
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 @leonpano2006 on GitHub (Jan 20, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/219
Originally assigned to: @007revad on GitHub.
@007revad commented on GitHub (Jan 20, 2024):
It should have set it to 64 GB if the setting in synoinfo.conf was set to less than 65536 MB.
To get the amount of installed memory I originally used
cat /proc/meminfobut because older versions of DSM 6 did not have /proc/meminfo I changed to using dmidecode.I just noticed this line:
but then the script uses
dmidecode -t memoryinstead ofcat /proc/meminfoThe comment should say "DSM 6 as has no dmidecode"
What does this command return?
dmidecode -t memory | grep -E "[Ss]ize: [0-9]+ [MG]{1}[B]{1}$"@leonpano2006 commented on GitHub (Jan 22, 2024):
DS:DiskStation[~]$ dmidecode -t memory | grep -E "[Ss]ize: [0-9]+ [MG]{1}[B]{1}$" /sys/firmware/dmi/tables/smbios_entry_point: Permission denied /dev/mem: Permission denied DS:DiskStation[~]$ sudo su Password: Sorry, try again. Password: DS:DiskStation[/volume1/homes/leonpano]# dmidecode -t memory | grep -E "[Ss]ize: [0-9]+ [MG]{1}[B]{1}$" Size: 1 MB Size: 1 MB@leonpano2006 commented on GitHub (Jan 22, 2024):
idk how to fix this false 1MB shit
it think 1 stick of 32GB as 1 stick 1MB
this also cause i have issue to use vm station
@007revad commented on GitHub (Jan 22, 2024):
I see why it said that. It's thinks you only have 1 MB of memory(!) so the script is saying the max_memory setting is already greater than the amount the NAS thinks is installed.
32 GB is the default max_memory setting for a DS2419+
Obviously DSM uses dmidecode to work out how much memory is installed because DSM thinks you only have 1 MB.
The specs for the DS2419+ say:
Memory 4 GB DDR4 Non-ECC SO-DIMM1 (expandable up to 32 GB with 16 GB ECC SO-DIMM x 2)Have you tried it with just 1 x 32 GB?
@leonpano2006 commented on GitHub (Jan 22, 2024):
I tried 1*32GB
then it will show 1MB total ram installed
But htop shows correct size of ram
Also neofetch
@leonpano2006 commented on GitHub (Jan 22, 2024):
And I also don't know why Intel say this cpu support up to 256GB
I wonder what device need weak cpu but large ram
@007revad commented on GitHub (Jan 22, 2024):
Yep. Intel says:
But they don't specify if memory type means dual or single rank, speed, ECC or not.
While the Intel Atom C3538 supports 256 GB the DS2429+ chipset may not support more than 32 GB total, with 16 GB per slot.
@leonpano2006 commented on GitHub (Jan 22, 2024):
If is chipset doesn't support it then I believe it won't boot up at all
And this is SoC chip(it is atom), I don't it have chipset like normal Intel CPUs
And question before just ask what is this cpu made for
But is there any fix can be done?
@leonpano2006 commented on GitHub (Jan 23, 2024):
@007revad commented on GitHub (Jul 1, 2024):
Is this still an issue in the latest version of syno_hdd_db?
@leonpano2006 commented on GitHub (Jul 3, 2024):
I will test that
@leonpano2006 commented on GitHub (Jul 18, 2024):
@leonpano2006 commented on GitHub (Jul 18, 2024):
i just try again after script update
@007revad commented on GitHub (Jul 18, 2024):
I'm sorry this has taken so long.
I just searched all the old versions and test files and found 1 from 13 months ago where I tested
cat /proc/meminfobut didn't continue with it for some reason.I'll edit the script tomorrow to use
cat /proc/meminfo | grep [Mm]em[Tt]otal. It's 11pm here so I need to go bed.@leonpano2006 commented on GitHub (Jul 18, 2024):
@leonpano2006 commented on GitHub (Jul 18, 2024):
@007revad commented on GitHub (Jul 19, 2024):
I remember why I didn't use
cat /proc/meminfo | grep 'MemTotal'. The kB values aren't KB or KiB and I don't how to convert them to MB and GB. Dividing by 1024 or 1000 does not give the correct result.code)"
On a NAS with 6GB of memory I can divide the MemTotal kB by 962.69 to get the expected 6144 MB. And divide the MemTotal kB by 985794 to get 6 GB. But dividing by 962.69 and 985794 does not give the correct results for 3GB or 32GB.
EDIT I just discovered "MemTotal: Total usable ram (i.e. physical ram minus a few reserved bits and the kernel binary."
@007revad commented on GitHub (Jul 19, 2024):
Lets try a different tactic.
If you have syno_hdd_db scheduled change the schedule so it does NOT include the -r or --ram options.
Then run these commands to set the mem_max_mb to 64 GB
@leonpano2006 commented on GitHub (Aug 16, 2024):
Latest veraion(downloaded with git clone #THIS_REPO)
@007revad commented on GitHub (Aug 16, 2024):
The fact the script got to those lines tells me that the $ramtotal variable was numeric. And since all 4 of those lines are comparing $ramtotal to $setting that would suggest that the $setting variable is the problem but 65536 is valid.
Can you download and run this test script and report back with the output:
https://github.com/007revad/Synology_HDD_db/blob/test/ramsize_213.sh
@leonpano2006 commented on GitHub (Aug 24, 2024):
@007revad commented on GitHub (Aug 25, 2024):
You downloaded the webpage instead of the file.
Download this zip file: https://github.com/007revad/Synology_HDD_db/raw/test/ramsize_213.zip then unzip it and run the ramsize_213.sh