December 21, 20196 yr Hi! I have installed unRAID on a server based on a chinese motherboard form huananzhi (x79 8d) with two xeon e5 2670 CPU:s and 64GB of ECC DDR3 memory. I really like the simplicity of unRAID so far and I am running several fun apps 😃 Now to my problem. The system information page and "dashboard" only shows 32GB of RAM, even though I see all 64GB in BIOS and when I execute "top" and "free" commands in the console. I can also allocate up to 64GB of RAM when creating a VM. root@Monsterservern:~# free total used free shared buff/cache available Mem: 65900588 3426488 58066292 615880 4407808 61168248 Swap: 0 0 0 See the attached images for dashboard and BIOS. I think that the BIOS in my huananzhi motherboard is a bit strange. It looks like it shows a lot more DIMM slots than are actually physically on the board (8 slots). See attached image. Perhaps this is the reason that unRAID does not include all RAM in the system information? This is not a huge issue, but a bit annoying to me as a perfectionist 😃 Also the system information only shows one CPU even though there are two of them, the dashboard shows all 16 threads / 32 cores accurately however. Is there a way to make unraid detect all my RAM in the system information? Thank you! /Erik
December 21, 20196 yr 58 minutes ago, eribob said: Is there a way to make unraid detect all my RAM in the system information? Unraid relies on what your BIOS is reporting.
December 21, 20196 yr Author 23 minutes ago, bonienl said: Unraid relies on what your BIOS is reporting. Ok, so why is not all RAM detected then? My BIOS reports 64GB.
December 22, 20196 yr Author Hi! Here is the output. Only half of the RAM sticks seem to be there. Also the last line that says that the "DMI table is broken" is interesting. Is that a BIOS issue? Getting SMBIOS data from sysfs. SMBIOS 2.8 present. Handle 0x002E, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: Node0_Dimm0 Bank Locator: Node0_Bank0 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: Dimm0_Manufacturer Serial Number: Dimm0_SerNum Asset Tag: Dimm0_AssetTag Part Number: Dimm0_PartNum Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0030, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: Node0_Dimm1 Bank Locator: Node0_Bank0 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: Dimm1_Manufacturer Serial Number: Dimm1_SerNum Asset Tag: Dimm1_AssetTag Part Number: Dimm1_PartNum Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0032, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: Node0_Dimm2 Bank Locator: Node0_Bank0 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: Dimm2_Manufacturer Serial Number: Dimm2_SerNum Asset Tag: Dimm2_AssetTag Part Number: Dimm2_PartNum Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0034, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: Node0_Dimm3 Bank Locator: Node0_Bank0 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: Dimm3_Manufacturer Serial Number: Dimm3_SerNum Asset Tag: Dimm3_AssetTag Part Number: Dimm3_PartNum Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0036, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: Node0_Dimm4 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Registered (Buffered) Speed: 1333 MT/s Manufacturer: SK Hynix Serial Number: 40354E13 Asset Tag: Dimm4_AssetTag Part Number: HMT31GR7EFR4A Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0038, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: Node0_Dimm5 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Registered (Buffered) Speed: 1333 MT/s Manufacturer: SK Hynix Serial Number: 40C54E0E Asset Tag: Dimm5_AssetTag Part Number: HMT31GR7EFR4A Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x003A, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: Node0_Dimm6 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Registered (Buffered) Speed: 1333 MT/s Manufacturer: SK Hynix Serial Number: 40254E10 Asset Tag: Dimm6_AssetTag Part Number: HMT31GR7EFR4A Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x003C, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: Node0_Dimm7 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Registered (Buffered) Speed: 1333 MT/s Manufacturer: SK Hynix Serial Number: 40254E09 Asset Tag: Dimm7_AssetTag Part Number: HMT31GR7EFR4A Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Invalid entry length (0). DMI table is broken! Stop.
December 22, 20196 yr 5 minutes ago, eribob said: Is that a BIOS issue? Yes, that looks like a BIOS problem. Perhaps a newer BIOS version is available for your motherboard?
December 22, 20196 yr Author Thanks, Unfortunately the support from huananzhi is not super... I have been googling a lot but I cant find a bios for the board. Is it possible to verify if the DMI table is indeed broken?
December 22, 20196 yr 22 minutes ago, eribob said: Is it possible to verify if the DMI table is indeed broken? Maybe the syslog gives some clues.
December 22, 20196 yr Author Here is my log (is this the one you meant?) Dec 22 10:58:20 Monsterservern kernel: vfio-pci 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Dec 22 10:58:24 Monsterservern kernel: vfio-pci 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Dec 22 10:58:24 Monsterservern kernel: br0: port 3(vnet1) entered blocking state Dec 22 10:58:24 Monsterservern kernel: br0: port 3(vnet1) entered disabled state Dec 22 10:58:24 Monsterservern kernel: device vnet1 entered promiscuous mode Dec 22 10:58:24 Monsterservern kernel: br0: port 3(vnet1) entered blocking state Dec 22 10:58:24 Monsterservern kernel: br0: port 3(vnet1) entered forwarding state Dec 22 10:58:25 Monsterservern avahi-daemon[4195]: Joining mDNS multicast group on interface vnet1.IPv6 with address fe80::fc54:ff:fe9b:403b. Dec 22 10:58:25 Monsterservern avahi-daemon[4195]: New relevant interface vnet1.IPv6 for mDNS. Dec 22 10:58:25 Monsterservern avahi-daemon[4195]: Registering new address record for fe80::fc54:ff:fe9b:403b on vnet1.*. Dec 22 10:58:37 Monsterservern acpid: input device has been disconnected, fd 4 Dec 22 10:58:37 Monsterservern acpid: input device has been disconnected, fd 5 Dec 22 10:58:37 Monsterservern acpid: input device has been disconnected, fd 6 Dec 22 10:58:37 Monsterservern acpid: input device has been disconnected, fd 7 Dec 22 10:58:38 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:38 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:38 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:39 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:42 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:43 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:43 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:43 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:54 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:54 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:54 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:54 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:55 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:56 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:56 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:56 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:57 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:57 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 10:58:57 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 10:58:57 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 11:37:35 Monsterservern login[11652]: ROOT LOGIN on '/dev/pts/2' Dec 22 11:49:23 Monsterservern kernel: usb 2-1.6: reset full-speed USB device number 3 using ehci-pci Dec 22 11:49:24 Monsterservern kernel: usb 1-1.2: reset full-speed USB device number 4 using ehci-pci Dec 22 12:25:51 Monsterservern login[14402]: ROOT LOGIN on '/dev/pts/2'
January 23, 20206 yr On 12/21/2019 at 10:16 PM, eribob said: Hi! I have installed unRAID on a server based on a chinese motherboard form huananzhi (x79 8d) with two xeon e5 2670 CPU:s and 64GB of ECC DDR3 memory. I really like the simplicity of unRAID so far and I am running several fun apps 😃 Now to my problem. The system information page and "dashboard" only shows 32GB of RAM, even though I see all 64GB in BIOS and when I execute "top" and "free" commands in the console. I can also allocate up to 64GB of RAM when creating a VM. root@Monsterservern:~# free total used free shared buff/cache available Mem: 65900588 3426488 58066292 615880 4407808 61168248 Swap: 0 0 0 See the attached images for dashboard and BIOS. I think that the BIOS in my huananzhi motherboard is a bit strange. It looks like it shows a lot more DIMM slots than are actually physically on the board (8 slots). See attached image. Perhaps this is the reason that unRAID does not include all RAM in the system information? This is not a huge issue, but a bit annoying to me as a perfectionist 😃 Also the system information only shows one CPU even though there are two of them, the dashboard shows all 16 threads / 32 cores accurately however. Is there a way to make unraid detect all my RAM in the system information? Thank you! /Erik Are you able to resolve the issue, for me its showing only 16Gb, Where as actual installed ram in 64 GB. Bios shows 64 GB Ram installed. But Unraid is shoiwing 16GB Only
January 24, 20206 yr Author Hi! i have not resolved the issue unfortunately. Any suggestions would be much appreciated. I am thinking of switching to a supermicro motherboard instead but it is a lot of work and some money as well so I am hesitant.
Archived
This topic is now archived and is closed to further replies.