I have a ME Mini with all M.2 slots populated using 6× 4TB Crucial P3 Plus drives. Every time I reboot, only one (sometimes two) of the six NVMe drives are detected in BIOS, usually the one on Bus 5. Even after multiple reboots, the others are still missing. However, if I shut down the unit completely and power it back on, all six drives are detected consistently. This behavior is fully reproducible: reboot = missing drives, shutdown + power on = all drives detected. Is there a way to fix this so all drives are detected after a reboot? Some extra info that might help: BIOS version: M1V305 Fast Boot: disabled No USB devices or external drives connected OS: TrueNAS, installed on the internal 64GB eMMC The consistently detected NVMe drive shows up on Bus 5, which appears to correspond to slot 4. When all six are detected, BIOS lists drives on Buses 3 to 8 (as seen in BIOS → NVMe Configuration → Drive Name → Seg:Bus:Dev:Func → 00:05:00:00) Would appreciate any advice or insight, thank you

Reboot Fails to Detect All NVMe Drives on ME Mini – Needs Full Shutdown

Beelink CS-George

Hi there, we will test and let you know if we can reproduce the problem

Beelink CS-George

Hi there, after we test, we are unable to reproduce the problem.
① Please use the latest Truenas version.
② Your BIOS is the latest one.
③ Please contact our team for a replacement if you try the new version of Truenas. Here is our contact email support-pc@bee-link.com

pasta

Beelink CS-George
Can you please confirm whether your testing was also done with all six M.2 slots running with drives?

I have already tried with the latest TrueNAS SCALE version, and the problem still occurs. I don’t believe this is related to the OS, as the issue is present even if I reboot before the OS starts loading.

This behaviour causes failure alerts after every update, since the OS needs to reboot and then fails to load the storage pool because most drives are missing in BIOS after a reboot. The only way to recover is to manually power the unit off completely and turn it back on.

It’s concerning that this product cannot reliably detect all six drives at the full advertised 24TB capacity when simply rebooting.

Luke

I’m encountering the same issue. Also running 6× 4TB Crucial P3 Plus drives but with the M1V304 BIOS and Ubuntu 24.04.3 LTS

Beelink CS-George

Luke Hi there, please update to V305 to see if it solves the problem.
https://dr.bee-link.cn/?dir=uploads%2FMEmini%2FBIOS%2FMEMINI-Version-M1V305--12GB-onboard-RAM--Solve-Secure-boot-issue

Beelink CS-George

pasta Hi there, we have perform some test , but we are unable to reproduce the problem.
How about you send the item back for checking ?

Luke

Beelink CS-George

Confirmed this is still an issue after the applying the V305 update

After rebooting the device the drives are consistently not being detected. Rebooting to BOIS shows a single drive on Bus 03 for me. Exiting from BOIS and loading the OS at that point will show all drives. All drives will show after a shutdown

pasta

Beelink CS-George Can you please confirm whether your testing was also done with all six M.2 slots running with drives?

Beelink CS-George

Luke Hi there, please install the system in the SSD of the slot 4.

Luke

Beelink CS-George Could you confirm how that might help resolve the issue? Following a reboot the drives are not visible in BIOS, regardless of where the OS is installed. The OS is currently installed on the eMMC and that boots fine, but the drives are not visible to the storage pool

Beelink CS-George

Luke 1. Access the TrueNAS Web UI
Log in to your TrueNAS SCALE dashboard.

Navigate to System Settings
Go to System Settings → Advanced.
Add Kernel Parameters
Under Kernel Extra Options, enter:

text
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

Save and Reboot
Click Save.

Reboot the system for changes to take effect.

pasta

Beelink CS-George There’s no such thing as “Add Kernel Parameters” in TrueNAS SCALE’s System Settings → Advanced.

pasta

I figured out how to get those set by shell.

To check the current “kernel_extra_options” config, mine was just "":
midclt call system.advanced.config | grep kernel_extra_options

To check the currently applied default_ps_max_latency_us, mine was originally 1000:
cat /sys/module/nvme_core/parameters/default_ps_max_latency_us

To apply @Beelink CS-George ’s suggestion:
midclt call system.advanced.update '{"kernel_extra_options":"nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off"}'

Then rebooted.

Checked that default_ps_max_latency_us was now 0:
cat /sys/module/nvme_core/parameters/default_ps_max_latency_us

After testing reboots and full shutdown cycles, it still did not solve the problem. Rebooting still loses the drives every time. Getting back into TrueNas showed missing pool and missing disks because BIOS still doesn’t see them on reboot. Full shut down is still needed to detect all 6 drives again.

I reverted @Beelink CS-George ’s suggestion with:
midclt call system.advanced.update '{"kernel_extra_options":""}'

Beelink CS-George

pasta
By the way, did you install the Truenas on SSD of the slot 4?

pasta

Beelink CS-George It’s installed on the internal 64gb emmc.

Beelink CS-George

pasta Hi there, please install it on SSD on slot 4.

It is not recommended to install Linux on the built-in eMMC of the ME MINI; instead, installing it in Slot 4 is advised. The reasons are as follows:
Linux has not been optimized for this device, and the eMMC is also not suitable for Linux’s usage scenarios.
Linux writes logs frequently. The eMMC is prone to wear and “disk drop” (sudden unrecognition by the system) when enduring such frequent read-write operations for a long time.
The NVME in Slot 4 is more resistant to read-write wear, which can make the system more stable.

pasta

Beelink CS-George The issue is not OS stability. The OS works fine every single time from the eMMC. The issue is that the hardware/firmware does not reliably detect all 6 nvme drives on reboot, as can be seen in BIOS itself.

Can you please confirm if you will be bringing this up with your firmware development team, they need to address that when all 6 nvme drives are used, there is an issue where drives are not all detected on reboot? We need a possible firmware update to fix this.

And if you are firm on the fact that OS’s should not be installed on the eMMC, why does the OS come pre-installed on it from factory when buying the option without an optional SSD? What is the eMMC part of the product for?

And I’d like to re-iterate @Luke ’s question to your repeated suggestion that you did not actually answer;

Could you confirm how that might help resolve the issue? Following a reboot the drives are not visible in BIOS, regardless of where the OS is installed. The OS is currently installed on the eMMC and that boots fine, but the drives are not visible to the storage pool

Beelink CS-George

pasta Hi there, the preinstalled OS is windows system not Linux system. If you install the Linux on the SSD in slot 4 the problem persists, you can send the item back for a replacement.

pasta

Beelink CS-George Moved the OS off the eMMC and it made no difference, as predicted BIOS still fails to detect all 6 drives on reboot. You still haven’t confirmed if your “we have perform some test , but we are unable to reproduce” was with 6 drives either.