Jump to content
eribob

Unraid does not correctly display my RAM

8 posts in this topic Last Reply

Recommended Posts

Hi! 

I have posted about this before, but I did not get an answer and I have found some more information. 

I have a Huananzhi x79 8D motherboard with 8x8GB of DDR3 ECC memory and 2 x Xeon E5 2670 CPU:s. 

 

The unraid dashboard lists my RAM to be 32GB (instead of 64GB). The system information as well: 

Model: Custom
M/B: HUANANZHI X79-8D Version VAA31 - s/n: MB-201903272019
BIOS: American Megatrends Inc. Version 4.6.5. Dated: 03/28/2019
CPU: Intel® Xeon® CPU E5-2670 0 @ 2.60GHz
HVM: Enabled
IOMMU: Enabled
Cache: 512 KiB, 2048 KiB, 20480 KiB, 512 KiB, 2048 KiB, 20480 KiB
Memory: 32 GiB DDR3 Multi-bit ECC (max. installable capacity 192 GiB)
Network: bond0: fault-tolerance (active-backup), mtu 1500
 eth0: 1000 Mbps, full duplex, mtu 1500
 eth1: interface down
Kernel: Linux 4.19.88-Unraid x86_64
OpenSSL: 1.1.1d
Uptime: 

The "free" command gives me 64GB of RAM: 

              total        used        free      shared  buff/cache   available
Mem:       65966588    19896080     4611780      696308    41458728    44772192
Swap:             0           0           0

 

lshw -short

Also shows 8 sticks of 8GB RAM: 

/W path         Device       Class       Description
=====================================================
                              system      To be filled by O.E.M. (To be filled by O.E.M.)
/0                            bus         X79-8D
/0/0                          memory      64KiB BIOS
/0/1                          processor   Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz
/0/1/5                        memory      512KiB L1 cache
/0/1/6                        memory      2MiB L2 cache
/0/1/7                        memory      20MiB L3 cache
/0/2                          processor   Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz
/0/2/9                        memory      512KiB L1 cache
/0/2/a                        memory      2MiB L2 cache
/0/2/b                        memory      20MiB L3 cache
/0/2c                         memory      System Memory
/0/2c/0                       memory      DIMM Synchronous [empty]
/0/2c/1                       memory      DIMM Synchronous [empty]
/0/2c/2                       memory      DIMM Synchronous [empty]
/0/2c/3                       memory      DIMM Synchronous [empty]
/0/2c/4                       memory      8GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/2c/5                       memory      8GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/2c/6                       memory      8GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/2c/7                       memory      8GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/3e                         memory      System Memory
/0/3e/0                       memory      8GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/3e/1                       memory      8GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/3e/2                       memory      8GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/3e/3                       memory      8GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/3e/4                       memory      DIMM Synchronous [empty]
/0/3e/5                       memory      DIMM Synchronous [empty]
/0/3e/6                       memory      DIMM Synchronous [empty]
/0/3e/7                       memory      DIMM Synchronous [empty]
/0/4                          memory      1023KiB BIOS
/0/6                          memory      1023KiB BIOS
/0/7                          memory      1023KiB BIOS
/0/9                          memory      1023KiB BIOS
/0/a                          memory      1023KiB BIOS
/0/b                          memory      1023KiB BIOS
/0/c                          memory      1023KiB BIOS
/0/d                          memory      1023KiB BIOS
/0/237e                       memory      1MiB BIOS
/0/e                          memory      
/0/f                          memory      

Attaching diagnostics and complete lshw output as a text file. 

 

Thank you for any assistance! 

 

monsterservern-diagnostics-20200114-2239.zip lshw-output.txt

Share this post


Link to post

Hi there,

 

I've passed this along to the devs to take a look.  I'm guessing that this is only an appearance issue and that nothing functionally is broken (e.g. you can still assign more than 32GB of RAM to VMs and whatnot).  Please confirm.

Share this post


Link to post

I've gone ahead and copied this into our bug reports forum for stable releases.  I've listed it under the category of "annoyance" as it doesn't seem to affect functionality, but obviously isn't reporting the correct data.  Further commenting on this should be done over there:

 

 

Share this post


Link to post

OK, thank you. It seems like it would be easy to fix, related to how Unraid processes the system information? 

Share this post


Link to post

Unraid relies on the information given by the BIOS of your motherboard.

 

Check if there is any newer BIOS available.

Share this post


Link to post

Hi! 

I have done some more digging. The problem seems to be with dmidecode, the command that the unraid GUI uses to fetch system information. When I run dmidecode manually I get some output and in the end the following error: 

 

Invalid entry length (0). DMI table is broken! Stop

 

Is there a way to fix the DMI table? Only through BIOS update? 

 

Thank you! 

/Erik

Share this post


Link to post
53 minutes ago, eribob said:

Only through BIOS update?

^^this

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.