May 1, 201610 yr Just recently installed 64GB of RAM to this new system. Dashboard states that allocated is 32GB whereas installed is 64GB. See below: Clicking "Info" on the top right hand corner results in the below: Running dmidecode -t 17 result in the below: Any thoughts? Thanks!
May 1, 201610 yr The dashboard might be reporting incorrectly, since the system information says you have 64 GiB installed. What is the output of the free command? Post your diagnostics zip file.
May 1, 201610 yr Author The dashboard might be reporting incorrectly, since the system information says you have 64 GiB installed. What is the output of the free command? Post your diagnostics zip file. unraid-diagnostics-20160501-1008.zip
May 1, 201610 yr Well, free shows a total of 32GiB and that agrees with what the system recognises at boot time: May 1 02:20:34 unRAID kernel: Memory: 32864256K/33518356K available (6120K kernel code, 627K rwdata, 2004K rodata, 916K init, 592K bss, 654100K reserved, 0K cma-reserved) (from your syslog). So I don't understand why the Info window shows 64 GiB, even though that's what you actually have fitted! I take it that there are eight sockets on the motherboard and each has an 8 GiB DIMM fitted. Is the make and part number of the RAM on the qualified list for that board?
May 2, 201610 yr Author Well, free shows a total of 32GiB and that agrees with what the system recognises at boot time: May 1 02:20:34 unRAID kernel: Memory: 32864256K/33518356K available (6120K kernel code, 627K rwdata, 2004K rodata, 916K init, 592K bss, 654100K reserved, 0K cma-reserved) (from your syslog). So I don't understand why the Info window shows 64 GiB, even though that's what you actually have fitted! I take it that there are eight sockets on the motherboard and each has an 8 GiB DIMM fitted. Is the make and part number of the RAM on the qualified list for that board? That's correct, 8x8GB. The ram was not on the qualified list. I didn't think it would be such a big issue. All sticks are the same model number so if the first four work, why wouldn't the next four. After further invsetigation, in BIOs, it's being recognized as 32GB as well. So perhaps the issue isn't so much the software as it is the recognition of it at a hardware level. Thanks for your efforts though! I'll have to look into it some more.
May 2, 201610 yr One thing that might be worth testing. Take the four DIMMs out of the blue sockets. Does the BIOS correctly detect 32 GiB? Now fill up the blue sockets and empty the black ones. Does it detect the other 32 GiB? I've known four-socket motherboards to be happy with two DIMMs but not four. Timings might be off or loadings too high.
May 2, 201610 yr Check the bios and see if it lists all 8 sticks of ram Could half your ram be dedicated to something else like shared memory for graphics? Because unraid seems to recognize the installed ram correctly, it's just that half of it is not available I have the same board with 8x8GB ram. Unraid dashboard shows 65 thousand something as installed and 64 thousand something allocated
May 2, 201610 yr Author One thing that might be worth testing. Take the four DIMMs out of the blue sockets. Does the BIOS correctly detect 32 GiB? Now fill up the blue sockets and empty the black ones. Does it detect the other 32 GiB? I've known four-socket motherboards to be happy with two DIMMs but not four. Timings might be off or loadings too high. I will look into this. Check the bios and see if it lists all 8 sticks of ram Could half your ram be dedicated to something else like shared memory for graphics? Because unraid seems to recognize the installed ram correctly, it's just that half of it is not available I have the same board with 8x8GB ram. Unraid dashboard shows 65 thousand something as installed and 64 thousand something allocated I was tinkering around with the RAM settings in the bios. If you ever power down your server, could you tell me your settings?
August 25, 20178 yr hi guys, i have the same issue, not sure if the above solved the problem, but here are my specs unraid 6.3.2 free total used free shared buff/cache available Mem: 8071464 5950368 1177376 504988 943720 1111740 Swap: 0 0 0 dmidecode -t 17 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0012, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: A1_DIMM0 Bank Locator: A1_BANK0 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum0 Part Number: F3-1866C10-8GSR Rank: 2 Configured Clock Speed: 667 MHz Handle 0x0014, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: Unknown Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: A1_DIMM1 Bank Locator: A1_BANK1 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: A1_Manufacturer1 Serial Number: A1_SerNum1 Asset Tag: A1_AssetTagNum1 Part Number: Array1_PartNumber1 Rank: Unknown Configured Clock Speed: Unknown Handle 0x0016, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: A1_DIMM2 Bank Locator: A1_BANK2 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum2 Part Number: F3-1866C10-8GSR Rank: 2 Configured Clock Speed: 667 MHz Handle 0x0018, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: A1_DIMM3 Bank Locator: A1_BANK3 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum3 Part Number: F3-14900CL9-4GBXL Rank: 2 Configured Clock Speed: 667 MHz
Archived
This topic is now archived and is closed to further replies.