In Dashboard, CPU has only one core.

[DarkCorner]

I did a fresh install of TrueNAS Scale to try to fix several issues, starting with inaccurate CPU information and the load always at 100%.

Installation done, nothing configured yet and the CPU is still with only one core, instead of 2.
Xubuntu sees 2 and also lscpu from the shell reports the correct data.

Why then does the dashboard only see one core?

Code:

admin@truenas[~]$ lscpu
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   48 bits physical, 48 bits virtual
CPU(s):                          2
On-line CPU(s) list:             0,1
Thread(s) per core:              2
Core(s) per socket:              1
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       AuthenticAMD
CPU family:                      21
Model:                           16
Model name:                      AMD A4-5300 APU with Radeon(tm) HD Graphics
Stepping:                        1
Frequency boost:                 enabled
CPU MHz:                         1396.600
CPU max MHz:                     3400.0000
CPU min MHz:                     1400.0000
BogoMIPS:                        6787.04
Virtualization:                  AMD-V
L1d cache:                       16 KiB
L1i cache:                       64 KiB
L2 cache:                        1 MiB
NUMA node0 CPU(s):               0,1
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Mitigation; untrained return thunk; SMT vulnerable
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid ex
                                 td_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skin
                                 it wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pf
                                 threshold

 

[NugentS]

Please read Forum Rules

 

[DarkCorner]

Please read Forum Rules

Why this reproach?
What rule did I violate?

 

[Davvo]

Why this reproach?
What rule did I violate?

Properly list your full hardware specs.

 

[DarkCorner]

Properly list your full hardware specs.

Considering that the problem is in the CPU I thought the data about the CPU was sufficient.

• TrueNAS version: TrueNAS-SCALE-22.12.3.3
• Motherboard: ASRock FM2A85X-ITX
• CPU: AMD A4-5300 APU with Radeon(tm) HD Graphics
• Memory: 9.2GB DDR3
• 3 work HDD WD Red 3TB (WDC_WD30EFRX) with 1 Pool RAIDZ
• 1 Boot SSD Crucial CT120BX500SSD1
• 1 Apps SSD Crucial CT120BX500SSD1 (No apps installed)

On another NAS I have the same configuration, but with AMD A10 CPU and on this one too I see 2 core instead of 4.

In other points on the forum I read that perhaps it depends on the presence of Hyperthreading, but I have no idea whether it is useful to keep it enabled, nor where I can disable it. I don't see any options in the BIOS about this.

 

[Davvo]

• Memory: 9.2GTB DDR3

GB? TB? The motherboard supports 32GB max; at least 8 is required to run TN.

In other points on the forum I read that perhaps it depends on the presence of Hyperthreading, but I have no idea whether it is useful to keep it enabled, nor where I can disable it. I don't see any options in the BIOS about this.

It's an Intel propietary feature. There should be an AMD similar one.

 

[HoneyBadger]

Hey @DarkCorner

Is the dashboard reporting your A4-5300 a "one CPU, two threads"? If so it's detecting the AMD Bulldozer style "module" layout and translating that into a single "full core" with two integer threads.

 

[DarkCorner]

Hey @DarkCorner

Is the dashboard reporting your A4-5300 a "one CPU, two threads"? If so it's detecting the AMD Bulldozer style "module" layout and translating that into a single "full core" with two integer threads.

Thanks for the explanation.
Is this a feature I can/should disable?
Both the motherboard and the CPU are old, what interests me is having maximum performance with minimum problems.

 

[somethingweird]

based on lscpu output

Vulnerability Retbleed: Mitigation; untrained return thunk; SMT vulnerable
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected

does CPU Mitigation via OS turn off hyperthreading? Just wondering - got CPUs without hyperthreading - so I don't know.

 

[Sparkey]

Running TrueNAS on old HW is problematic.

 

[Davvo]

Running TrueNAS on old HW is problematic.

Not really.

 

[HoneyBadger]

Running TrueNAS on old HW is problematic.

Old server hardware is just to be electrically inefficient, or be short on performance for certain features, but there's nothing inherently bad about it - save for components that wear out over time. I have a 2010-era HP system ticking along just fine, still merrily saturating its gigabit line - but I wouldn't ask it to run Apps, VMs, or handle an encrypted pool.

 

[Davvo]

Define old, because 2010-era hardware is ancient nowadays.
2000-era is Jurassic.

 

[asap2go]

based on lscpu output

Vulnerability Retbleed: Mitigation; untrained return thunk; SMT vulnerable
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected

does CPU Mitigation via OS turn off hyperthreading? Just wondering - got CPUs without hyperthreading - so I don't know.

In FreeBSD Hyperthreading will be disabled as mitigation. But not in most Linux distros.
SMT (Simultaneos MultiThreading, AMD's name for hyperthreading) can usually be explicitly disabled in the BIOS or sometimes unintentionally if one sets the CPU into ECO mode in BIOS or similar.

 

[Davvo]

Leave me my hyperthreading!

 

[MrGuvernment]

Interesting, on Core 13 U5.3 I just enabled HT the other day, to run some VMs on my 10 core Xeon Silver, and it shows them fine..

 

[Davvo]

I can confirm that my hyperthreading still works on CORE 13U5.3, and I really hope it stays so or that at least I am given an option to disable the mitigation... I want my 4 threads!

@Patrick M. Hausen you know anything about this?

 

[asap2go]

I can confirm that my hyperthreading still works on CORE 13U5.3, and I really hope it stays so or that at least I am given an option to disable the mitigation... I want my 4 threads!

@Patrick M. Hausen you know anything about this?

I was wrong. It was under OpenBSD and not FreeBSD.

 

[LizzicalGal]

I am having the same problem. It only shows 1 core. I am runing on older hardware, Dell Inspiron 560, Intel celeron, 2 cores, 2gb or ram. Trunas installed on a 125GB SSD. I know I am bellow the required RAM I have 6gb on the way. But I don't think that is related to only one core showing up. It was running fine. I have 2x4tb HDD mirrored. I did noticed the processor has been runing at capacity lately. But the whole time it only registers 1 core which is the topic of this thread.

DarkCorner did you ever figure out what was wrong? or anyone?​

 

[Davvo]

@LizzicalGal which Celeron are you running exactly?