rigacci.org

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Mini PC T9Plus with D4-300 TerraMaster DAS ======

In March 2024 I decided to assemble an **home server** to be run **24h, 7/7**, the system is intended to replace an old Dell PowerEdge T110, which served my house for the past 14 years without any issue. The main reason for the switch is power consumption and the fear of old hardware wear.

I discovered that a new generation of **Mini PCs** based on the **Intel Alder Lake N95** processor outperform the old **Intel Xeon @ 3.0 GHz**. The [[https://www.cpubenchmark.net/compare/|cpubenchmark.net]] site scores a CPU Mark 5391 versus 1070, respectively. Because sometimes I use the home server to encode large video files (using ffmpeg), I was even more pushed to change the hardware.

My home server is acting also as a domestic firewall (running Debian GNU/Linux), so I opted for a dual LAN Mini-PC. Obviously the only problem is the storage: the embedded SDD disk is not sufficient for my media library, so I opted for an esternal USB Direct Attached Storage. The choice was a **D4-300 TerraMaster DAS** which will host **two 4 Tb 3.5 inches drives** (leaving two empty slots).

^  Mini PC T9Plus  ^^
^ CPU       | Intel(R) N95, 4 Cores  |
^ RAM       | 16 Gb  |
^ HDD       | NS512GSSD330 512 Gb Solid State Disk  |
^ Ethernet  | 2 x PCI Express Gigabit Realtek RTL8111/8168/8411  |
^ WiFi      | Realtek RTL8852BE PCIe 802.11ax  |
^ Video     | Intel Alder Lake-N UHD Graphics  |

^  D4-300 TerraMaster DAS  ^^
^ Disk Slot Number       | 4  |
^ Compatible Disk Types  | 3.5" SATA HDD\\ 2.5" SATA HDD\\ 2.5" SATA SSD  |
^ USB                    | USB3.1 Type-C gen1 x 1  |

===== Installing Debian GNU/Linux =====

It seems that Linux **kernel 6.1.0** (as shipped with Debian 12 Bookworm) still does not support the WiFi adapter **RTL8852BE**, see this page **[[rtl8852be_on_debian_12]]**.

These are the USB and PCI peripherals:

<code>
Bus 001 Device 008: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 001 Device 006: ID 0573:1573 Zoran Co. Personal Media Division (Nogatech) USB Audio and HID
Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 002: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
</code>

<code>
00:00.0 Host bridge: Intel Corporation Device 4618
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [UHD Graphics]
00:14.0 USB controller: Intel Corporation Alder Lake-N PCH USB 3.2 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Alder Lake-N PCH Shared SRAM
00:16.0 Communication controller: Intel Corporation Alder Lake-N PCH HECI Controller
00:17.0 SATA controller: Intel Corporation Alder Lake-N SATA AHCI Controller
00:1c.0 PCI bridge: Intel Corporation Device 54bb
00:1d.0 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port
00:1d.3 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port
00:1f.0 ISA bridge: Intel Corporation Device 5482
00:1f.3 Audio device: Intel Corporation Alder Lake-N PCH High Definition Audio Controller
00:1f.4 SMBus: Intel Corporation Alder Lake-N SMBus
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-N SPI (flash) Controller
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
        RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: Realtek Semiconductor Co., Ltd.
        RTL8852BE PCIe 802.11ax Wireless Network Controller
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
        RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
</code>

==== The RGB rainbow LEDs ====

The T9Plus Mini PC has a strip of RGB LEDs all around the case; the default behaviour is to play a circular rainbow effect, rather nice the first time that you see it, but utterly annoing after a couple of hours!

You can program the LEDs with several visual effects, brigthness and speed by sending some specific commands to the USB serial adapter exposed to the operating system. The manufacturer provides a Windows program to configure the LEDs, but several users on the internet reported that the program (named **LedControl.exe**) is detected as a malware by several antivirus software. I never run MS-Windows on this PC because I booted and installed Debian GNU/Linux since the very first boot, so I cannot give any insight on it.

Fortunately enough, someone [[https://www.reddit.com/r/MiniPCs/comments/18icusg/t9_plus_n100_how_to_control_led/|made the reverse engineering of the serial protocol]] required by the LEDs controller and published a working code. Then I wrote a Python program to make the programming: **[[t9plus_mini_pc_rgb_led_control]]**.

In Debian GNU/Linux 12 it is possibile to run the script at bootstrap; just add a Systemd unit creating the file **/etc/systemd/system/t9plus-leds.service** with:

<file>
# /etc/systemd/system/t9plus-leds.service
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/local/bin/t9plus-leds -m Off
[Install]
WantedBy=multi-user.target
</file>

Run and enable the service issuing the command:

<code>
systemctl daemon-reload
systemctl enable t9plus-leds.service --now
</code>

===== Always on =====

Press **Del** at bootstrap time to enter the BIOS settings, go to the **Boot** page and set **State After G3** => **S0 State**.

The ACPI power states are:

  * S0: Normal Powered-On state (system working)
  * S1: Standby
  * S3: Suspend to Ram
  * S4: Suspend to Disk
  * S5: Shutdown state (soft off: some devices are still powered-on)
  * G3: Mechanical off state

===== USB Fast Boot problem =====

{{ .:mini_pc_t9plus:mini-pc-t9plus-bios-boot-usb.jpg?180|BIOS Fast Boot settings}}
Sometimes (randomly, about 50% of the time) the **reboot** command does not work. The shutdown process seems to proceed well and the PC seems to begin the reboot process, but the video signal does not switch-on and the host remains frozen. The power LED remains on.

The wake-on-lan (which is working well in normal power-off condition) does not reboot the PC when it freezes in that way.

It seems that **the reboot problem is tied to the USB attached storage**. If I remove the TerraMaster DAS and allow the Mini PC to boot with just the GNU/Linux operating system from the SSD, the reboot seems 100% reliable.

May be I found a workaround for the problem: in the BIOS settings I set the **Boot** => **Fast Boot** to **Enabled**, then I leaved the **SATA Support** to **All SATA Devices** but set the **USB Support** to **Disable** (just for safety I disabled all the boot devices, except SATA). Till now I tried several reboots, without any issue!

The problem with this workaround is that **you cannot longer enter into the BIOS setup program**, because the USB keyboard is not initialized at boot and **you cannot press the Delete key**.

If the system starts normally, it is simple to enter the BIOS setup from a Linux command propt; just issue the command:

<code>
systemctl reboot --firmware-setup
</code>

It seems that - by chance - I was able to **entered the BIOS setup even when Fast Boot was enabled**; it was a mix of keeping the Delete key pressed on the keyboard while long-pressing the power button for about 4 seconds, or by repeatedly pushing the power button 4 or 5 times. But I was not able to replicate this behaviour in a consistend manner.

===== The D4-300 USB attacched storage =====

Outpt of the **lsusb** command:

<code>
Bus 002 Device 004: ID 174c:55aa ASMedia Technology Inc.
  ASM1051E SATA 6Gb/s bridge,
  ASM1053E SATA 6Gb/s bridge,
  ASM1153 SATA 3Gb/s bridge,
  ASM1153E SATA 6Gb/s bridge
Bus 002 Device 003: ID 174c:55aa ASMedia Technology Inc.
  ASM1051E SATA 6Gb/s bridge,
  ASM1053E SATA 6Gb/s bridge,
  ASM1153 SATA 3Gb/s bridge,
  ASM1153E SATA 6Gb/s bridge
...
</code>

Outpt of the **lsusb -t** command:

<code>
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
        |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M
        |__ Port 4: Dev 4, If 0, Class=Mass Storage, Driver=uas, 5000M
...
</code>

===== USB instability =====

It turned out that **the USB bus is not reliable enough**, maybe due **power issues**. Simply inserting a USB storage key caused **read errors** on the USB attached storage and a consequent **kernel panic**.

===== USB Direct Attached Storage =====

==== Performance ====

I installed two hard disks on the Terramaster DAS:

  * Western Digital 3.5" 4Tb WD Red NAS 256 Mb, 5400 rpm, SATA 6Gb/s - **WDC WD40EFZX-68AWUN0**
  * Seagate IronWolf 3.5" 4Tb 64 Mb cache, 5900 rpm, SATA 6Gb/s - **ST4000VN008-2DR166**

I made some tests on read performances on the USB attached device using **hdparm**. Here are the average results, which are similar on both my RAID disks (a bare 1% more performance on the Western Digital):

<code>
hdparm -t /dev/sdb
/dev/sdb:
 Timing buffered disk reads: 572 MB in  3.00 seconds = 190.47 MB/sec
</code>

==== Power management ====

==== Monitoring SMART with Nagios/Icinga ====

Unfortunately the **check_ide_smart** Nagios plugin provided by the Debian 12 package **monitoring-plugins-basic 2.3.3-5+deb12u2**, is unable to scan the SMART attributes of the SATA drives through the Terramaster Direct Attached Storage. As reported into the **[[https://github.com/nagios-plugins/nagios-plugins/issues/16|Nagios-plugins issue #16]]**, the //check_ide_smart// plugin should be phased out in favor of **[[https://github.com/spjmurray/check_scsi_smart|check_scsi_smart]]**.

We compiled the plugin binary from the sources (using the master branch [[https://github.com/spjmurray/nagios-plugin-check-scsi-smart/commit/064a9fdac07414947e0465a044840b964cd85e9f|064a9fd]]) and now we can check the SMART attributes of each disk into the DAS:

<code bash>
check_scsi_smart -d /dev/sdb
OK: prdfail 0, advisory 0, critical 0, warning 0, logs 0 | 1_read_error_rate=0;;;; 3_spin_up_time=3883;;;; 4_start_stop_count=26;;;; 5_reallocated_sectors_count=0;;;; 7_seek_error_rate=0;;;; 9_power_on_hours=19301;;;; 10_spin_retry_count=0;;;; 11_recalibration_retries=0;;;; 12_power_cycle_count=17;;;; 192_power_off_retract_count=5;;;; 193_load_cycle_count=49;;;; 194_temperature=32;;;; 196_reallocation_event_count=0;;;; 197_current_pending_sector_count=0;;;; 198_uncorrectable_sector_count=0;;;; 199_ultradma_crc_error_count=0;;;; 200_multi_zone_error_rate=0;;;;
</code>

To integrate the SMART checks for all the devices into a single Nagios check and to have a more terse output, we created the following script **check_scsi_smart_all**:

<code bash>
#!/bin/sh
if [ "$#" -lt "1" ]; then
    echo "Usage: $(basename $0) sda [sdb ...]"
    exit 1
fi
OUTPUT=''
STATE=0
for DEV in $@; do
    OUT="$(/usr/local/sbin/check_scsi_smart -d /dev/$DEV)"
    RET=$?
    if [ $RET -gt $STATE ]; then
        STATE=$RET
    fi
    if [ "$RET" -eq "0" ]; then
        # Get only the short status, e.g. "OK".
        OUT="$(echo "$OUT" | cut -f1 -d':')"
    else
        # Get the summary, e.g. "OK: prdfail 0, advisory 0, critical 0, warning 0, logs 1 "
        OUT="$(echo "$OUT" | cut -f1 -d'|' | sed 's/[[:space:]]\+$//')"
    fi
    test -n "$OUTPUT" && OUTPUT="${OUTPUT}; "
    OUTPUT="${OUTPUT}${DEV}: ${OUT}"
done

OUTPUT="check_ide_smart[${OUTPUT}]"
case $STATE in
    0)
        OUTPUT="OK: $OUTPUT"
        ;;
    1)
        OUTPUT="WARNING: $OUTPUT"
        ;;
    2)
        OUTPUT="CRITICAL: $OUTPUT"
        ;;
    *)
        OUTPUT="UNKNOWN: $OUTPUT"
        ;;
esac
echo "$OUTPUT"
exit $STATE
</code>

Finally we defined the NRPE Nagios check with a line into **/etc/nagios/nrpe_local.cfg**:

<file>
command[check_scsi_smart]=/usr/bin/sudo /usr/local/sbin/check_scsi_smart_all sda sdb sdc
</file>


===== ACPI errors =====

During bootstrap several error messages appears on the console (and are logged in syslog):

<code>
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS01], AE_NOT_FOUND (20220331/dswload2-162)
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.ITE8.GETT], AE_NOT_FOUND (20220331/psargs-330)
...
</code>

This is caused by the BIOS missing the "Advanced Error Reporting” mechanism. It is possibile to ignore it by adding ''pci=noaer'' to the Linux command line in **/etc/default/grub**:

<file>
GRUB_CMDLINE_LINUX="pci=noaer fsck.repair=yes consoleblank=0 reboot=cold,force"
</file>

Do an ''update-grub'' and reboot.

===== Web References =====

  * **[[https://superuser.com/questions/928741/how-can-i-check-whether-usb3-0-uasp-usb-attached-scsi-protocol-mode-is-enabled|How can I check whether USB3.0 UASP (USB Attached SCSI Protocol) mode is enabled in Linux?]]**
  * **[[https://unix.stackexchange.com/questions/347006/systemd-how-do-i-automount-a-usb-filesystem-using-etc-fstab|systemd: How do I automount a USB filesystem using /etc/fstab?]]**
  * **[[t9plus_mini_pc_rgb_led_control]]**
  * **[[https://www.reddit.com/r/MiniPCs/comments/18icusg/t9_plus_n100_how_to_control_led/|T9 Plus N100 - How to control LED]]**
  * **[[https://github.com/thekief/s1t-ledcontrol|LED Controller]]**
  * **[[https://minipcunion.com/viewtopic.php?t=4424|Mini PC RGB AK1 Plus - Controllo RGB]]**
  * **[[https://forum.manjaro.org/t/how-can-i-fix-these-acpi-errors/146857/|How can I fix these ACPI errors?]]**