AOOSTAR WTR Max vs Minisforum N5 Pro

oh, this is a really good thought. the corrupt metadata buffer is all zeros from his xfs dump. that would be consistent with a drive reset or incomplete write – could totally be the power brick or voltage droop under load.

what’s also interesting is mergerfs is lower controller load than zfs. only one drive is active at any given time. so imho mergerfs is the easiest possible scenario, no different than jbod, from a hardware stress standpoint.

I’m in Austin TX, so 120V. I did originally consider power delivery as a suspect. My critical appliances, namely the NAS server, are plugged into a CyberPower 1500 (smooths jitter and allows me to safely power down appliances in the case of a power outage). When first testing the N5 Pro, I had it on the CyberPower. Later on I moved it to an entirely different outlet in the house without the CyberPower just to see if there would be a difference. Unfortunately it was the same behavior.

I would also suspect that if this were an issue in power delivery, I’d see failures across multiple devices over time. I just don’t see that behavior.

I still have the server until Monday when I take it to the UPS office, so if there’s a different test I can run I’m all for it. Let me stress I would REALLY rather this server work out and I keep it, but every test suggests the N5 Pro is at fault here.

For hard drives, I’m using 4x20TB Western Digital Red Pros, and a single 24TB Western Digital Red Pro that is meant for parity. During testing, at one point I only had two of the 20TB drives in it just to see if behavior would change (it did not unfortunately).

Oh and I ran another test on Scrappy last night - I have a NVMe SATA port device that uses the same controller as the N5 Pro (I watched your cheat code video many moons ago - there’s a reason I call this NAS box Scrappy :wink: ).

For kicks I figured I’d just try it out on Scrappy to see if the same error would arise - and it worked just fine. So I’m not even sure if I can blame the SATA controller itself on the N5 Pro - this is more of a (seemingly very minor but very annoying) signal integrity issue. I don’t completely rule out the SATA controller on the N5 Pro due to the fact that the kernel message comes from the SATA controller itself before loss of all the SATA hard drives.

Anyway thought I’d throw that out there.

interesting

last thing is maybe checking output voltage of power brick if you have a volt meter. sus power brick could do it maybe, too.

if you have another brick with same voltage and at least as many watts(amps) that may be worth trying

I don’t have another power brick that matches that one (it’s huuuge). If I use a multimeter and test it, it gives me around 19 volts.

Hey y’all; it looks like there’s substantial discussion on what seems to be either the same or a related issue on Reddit as well. It doesn’t look like I’m allowed to put links in my posts yet (I just made this account to post this), but if you search “(Silent) Data Corruption on N5 Pro NAS” in r/MINISFORUM you’ll see a bunch of folks running into this.

It appears that the issue is not isolated to any individual machine.

2 Likes

We happened across this level1techs thread while discussing the reddit results in Minisforum’s discord. Hopefully Minisforum issues some sort of official response. There are at least a few potential buyers, including myself, who are hesitant now to purchase what is otherwise a fantastic looking machine as a result of what seems to be a dealbreaker issue.

Here’s the Reddit thread: https://www.reddit.com/r/MINISFORUM/comments/1pbnql6/silent_data_corruption_on_n5_pro_nas/

There are at least 3 or 4 more reports of the issue there. At least from the comments there it seems Minisforum is aware of the issue.

I have one still in the box (unopened) until I buy HDDs, but I am now on the fence about this unit.

Interesting…I ended up getting a full refund on mine. My only gripe would be that I had to pay for some of the shipping for the return, but rather than that it was a painless process and Minisforum support was very responsive and helpful throughout the entire process.

Sucks that others are seeing problems. I hope it gets figured out.

I just recently received some SATA HDDs to throw into my N5 Pro. I’ve been using this awesome machine for a while with some high‑capacity U.2 drives, but I wanted more bulk storage. So I installed 2× 24 TB HDDs in the 3.5" bays and copied a few TB of data over. No issues showed up during the initial copy, but as soon as I fired up my media services and they started reading from the new disks, problems began.

I saw the kernel log entry many others have mentioned right before corruption became apparent:
[347523.311655] ahci 0000:c1:00.0: Using 64-bit DMA addresses

Then BTRFS started to complain:

