[GH-ISSUE #156] Total memory size is not numeric: ''

kerem commented

2026-03-07 19:15:01 +03:00

Owner

Originally created by @hirenshah on GitHub (Oct 21, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/156

Originally assigned to: @007revad on GitHub.

Just noticed this in the logs when re-running the Task Schedule to update from v3.1.64 to v3.1.65.

Searched the issues and it looks like this issue was resolved. Any ideas?

Synology_HDD_db v3.1.64
DS1813+ DSM 7.1.1-42962-6 
Using options: -nr --autoupdate=1
Running from: /volume1/web/scripts/utilities/syno_hdd_db.sh

[0;36mThere is a newer version of this script available.[0m
Current version: v3.1.64
Latest version:  v3.1.65
Downloading v3.1.65
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  408k    0  408k    0     0   480k      0 --:--:-- --:--:-- --:--:-- 1352k

v3.1.65 and changes.txt downloaded to: /volume1/web/scripts/utilities

-------------------------------------------------------------------------------
Synology_HDD_db v3.1.65
DS1813+ DSM 7.1.1-42962-6 
Using options: -nr --autoupdate=1
Running from: /volume1/web/scripts/utilities/syno_hdd_db.sh

HDD/SSD models found: 5
CT250MX500SSD1,M3CR023
CT250MX500SSD1,M3CR045
WD30EFRX-68AX9N0,80.00A80
WD30EFRX-68EUZN0,80.00A80
WD30EFRX-68EUZN0,82.00A82

No M.2 drives found

No M.2 PCIe cards found

No Expansion Units found

Updated [0;33mCT250MX500SSD1[0m to [0;36mds1813+_host_v7.db[0m
[0;33mCT250MX500SSD1[0m already exists in [0;36mds1813+_host.db[0m
[0;33mCT250MX500SSD1[0m already exists in [0;36mds1813+_host.db.new[0m
Updated [0;33mCT250MX500SSD1[0m to [0;36mds1813+_host_v7.db.new[0m
Updated [0;33mCT250MX500SSD1[0m to [0;36mds1813+_host_v7.db[0m
[0;33mCT250MX500SSD1[0m already exists in [0;36mds1813+_host.db[0m
[0;33mCT250MX500SSD1[0m already exists in [0;36mds1813+_host.db.new[0m
Updated [0;33mCT250MX500SSD1[0m to [0;36mds1813+_host_v7.db.new[0m
[0;33mWD30EFRX-68AX9N0[0m already exists in [0;36mds1813+_host_v7.db[0m
[0;33mWD30EFRX-68AX9N0[0m already exists in [0;36mds1813+_host.db[0m
[0;33mWD30EFRX-68AX9N0[0m already exists in [0;36mds1813+_host.db.new[0m
[0;33mWD30EFRX-68AX9N0[0m already exists in [0;36mds1813+_host_v7.db.new[0m
Updated [0;33mWD30EFRX-68EUZN0[0m to [0;36mds1813+_host_v7.db[0m
[0;33mWD30EFRX-68EUZN0[0m already exists in [0;36mds1813+_host.db[0m
[0;33mWD30EFRX-68EUZN0[0m already exists in [0;36mds1813+_host.db.new[0m
Updated [0;33mWD30EFRX-68EUZN0[0m to [0;36mds1813+_host_v7.db.new[0m
Updated [0;33mWD30EFRX-68EUZN0[0m to [0;36mds1813+_host_v7.db[0m
[0;33mWD30EFRX-68EUZN0[0m already exists in [0;36mds1813+_host.db[0m
[0;33mWD30EFRX-68EUZN0[0m already exists in [0;36mds1813+_host.db.new[0m
Updated [0;33mWD30EFRX-68EUZN0[0m to [0;36mds1813+_host_v7.db.new[0m

Support disk compatibility already enabled.

[41mERROR[0m Total memory size is not numeric: ''

Drive db auto updates already disabled.

DSM successfully checked disk compatibility.

You may need to [0;36mreboot the Synology[0m to see the changes.

Originally created by @hirenshah on GitHub (Oct 21, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/156 Originally assigned to: @007revad on GitHub. Just noticed this in the logs when re-running the Task Schedule to update from v3.1.64 to v3.1.65. Searched the issues and it looks like this issue was resolved. Any ideas? ``` Synology_HDD_db v3.1.64 DS1813+ DSM 7.1.1-42962-6 Using options: -nr --autoupdate=1 Running from: /volume1/web/scripts/utilities/syno_hdd_db.sh [0;36mThere is a newer version of this script available.[0m Current version: v3.1.64 Latest version: v3.1.65 Downloading v3.1.65 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 408k 0 408k 0 0 480k 0 --:--:-- --:--:-- --:--:-- 1352k v3.1.65 and changes.txt downloaded to: /volume1/web/scripts/utilities ------------------------------------------------------------------------------- Synology_HDD_db v3.1.65 DS1813+ DSM 7.1.1-42962-6 Using options: -nr --autoupdate=1 Running from: /volume1/web/scripts/utilities/syno_hdd_db.sh HDD/SSD models found: 5 CT250MX500SSD1,M3CR023 CT250MX500SSD1,M3CR045 WD30EFRX-68AX9N0,80.00A80 WD30EFRX-68EUZN0,80.00A80 WD30EFRX-68EUZN0,82.00A82 No M.2 drives found No M.2 PCIe cards found No Expansion Units found Updated [0;33mCT250MX500SSD1[0m to [0;36mds1813+_host_v7.db[0m [0;33mCT250MX500SSD1[0m already exists in [0;36mds1813+_host.db[0m [0;33mCT250MX500SSD1[0m already exists in [0;36mds1813+_host.db.new[0m Updated [0;33mCT250MX500SSD1[0m to [0;36mds1813+_host_v7.db.new[0m Updated [0;33mCT250MX500SSD1[0m to [0;36mds1813+_host_v7.db[0m [0;33mCT250MX500SSD1[0m already exists in [0;36mds1813+_host.db[0m [0;33mCT250MX500SSD1[0m already exists in [0;36mds1813+_host.db.new[0m Updated [0;33mCT250MX500SSD1[0m to [0;36mds1813+_host_v7.db.new[0m [0;33mWD30EFRX-68AX9N0[0m already exists in [0;36mds1813+_host_v7.db[0m [0;33mWD30EFRX-68AX9N0[0m already exists in [0;36mds1813+_host.db[0m [0;33mWD30EFRX-68AX9N0[0m already exists in [0;36mds1813+_host.db.new[0m [0;33mWD30EFRX-68AX9N0[0m already exists in [0;36mds1813+_host_v7.db.new[0m Updated [0;33mWD30EFRX-68EUZN0[0m to [0;36mds1813+_host_v7.db[0m [0;33mWD30EFRX-68EUZN0[0m already exists in [0;36mds1813+_host.db[0m [0;33mWD30EFRX-68EUZN0[0m already exists in [0;36mds1813+_host.db.new[0m Updated [0;33mWD30EFRX-68EUZN0[0m to [0;36mds1813+_host_v7.db.new[0m Updated [0;33mWD30EFRX-68EUZN0[0m to [0;36mds1813+_host_v7.db[0m [0;33mWD30EFRX-68EUZN0[0m already exists in [0;36mds1813+_host.db[0m [0;33mWD30EFRX-68EUZN0[0m already exists in [0;36mds1813+_host.db.new[0m Updated [0;33mWD30EFRX-68EUZN0[0m to [0;36mds1813+_host_v7.db.new[0m Support disk compatibility already enabled. [41mERROR[0m Total memory size is not numeric: '' Drive db auto updates already disabled. DSM successfully checked disk compatibility. You may need to [0;36mreboot the Synology[0m to see the changes. ```

kerem

2026-03-07 19:15:01 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-07 19:15:02 +03:00

Author

Owner

@007revad commented on GitHub (Oct 24, 2023):

I replied to this 3 days ago but my reply is missing!?!?!

If you run syno_hdd_db with the -e or --email option you won't get all those �[0;33 �[41m �[0m in the email from task scheduler.

What does the following command return?
dmidecode -t memory | grep -E "[Ss]ize: [0-9]+ [MG]{1}[B]{1}$"

@007revad commented on GitHub (Oct 24, 2023): I replied to this 3 days ago but my reply is missing!?!?! If you run syno_hdd_db with the -e or --email option you won't get all those �[0;33 �[41m �[0m in the email from task scheduler. What does the following command return? `dmidecode -t memory | grep -E "[Ss]ize: [0-9]+ [MG]{1}[B]{1}$"`

kerem commented

2026-03-07 19:15:02 +03:00

Author

Owner

@hirenshah commented on GitHub (Oct 26, 2023):

@hirenshah commented on GitHub (Oct 26, 2023): ![image](https://github.com/007revad/Synology_HDD_db/assets/418112/5f9728dc-2648-4a4d-93ec-d74a963bb61b)

kerem commented

2026-03-07 19:15:02 +03:00

Author

Owner

@hirenshah commented on GitHub (Oct 26, 2023):

Without the grep:

@hirenshah commented on GitHub (Oct 26, 2023): Without the grep: ![image](https://github.com/007revad/Synology_HDD_db/assets/418112/d5464f90-fcd4-43d0-8313-edfc4f7cb0c4)

kerem commented

2026-03-07 19:15:02 +03:00

Author

Owner

@007revad commented on GitHub (Oct 26, 2023):

Interesting.

I know DSM 6 does not have dmidecode, but your DS1813+ is using DSM 7.1.1. Your dmidecode is the same version that's in DSM 7.2

But I notice the SMBIOS is different which is probably model dependant rather than DSM version dependant:

It's SMBIOS 2.6 on your DS1813+
It's SMBIOS 3.01 on my DS720+
It's SMBIOS 3.1.1 on my DS1821+

Have you upgraded the amount of memory in the DS1813+ to more than 4GB (2 x 2GB) ?

@007revad commented on GitHub (Oct 26, 2023): Interesting. I know DSM 6 does not have dmidecode, but your DS1813+ is using DSM 7.1.1. Your dmidecode is the same version that's in DSM 7.2 But I notice the SMBIOS is different which is probably model dependant rather than DSM version dependant: - It's SMBIOS 2.6 on your DS1813+ - It's SMBIOS 3.01 on my DS720+ - It's SMBIOS 3.1.1 on my DS1821+ Have you upgraded the amount of memory in the DS1813+ to more than 4GB (2 x 2GB) ?

kerem commented

2026-03-07 19:15:02 +03:00

Author

Owner

@hirenshah commented on GitHub (Oct 27, 2023):

I upgraded the RAM from 2GB to 4GB a couple of years ago.

@hirenshah commented on GitHub (Oct 27, 2023): I upgraded the RAM from 2GB to 4GB a couple of years ago.

kerem commented

2026-03-07 19:15:02 +03:00

Author

Owner

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

The DS1813+ already supports 4GB of memory.

This command should return 4096
get_key_value /etc.defaults/synoinfo.conf mem_max_mb

If it does, you don't the -r option when running syno_hdd-db.

@007revad commented on GitHub (Oct 27, 2023): The DS1813+ already supports 4GB of memory. This command should return 4096 `get_key_value /etc.defaults/synoinfo.conf mem_max_mb` If it does, you don't the -r option when running syno_hdd-db.

kerem commented

2026-03-07 19:15:02 +03:00

Author

Owner

@hirenshah commented on GitHub (Oct 27, 2023):

It does indeed return 4096, so I've now changed the task to:
/volume1/web/scripts/utilities/syno_hdd_db.sh -n --autoupdate=1

@hirenshah commented on GitHub (Oct 27, 2023): It does indeed return 4096, so I've now changed the task to: `/volume1/web/scripts/utilities/syno_hdd_db.sh -n --autoupdate=1`

kerem referenced this issue

2026-03-07 19:17:23 +03:00

[PR #67] [MERGED] Develop #253

kerem referenced this issue

2026-03-12 17:41:06 +03:00

[PR #67] [MERGED] Develop #912

Rows
Columns

[GH-ISSUE #156] Total memory size is not numeric: '' #67