[geerlingguy]

That's addressed in the second section of the article:

> I've found numerous times, running modern applications on slower hardware is an excellent way to expose little configuration flaws and misconceptions that lead to learning how to run the applications much better on more capable machines.

It's less about the why, and more about the 'why not?' :)

I explicitly don't recommend running TrueNAS on a Pi currently, at the end (though I don't see a problem with anyone doing it for the fun, or if they need an absolutely tiny build and want to try Arm):

> Because of the current UEFI limitations, I would still recommend running TrueNAS on higher-end Arm hardware (like Ampere servers).

[esskay]

On a somewhat related note, would you trust a Pi based NAS long term? I've not tried doing one since the Pi 4 which understandably because of its hardware limitations left a lot to be desired, but that part aside I was still finding the pi as a piece of hardware somewhat quirky and unpredictable - power especially, I can't count the number of times simply unplugging a usb keyboard would cause it to reboot.

[geerlingguy]

I've run a Pi NAS as my 2nd onsite replica for over a year without a hiccup, it's using a Radxa Penta SATA HAT with 4x SATA SSDs, and a 2.5 Gbps USB dongle for faster Ethernet[1].

[1] https://www.jeffgeerling.com/blog/2024/radxas-sata-hat-makes...

[ycombinatrix]

totally agree. it becomes extremely obvious when applications are poorly optimized or have outdated build systems that don't support ARM.

imo, if the software doesn't work without issue on my Pi, it isn't good enough for prod.