satmeiler

Hey guys, A couple of months ago I built a dual CPU system with a Supermicro X10 motherboard. Since I built the system only half of the memory has been usable and I quickly accepted that and moved on. Recently as I've become more experienced with unRaid I realized that NUMA 0 only had 2GB of memory. So the slots on CPU 1 are where the issue exists. When moving modules between slots the ram on CPU 0 was not usable while all the ram on CPU 1 is. Windows 10 also only sees about half of the memory 49/96GB when the RAM is installed in the correct slots. I have 6 DIMMs using 6/8 slots and all of them work when in CPU 1 slots. All of the memory has always been detected in the BIOS. I swapped the CPUs between slots and the issue was still present with CPU0 DIMMs. I also checked for bent pins and did not see any. I have not had any stability issues over the last two months. I have spent hours today searching for and trying to figure out this problem to no avail. At this point I feel like the RAM is being reserved for some reason or my motherboard is faulty. The motherboard is a Supermicro X10DAL-i. I will post the results of some diagnostic commands that I used to narrow this down. Any ideas are appreciated. Thank you. # numactl --hardware available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 28 29 30 31 32 33 34 35 36 37 38 39 40 41 node 0 size: 1869 MB node 0 free: 10 MB node 1 cpus: 14 15 16 17 18 19 20 21 22 23 24 25 26 27 42 43 44 45 46 47 48 49 50 51 52 53 54 55 node 1 size: 48378 MB node 1 free: 9856 MB node distances: node 0 1 0: 10 21 1: 21 10 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 3.0 present. Handle 0x0026, DMI type 17, 40 bytes Memory Device Array Handle: 0x0025 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: P1-DIMMA1 Bank Locator: P0_Node0_Channel0_Dimm0 Type: DDR4 Type Detail: Synchronous Speed: 2133 MT/s Manufacturer: Samsung Serial Number: 40152481 Asset Tag: P1-DIMMA1_AssetTag (date:15/09) Part Number: M393A2G40DB0-CPB Rank: 2 Configured Memory Speed: 2133 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0027, DMI type 17, 40 bytes Memory Device Array Handle: 0x0025 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: P1-DIMMB1 Bank Locator: P0_Node0_Channel1_Dimm0 Type: DDR4 Type Detail: Synchronous Speed: 2133 MT/s Manufacturer: Samsung Serial Number: 401524A7 Asset Tag: P1-DIMMB1_AssetTag (date:15/09) Part Number: M393A2G40DB0-CPB Rank: 2 Configured Memory Speed: 2133 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0029, DMI type 17, 40 bytes Memory Device Array Handle: 0x0028 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: P1-DIMMC1 Bank Locator: P0_Node0_Channel2_Dimm0 Type: DDR4 Type Detail: Synchronous Speed: 2133 MT/s Manufacturer: Samsung Serial Number: 41755E2E Asset Tag: P1-DIMMC1_AssetTag (date:15/41) Part Number: M393A2G40DB0-CPB Rank: 2 Configured Memory Speed: 2133 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x002A, DMI type 17, 40 bytes Memory Device Array Handle: 0x0028 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: P1-DIMMD1 Bank Locator: P0_Node0_Channel3_Dimm0 Type: DDR4 Type Detail: Synchronous Speed: Unknown Manufacturer: NO DIMM Serial Number: NO DIMM Asset Tag: NO DIMM Part Number: NO DIMM Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x002C, DMI type 17, 40 bytes Memory Device Array Handle: 0x002B Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: P2-DIMME1 Bank Locator: P1_Node1_Channel0_Dimm0 Type: DDR4 Type Detail: Synchronous Speed: 2133 MT/s Manufacturer: Samsung Serial Number: 3138105A Asset Tag: P2-DIMME1_AssetTag (date:16/01) Part Number: M393A2G40DB0-CPB Rank: 2 Configured Memory Speed: 2133 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x002D, DMI type 17, 40 bytes Memory Device Array Handle: 0x002B Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: P2-DIMMF1 Bank Locator: P1_Node1_Channel1_Dimm0 Type: DDR4 Type Detail: Synchronous Speed: 2133 MT/s Manufacturer: Samsung Serial Number: 31380E6E Asset Tag: P2-DIMMF1_AssetTag (date:16/01) Part Number: M393A2G40DB0-CPB Rank: 2 Configured Memory Speed: 2133 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x002F, DMI type 17, 40 bytes Memory Device Array Handle: 0x002E Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: P2-DIMMG1 Bank Locator: P1_Node1_Channel2_Dimm0 Type: DDR4 Type Detail: Synchronous Speed: 2133 MT/s Manufacturer: Samsung Serial Number: 4175B7C4 Asset Tag: P2-DIMMG1_AssetTag (date:15/41) Part Number: M393A2G40DB0-CPB Rank: 2 Configured Memory Speed: 2133 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown Handle 0x0030, DMI type 17, 40 bytes Memory Device Array Handle: 0x002E Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: P2-DIMMH1 Bank Locator: P1_Node1_Channel3_Dimm0 Type: DDR4 Type Detail: Synchronous Speed: Unknown Manufacturer: NO DIMM Serial Number: NO DIMM Asset Tag: NO DIMM Part Number: NO DIMM Rank: Unknown Configured Memory Speed: Unknown Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: Unknown # numastat qemu Per-node process memory usage (in MBs) for PID 31873 (qemu-system-x86) Node 0 Node 1 Total --------------- --------------- --------------- Huge 0.00 0.00 0.00 Heap 0.02 0.04 0.05 Stack 0.01 0.02 0.04 Private 63.94 20674.24 20738.18 ---------------- --------------- --------------- --------------- Total 63.97 20674.30 20738.27 syslog.txt

