mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #93] ERROR Memory size is not numeric: 'No' #540
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#540
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 @phillipmcmahon on GitHub (Jun 21, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/93
Running the latest script with -nr flags. I get the following output error
$ sudo dmidecode -t memory | grep "[Ss]ize" Size: 8192 MB Size: No Module Installed Size: 16384 MB Size: No Module InstalledHuge thanks for this script btw, it's an essential!
@007revad commented on GitHub (Jun 22, 2023):
Thank you.
Since DSM 7.2 was released, different Synology models' output different information for dmidecode -t memory. I don't know why, and it's not the actual dmidecode binary that's different. I just ran the DS1621xs+ dmidecode binary on a DS720+ with an empty memory slot and it didn't return "No Module Installed" for the empty slot.
I've disabled the warning for non-numeric values - as the script skips them anyway, and will show an error if the total memory size is non-numeric.
I also noticed the script didn't show the current max memory setting.
I've fixed both issues in https://github.com/007revad/Synology_HDD_db/releases/tag/v3.0.56 or you can run v3.0.55 again and let it update itself to 3.0.56
@phillipmcmahon commented on GitHub (Jun 22, 2023):
Thanks so much!