[ulnarkressty]

The article is right, if you need a (very) low power server the rpi is unbeatable. I have tried a lot during the years to make it as robust as possible, however I find that there is only a matter of time until a power failure, regular update or even a simple reboot will render a pi unusable. And you'll be powerless to fix whatever flavor of boot error is occurring half a world away. Never had these kinds of issues with regular servers. Perhaps if there was a way to "boot to ssh" to fix these...

Some recommend the miniPCs from Dell, Fujitsu etc. But they also have custom firmware with their own set of problems and strange design decisions which you won't be able to change if you needed to.

[sangnoir]

I never had a breaking update on Raspbian. However, I have run into write errors caused by power failures that required an fsck on the SD from a different computer: I now have a `@reboot touch /forcefsck` cronjob, but it may just be a talisman (IIRC, dirty filesystems get a fsck automatic at boot)

Have you considered read-only boot & system partitions? That way, your pi will always boot, at the cost of have to remount in read/write mode to perform updates.