There are 4 identical sticks (SAMSUNG 16GB 288-Pin DDR4 SDRAM ECC Registered DDR4 2133 (PC4 17000) Server Memory Model M393A2G40DB0-CPB) they are on the Qualified Memory List of the X10-DAL-i. I do have ES CPUs (Intel Xeon QFQG E5-2695 V3 ES 2.3GHz 14-Core Turbo 3.5GHz LGA 2011-3 X99 C612). Everything else has worked as expected. I am also running Unraid Nvidia with a GTX 660 to be used by a VM, and a P2000 for Emby. There is also a small 4 port SATA controller and Mellanox 10Gb adapter that are working as expected.

Memorytest completed with no errors, does anyone know what could cause this?

Hey Guys, I've recently upgraded my server to a dual CPU setup and have been stuck on a memory issue. The system runs fine, however it only shows 34GB of usable memory despite detecting all 64. I am using a Supermicro X10DAL-i and did have my memory sticks in the incorrect slots, however switching them provided no change. The BIOS detects all 64GB in the correct slots, however Unraid still does not show it all as usable. I am currently running Memtest86+ and have noticed that the testing like reads: xG - yG 2048M of 34G, where x and y count up from 0G - 2G to 62G - 64G. That line seems to contradict itself saying that its testing all 64GB but there are only 34? Also I'm not sure how long this is supposed to take, It seems to go about 1% a min overall. Thanks for all your help, Matt

Interesting, I'm not sure how to proceed with the fan issue then, is this something anyone else has experienced?

That downloaded the log telling me to access the tmp folder.

I installed the user scripts plugin and ran that script however I saw now change in the GPU temp. When I clicked view log, the log showed that the actual log was stored in the /tmp folder. I attempted to use midnight commander to copy that txt file somewhere it could be accessed. Midnight commander seems to work at random for me I'm not sure if I'm missing something but I was unable to perform any actions of the file. To install the script I mounted the flash share and browsed to the file created when I added a script with the plugin. I then copied the script from this post into that txt file and ran it. Am I doing all of this right?

Thank you, Ill give that a shot later today when I have time, I don't have any experience installing a script into the Nvidia Drivers, but I assume there is documentation about that. Ill report back if that fixes it.

Hi guys, I've been using Unraid Nvidia for a couple months now with Plex and its been working great. I did notice however that whenever the Plex docker was restarted the fan on my P2000 would ramp up to about 90% until Plex was restarted. This wasn't bothersome as I always kept Plex running, however when I recently switched to Emby I noticed that the GPU fan would ramp to 75-90% whenever there were no running processes in nvidia smi, so as soon as a transcode completes the fan speeds up. I have tried to find solutions to this, but haven't come across anyone speaking of the same issue. My server is on my desk and the fan is tolerable but not ideal, does anyone know of a way to fix this? I am running version 6.7.2 and the fan is usually at about 55% with the GPU at 55-60C with a transcode running. At idle it is usually about 80% with the GPU at 35-40C. Thank you all.

Nevermind, I have managed to confirm that that will work as intended by changing the wording of my search. I'll leave this up in case someone else wonders them same.

My main array only holds larger static files. I will be installing a new drive soon, as the array is getting full, and want to fill all the old drives to 90%, then not write to them anymore. Only one share is stored on the main array and it uses high water allocation. It didn't quite perfectly fill the drives as I was hoping, I assume I can use the exclude disks functionality to manually copy some files to the disk. I do have a cache drive however for example one drive has 617 GB free. If I were to exclude all other disks from the share, copy 17 GB of data to the array, then start the mover, would this work as I hope? If so, then I assume I could do this for all the other disks then exclude all 90% disks from the share forcing writing to the new drive? I want to confirm that excluding a disk from a share will not effect the data already on that disk.

Hi guys. I wanted to replace one of my drives with one of higher capacity. I had read that I should preclear the new drive then pull out the one to be replaced and allow a data rebuild to occur. I am replacing a 2TB drive with a 10TB drive. The 2TB drive had 615GB of data on it, and I had assumed that once it rebuilt that it would be complete. It is now at 750GB and is still reading from all drives and writing to the new one. I was under the impression that because I precleared the drive it would simply rebuild the necessary data and be done. I must've been mistaken, but what would happen if I cancelled the operation at this point?

Perfect, that has fixed it. Thanks to the both of you for your help!

Okay thanks I'll give that a shot. Sorry if this is a stupid question, but how do I access the cache drive to delete that folder. I am able to access the share but obviously if I delete it there, it will delete everywhere. I would think a disk share?

Network HDD is the share in question, all other shares are set to cache only. I didn't want a cache drive as much as a separate storage location. I wasn't expecting such a quick reply, thanks!

My mistake I meant to say 0 bytes on the cache drive, I will take the screenshot now.

I have been stumped with my main share showing some or all files unprotected. I have browsed all the forum posts I could find and have not found a solution for my situation. All shares show this error. I have a parity drive and single cache drive. All shares except my main data share are set to cache only so I would expect this error. The main share I created is has cache set to no. When I compute the share it shows 0 bytes on the cache drive. The cache drive does have a folder (Network HDD) for my main share however it is empty. I intend to replace a drive soon and need to be sure that the parity is correct. I am aware that unRaid parity is not faultless and isn't a replacement for a backup however at this time I cannot afford to separately back up all files. I ran a parity check yesterday which completed with 0 errors. I have attached the diag zip here. Thank you. fileserver-diagnostics-20190723-2059.zip