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.