logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·30.10.26
← Back to news

FreeBSD on Aoostar WTR Pro NAS

Original article
tumfatig.net|31 points|3 comments|by Mr_Minderbinder|Sep 19, 2026

Exploring FreeBSD on the Aoostar WTR Pro NAS

By TuM'Fatig
Published: 2026-09-08 | Reading Time: ~11 minutes | Tags: #aoostar #freebsd #netbsd #openbsd #nas


🎯 The Quest for the Perfect Mini-NAS

Finding a Network Attached Storage (NAS) device that checks every single box is a daunting task. My specific requirements were quite stringent:

  • Must fit within a 10" rack.
  • Must provide both NVMe and SATA storage options.
  • CPU must be efficient (no "power hogs").
  • Low overall wattage consumption.
  • Compatibility with a non-proprietary OS.
  • Absolute Requirement: Must be capable of running a BSD-family operating system.

After an extensive search, the AOOSTAR WTR Pro (Ryzen Edition) emerged as the only candidate meeting all these prerequisites.

"Finding a machine that balances size, storage versatility, and BSD compatibility is rarely a simple process, but the WTR Pro seems to hit the sweet spot."


🛠️ Hardware Breakdown

Physical Design & Accessibility

The chassis is surprisingly cool to the touch, even in a room kept at 25–27∘C25\text{--}27^\circ\text{C}25–27∘C.

  • Internal Slots: Both the RAM and NVMe slots are located on the underside of the unit. They are secured with screws and, crucially, are numbered, which eliminates guesswork when mapping drive IDs within the OS.
  • SATA Bays: Accessible from the front.
    • The front panel is held in place by magnets, neatly concealing the LEDs and drive caddies.
    • 3.5" Drives: Feature a clever, tool-less installation mechanism.
    • 2.5" Drives: Easy to install Actually quite finicky; it took several failed attempts before I successfully seated them.
    • Ordering: SATA disks are indexed from the bottom (SATA 1) to the top (SATA 4).

Thermal & Acoustic Performance

The cooling system is a bit of a mixed bag. The default fan profile is quite loud, emitting a low-pitched drone. There is a distinct "metallic" quality to the sound, likely caused by the resonance of the case.

Aoostar WTR Pro Hardware


⚙️ BIOS & Initial Power Baseline

To get started, I referenced reviews from Hardware Haven and Robtech.

Quick Boot Guide:

  • F7 →\rightarrow→ Boot Selection Menu
  • Del →\rightarrow→ BIOS Setup
  • Note: SecureBoot is disabled by default.

The "Bare Bones" Power Draw

With only a single 32 GB RAM module installed (no storage), I monitored the PC Health Status page in the BIOS.

MetricValue
Total Power Draw≈28W\approx 28\text{W}≈28W
System Temp26∘C26^\circ\text{C}26∘C
CPU Temp68∘C68^\circ\text{C}68∘C
CPU Fan Speed≈1900 RPM\approx 1900\text{ RPM}≈1900 RPM
System Fan Speed≈820 RPM\approx 820\text{ RPM}≈820 RPM

The high CPU fan speed explains the whistling noise noted earlier. Interestingly, adding an RJ45 cable, a USB keyboard, or a 10" USB LCD (800x600) had negligible impact on power consumption. Even adding two NVMe drives didn't significantly move the needle.


🐧 Linux as a Power Benchmark

To establish a "floor" for power consumption, I installed Alpine Linux and Debian 13. I used a Fibaro FGWP-102 integrated with Home-Assistant for monitoring.

Optimization Results:

  1. Alpine: Dropped from 13W→11W13\text{W} \rightarrow 11\text{W}13W→11W after powertop --auto-tune.
  2. Debian 13: Dropped to 9W9\text{W}9W with tuning, and finally to 8W8\text{W}8W after removing the screen and keyboard.
  3. Thermals: lm-sensors reported temperatures between 34–38∘C34\text{--}38^\circ\text{C}34–38∘C.

🌐 The BSD Experiments

1. NetBSD 11.0

NetBSD wasn't my primary target, but I wanted to see the default behavior.

  • Installer Power: 19W19\text{W}19W
  • Idle Power: 18W18\text{W}18W (remained 18W18\text{W}18W even after running estd -os)
  • Headless Power: 14W14\text{W}14W (after removing the USB monitor)

CPU Status:

# sysctl -a | grep freq
machdep.dmi.processor-frequency = 2000 MHz
machdep.cpu.frequency.current = 1600

The temperature was recorded at 40.75∘C40.75^\circ\text{C}40.75∘C via envstat.

2. OpenBSD 7.9

I tested both the stable release and the snapshot branch.

  • Initial Power: 21W21\text{W}21W (during setup wizard).
  • Headless Power: ≈10W\approx 10\text{W}≈10W.
  • CPU Behavior: Defaults to full speed (2 GHz2\text{ GHz}2 GHz).

To optimize, I enabled apmd:

# rcctl enable apmd
# rcctl set apmd flags -A
# rcctl start apmd

After tuning, hw.cpuspeed dropped to 160016001600.

Sensor Data:

  • CPU Temp: 37.25∘C37.25^\circ\text{C}37.25∘C
  • NVMe 0: 31.00∘C31.00^\circ\text{C}31.00∘C
  • NVMe 1: 38.00∘C38.00^\circ\text{C}38.00∘C

3. FreeBSD 15.1

This was the main event.

  • Installation Power: 19W19\text{W}19W
  • Idle Power: 18W18\text{W}18W
  • Headless Power: 15W15\text{W}15W

Upon checking htop, I noticed the CPU remained locked at 2 GHz2\text{ GHz}2 GHz. I attempted to verify this using the standard system control tools:

# sysctl 
# (Checking CPU frequency settings...)

(Note: The original text cuts off here, but the trend indicates FreeBSD's power consumption is higher than Debian's baseline and requires further tuning to match OpenBSD's efficiency.)