[367985.086640] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 131072 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086651] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815808, gen 0
[367985.086652] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 262144 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086657] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 393216 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086660] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 655360 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086664] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815810, gen 0
[367985.086664] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815810, gen 0
[367985.086676] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 786432 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086680] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 917504 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086684] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815811, gen 0
[367985.086688] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815812, gen 0
[367985.086690] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 1179648 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086693] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815813, gen 0
[367985.086700] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815814, gen 0
[367985.086703] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 1310720 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086704] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815815, gen 0
[367985.086717] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 1703936 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086713] BTRFS warning (device sda1): csum failed root 256 ino 7261 off 1441792 csum 0x8941f998 expected csum 0x9c51e21f mirror 2
[367985.086719] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815816, gen 0
[367985.086724] BTRFS error (device sda1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 15815817, gen 0
[367985.320236] BTRFS info (device sda1): read error corrected: ino 7261 off 917504 (dev /dev/sda1 sector 1939926272)
[367985.320470] BTRFS info (device sda1): read error corrected: ino 7261 off 2228224 (dev /dev/sda1 sector 1939926328)
[367985.320543] BTRFS info (device sda1): read error corrected: ino 7261 off 2359296 (dev /dev/sda1 sector 1939926336)
[367985.320691] BTRFS info (device sda1): read error corrected: ino 7261 off 4063232 (dev /dev/sda1 sector 1939926416)
[367985.320815] BTRFS info (device sda1): read error corrected: ino 7261 off 4849664 (dev /dev/sda1 sector 1939926448)
[367985.320948] BTRFS info (device sda1): read error corrected: ino 7261 off 5373952 (dev /dev/sda1 sector 1939926472)
[367985.321539] BTRFS info (device sda1): read error corrected: ino 7261 off 5505024 (dev /dev/sda1 sector 1939926480)
[367985.321672] BTRFS info (device sda1): read error corrected: ino 7261 off 5898240 (dev /dev/sda1 sector 1939926496)
[367985.321676] BTRFS info (device sda1): read error corrected: ino 7261 off 5636096 (dev /dev/sda1 sector 1939926488)
[367985.321967] BTRFS info (device sda1): read error corrected: ino 7261 off 6029312 (dev /dev/sda1 sector 1939926504)
...

I pulled the drives out of the N5 and tested them in another machine. To my surprise, everything that had been written was perfectly intact. It appears that, at least in my testing, corruption only occurs when data is read from the disks while they are attached to the N5. This bad behaviour persists until the N5 is rebooted. After a restart it can take a few minutes of activity before the controller goes wonky again. I also tried multiple different drive bays; that didn’t change the outcome.

To dig deeper, I reformatted the disks and wrote data to them using a different machine. Then I put the drives back into the N5 and ran a BTRFS scrub across ~1.4 TB of data. The first scrub completed without issues. As soon as I started doing heavier mixed I/O (more than just pure reads or pure writes), corruption started to appear again. A second BTRFS scrub after that showed many unrecoverable errors.

Regarding power: there has been some discussion about the power brick being a potential culprit. I don’t have the right equipment to definitively test it, but for context it is being fed 240 V @ 60 Hz from a double‑conversion online UPS (SRT3000), so upstream power quality into the brick should not be a factor.

I purchased my machine on Sept 27 and received it on Oct 22. When I contacted Minisforum support with all the technical details, I was not offered a refund. Instead, I was told:

It’s great to hear from you, and I hope you’re doing well today! I will be happy to assist you!

In this case, we will provide you with a replacement service. However, your machine is currently discontinued. However, Minisforum offers a trade-in service.

With our trade-in program, you have the option to exchange your existing machine for a new model. You can select the available models in the official Minisforum store and pay the price difference between the discontinued and available models. This way, you can still enjoy the benefits of our latest technology and improvements. If you are interested in this program, I am here to provide you with a detailed description of the process along with all the necessary information.

@xavierl Can you give me your service number. I Will Dealing with this.

@xavierl @buddwm Do you have discord. I want make a directly connect with you.

Could you provide more detailed information?

  1. OS information(System, and Kernel version)
  2. HDD model number
  3. is there software raid enable? or just single HDD format to BTRFS?
  4. How you run your mixed offload test, could you give more details?

Regarding after-sales returns, please provide me with your service order number so I can properly handle this matter for you.

@Jax_Jiang I’ve been in contact with Amber and we were able to sort things out. They’re going to send over a barebone N5 Pro once I ship my unit over.

Curious how you made out with the new unit? I’m using unraid on mine and had drives dropping out and throwing errors. I tried the “fix” from the reddit thread “silent_data_corruption_on_n5_pro_nas” and changed the link speed + disabled aspm and the errors have stopped. I’m hoping that is the end of the issue but am truing to figure out if it’s worth getting another unit or going to the aoostar wtr max. Thanks

@xavierl
if error always happended with “[347523.311655] ahci 0000:c1:00.0: Using 64-bit DMA addresses”

edit /etc/default/grub file
add “iommu=pt”
maybe will fix this issue.

@xavierl
And I’m curious what kind of work load caused this problem.
Is there any pcie card and VMs or a lots of data?

Hi,

Did anyone ever get back to the AOOSTAR? Did it stack up to the promising design?

Hi there.

I had an issue with my N5 Pro spontaneously rebooting after months of problem-free use. I suspect it is related to this issue.

I’m speaking with Ann about a replacement, but I just wanted to check that the issue is being looked into. I don’t want a replacement unit with the same problem.

I asked Ann, but she is just pushing me to accept the return first and telling me she would “need to verify this internally”.

Can you tell me whether you are looking into the issue and should I wait to return my N5 Pro? I moved all the drives into an emergency server and it is all running perfectly, so my Minisforum unit is just sitting empty now.

I’m happy to wait if it means I get a unit where the problem has been verified resolved. It is working as a server in a school and even though backups are taken regularly, there is sensitive data I would rather not lose between backups.

My reference for the RMA is C202601210222 JP35020

Im trying to refund my N5 Pro too, all my brand-new Seagate Disks now have 3 figures or millions of READ and SEEK errors in under 200 hours of power on thanks to this … not sure how reliable the disk are now still …

Does the “AOOSTAR WTR Max” have any problems like this?