FoxxMD

@Benson I have no such options in BIOS. I have attached pics of the memory-related features in my BIOS. Everything is set on auto or factory default. All memory is recognized. The only other piece of information I can think of is that my motherboard is a consumer board (GA-990FXA-UD3) and not advertised to work with ECC memory. However it's been confirmed by multiple forums posts I've found (and my own experience) that ECC does indeed work with it -- due to the board and cpu having a workstation heritages IE they were workstation base products that were "downgraded" to be consumer products. But I don't see how this would have any effect on my current issue since everything reports normally on BIOS and in unraid *except* that unraid won't use all 4 sticks for some reason...

Application Name: szurubooru-api Application Site: https://github.com/rr-/szurubooru Docker Hub: https://hub.docker.com/r/sgsunder/szurubooru-api Template Repo: https://github.com/FoxxMD/unraid-docker-templates Application Name: szurubooru-client Application Site: https://github.com/rr-/szurubooru Docker Hub: https://hub.docker.com/r/sgsunder/szurubooru-client Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview Szurubooru is an image board engine inspired by services such as Danbooru, Gelbooru and Moebooru dedicated for small and medium communities. It is pronounced as shoorubooru. Some features: Post content: images (JPG, PNG, GIF, animated GIF), videos (MP4, WEBM), Flash animations Ability to retrieve web video content using youtube-dl Post comments Post notes / annotations, including arbitrary polygons Rich JSON REST API Token based authentication for clients Rich search and privilege system Autocomplete in search and while editing tags Tag categories Tag suggestions Tag implications (adding a tag automatically adds another) Tag aliases Duplicate detection Post rating and favoriting; comment rating Prerequisites Postgres 11 is required for szurubooru to run. It is accessed through IP so any existing instances you have can be used. Otherwise check CA for "postgres" to find available options. How To Use Start by installing szurubooru-api. The template provides defaults for volumes and api port, you will need to: Fill in the IP endpoints for Postgres as well as user/pass/db. Optionally, if you have your own server config you can override the default production config by creating another Path entry and setting container dir to /opt/app/config.yaml, with the host dir pointing a valid file EX /mnt/user/appdata/szurubooru/config.yaml After the api is running install szurubooru-client. The template provides defaults for everything but the api endpoint. Visit your docker page or check "show docker allocations" to find the internal IP szurubooru-api is bound to. Use that as the BACKEND_HOST value. The first user created will have admin privileges. NOTE: If you are upgrading from v2.2 Elasticsearch is no longer necessary. It is recommended you backup your postgres DB and data folders before upgrading. Once you have started the new (upgraded) container do not stop/update the container until post data has been rehashed -- progress can be checked by viewing the logs. After hashing is complete you can safely remove the Elasticsearch Host variable from your unraid template and restart the the container.

Application Name: elasticsearch Application Site: https://www.elastic.co/ Docker Hub: https://hub.docker.com/_/elasticsearch Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview Elasticsearch is an open-source, RESTful, distributed search and analytics engine built on Apache Lucene. Since its release in 2010, Elasticsearch has quickly become the most popular search engine, and is commonly used for log analytics, full-text search, security intelligence, business analytics, and operational intelligence use cases. This template defaults to Elasticsearch 6.6.2. This can easily be changed by modifying the Repository field (in Advanced View) on the template to use any available tags from dockerhub. Note: I have not tested any alpine variants. How To Use You must follow these steps if using Elasticsearch 5 or above -- vm.max_map_count must be increased or this container will not work Install CA User Scripts from Community Apps Create a new script named vm.max_map_count with this contents: #!/bin/bash sysctl -w vm.max_map_count=262144 3. Set script schedule to At Startup of Array 4. Run the script now to affect changes General Instructions (all versions) Check the default exposed ports and volume mappings in the template to ensure no conflicts. Happy searching! Acknowledgements Big thanks to @Jclendineng for instructions on how to modify max_map_count for elasticsearch Thanks to @OFark for additional arguments needed to get elasticsearch running

~# dmidecode -t 17 # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x002E, DMI type 17, 34 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_Dimm0 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 800 MT/s Manufacturer: Micron Serial Number: 0E93CBB4 Asset Tag: Dimm0_AssetTag Part Number: 18KSF1G72AZ-1 Rank: 2 Configured Clock Speed: 800 MT/s Handle 0x0030, DMI type 17, 34 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_Dimm1 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 800 MT/s Manufacturer: Micron Serial Number: 0E93CBB3 Asset Tag: Dimm1_AssetTag Part Number: 18KSF1G72AZ-1 Rank: 2 Configured Clock Speed: 800 MT/s Handle 0x0032, DMI type 17, 34 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_Dimm2 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 800 MT/s Manufacturer: Micron Serial Number: 0E93CBB6 Asset Tag: Dimm2_AssetTag Part Number: 18KSF1G72AZ-1 Rank: 2 Configured Clock Speed: 800 MT/s Handle 0x0034, DMI type 17, 34 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_Dimm3 Bank Locator: Node0_Bank0 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 800 MT/s Manufacturer: Micron Serial Number: 0E93CD82 Asset Tag: Dimm3_AssetTag Part Number: 18KSF1G72AZ-1 Rank: 2 Configured Clock Speed: 800 MT/s

I have 32GB (4x8GB) of UDIMM ECC DDR3 memory installed on my server. On my dashboard under Memory Size it reports total usable as 24.068 GB I have read other threads on this forum about people with the same issue but usually the issue is a bad stick. Here is what I've determined so far (trying to rule out other threads) I can see every stick within unraid (on System Profiler in Memory Devices) Memory Summary shows a Maximum Capacity of 32 GB My motherboard supports 32GB memory I haven't found anything saying my cpu, an FX-8350, can't support 32GB memory All memory is accessible from BIOS All memory is accessible and passes all tests with memtest All sticks are the same brand/model, shouldn't be an issue with pairing for dual-channel mode I have used other sticks (not part of this 4x8GB kit) in the past with unraid, up to 20GB with random pairings, and never had an issue Removing any stick puts my total usable and installed at ~24GB It's not being consumed for video memory because I have a dedicated GeForce 210 installed I have attached a diagnostics zip file for your convenience. Does anyone have any idea why I can't use all my memory? Thanks foxxnas-diagnostics-20190401-1417.zip

Having the same problem