Hello,
I wanted to build a small travel-friendly system using the new Beelink ME mini. As my drives, I got five Seagate FireCuda 530R (meant for the storage pool with RAIDZ1) and one WD Red SN700 (OS installation disk).
Even though TrueNAS Scale Version 25.04.1 recognized all drives in die Disk Overview, I’m only able to create a storage pool with 3 of the Seagate drives instead of five. Using the command “nvme list” shows only four drives (including the OS drive). I had already done some searches and found people with similar problems on other hardware / devices. The recommendation to disable VT-D, but it didn’t fix anything.
One additional step I already took: Checked using the included Windows Installation on the 64 GB eMMC storage with the result that it can detect all 6 drives with them being all accessible from within Windows.
Do you have any idea what I can do for troubleshooting?
You found the correct model!
Even though it shows preorder, mine arrived 20 days after ordering it.
My current further steps in troubleshooting have been updating the bios version from M1V303 to M1V305. But no change.
// Update: // BE AWARE: After doing some tests, this method failed after ~4 hours, making the pool fail, reboot fixed it. Better wait for a TureNAS release with newer kernel
Found the solution (thanks to Ai). Beelink uses the ASM2824 controller. The current Linux Kernel of TureNAS has an upstream bug in the pcie driver that prevents the first (or occasionally the fifth or sixth) downstream port on that switch from completing link-training, so any NVMe devices on those lanes never appear to the OS.
Ai asked me to edit GRUB and add this at the end line of “linux”:nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off. Trying this fixed my problems.
I then added this permanently by using the shell with this command: midclt call system.advanced.update '{"kernel_extra_options": "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off"}'.
After this, I could check if was successfully added by this command midclt call system.advanced.config | jq .kernel_extra_options.
PS: Rolling back this fix should be possible using midclt call system.advanced.update '{"kernel_extra_options": ""}'
Hello, new poster here. Signed up to respond in this thread.
Another discussion thread on Reddit, using TrueNAS, also ran into issues until a poster pointed out that the built-in power supply has a rated output of 45W – and sticking 6 SSD sticks and the mobo against a 45W PSU without thinking through power needs could cause lots of turbulent instability that has nothing to do with TrueNAS.
The OP on reddit replaced his SSDs of choice with Lexar low-power SSDs and got everything working ok.
What SSDs are you using and are you near or at the PSU 45W limit?
OP is using the Seagate FireCuda 530R which according to its dataset consume between 8-9W (8.3 to 8.9W, to be precise) on average during activity. With 6 SSDs at 8W each, the 48W from the SSDs alone would be above the rated 45W output - and that’s not accounting for anything else in the system. Sorry - 5 530R’s is 40W, and then there’s the WD Red SN700 and anything else. Still, those are “average” values - IIRC the M.2 socket is capable of delivering more.
The product datasheet for the WD Red SN700 has peak power draw at 2.8A; Watts = Amps x Volts, and if 5V = 14W. While that’s “peak” – add in the Mobo / Wifi / Fan / reserve for peaks and inefficiency – I wonder if OP is at or above the PSU limit of watt draw.
