dividido

I was rocking an i5-10600 but fell into some ecc sodimms, so was trying to migrate onto a platform that supports it. There aren't a ton of options unfortunately and diy costs exceeded these pre-builts. Hopefully the aoostar is reliable.

Sorry to hear that @AlexHackney - I've also returned my n5 pro as I need my nas to be rock solid. I have an aoostar wtr max on order to see how that goes. At least it has the better sata controller (ASMedia ASM1166) vs what the n5 pro has and is the cause of these instabilities (JMicron JMB585).

Got it! Just realized I had that from my last system - disabled this user script and hopefully smooth sailing from here.

Thanks @JorgeB - could this be caused by a startup script running the following? powertop --auto-tune &>/dev/nullThe psu is an external 280w adapter included with the system.

And now a 3rd drive is showing read errors. Hopefully I'm not spamming you thehive-diagnostics-20260119-1046.zip

Hmm that was a no go - both drives 1 and 3 are showing the same count of errors 😥 thehive-diagnostics-20260119-1022.zip

Thanks I restarted and 1 drive was missing ☹️, then powered off and reseated them after using a dust blower. I'll report back after running today. Thanks again and hopefully it was as simple as that.

Thanks for the reply! Yes, all 3.5" drives are on the motherboard controller. No power splitters or external cabling - it's all using the built in 5 hdd bays. I have a pcie card adding bifurcation for two WD Red nvme's for cache drives - but not seeing any errors/issues with them.

Hi! I just migrated my unraid setup from a custom server to a minisforum n5 pro and am running into drive errors. The drives themselves are all passing smart tests and I didn't have this problem in my old system. I'm new to diagnosing unraid errors, and tried with gemini and was hoping to get some opinions. It's suggesting a possible hardware issue and opening a support case with minisforum was my next step. Thanks in advance! Based on the logs you provided, the good news is that your hard drives (Disk 1 and Disk 3) appear to be physically healthy. The errors you are seeing are not caused by failing disks, but by a critical connectivity or power failurebetween the drives and your Minisforum N5 Pro. 1. Diagnosis: Controller or Power FailureThe most telling evidence is in your syslog.txt. Both drives are reporting a limit=0 error: Jan 19 02:03:03 TheHive kernel: sde: rw=0, sector=..., nr_sectors = 8 limit=0 Jan 19 02:03:03 TheHive kernel: md: disk1 read error, sector=... Jan 19 02:03:03 TheHive kernel: md: disk3 read error, sector=... In Linux, a limit=0 error means the operating system suddenly believes the drive has a capacity of zero sectors. This almost always happens when a drive completely disappears from the SATA bus while the system is trying to read from it. Because this is happening to multiple drives (Disk 1 and Disk 3) at the exact same time, the issue is not the individual drives, but something they share: the SATA controller, the cabling, or the power supply. 2. SMART Health AnalysisThe SMART logs for both drives show them to be in excellent condition: Disk 1 (sde - 12TB WD): Has 0 reallocated sectors, 0 pending sectors, and 0 UDMA CRC errors (which would indicate a bad SATA cable). Disk 3 (sdf - 14TB WD): Also has 0 reallocated sectors and 0 pending sectors. High Reset Count: Both drives show a relatively high "Number of Hardware Resets" (367 and 372), which suggests they have been forcefully power-cycled or dropped many times previously. thehive-diagnostics-20260119-0817.zip