23 ms·
I have a similar home setup, but don’t recommend using Pis for disk-intensive workloads due to SD Card volatility. My HomeKit setup, for instance, is Dockerized
by rcarmo 8y ago
I have a similar home setup, but don’t recommend using Pis for disk-intensive workloads due to SD Card volatility. My HomeKit setup, for instance, is Dockerized and runs on an ODROID board with EMMC storage, and the build server for my ARM containers boots from an SD card but has an USB hard drive.
- fallenhitokiri 8y agoAt this point I would not recommend using PIs for anything long running at all. I have two v3 and one v2 and all of them crashed at some point, one of the v3 was idle during that time. The one PI I still run as build server operates of a write protected SD card and reboots regularly. I am not 100% sure why the PIs crashed yet (still have to do the investigation), but if errors like this already show up in a server rack with AC attached I'm a bit skeptical.
- 8fingerlouie 8y agoThe usual suspect when i comes to Pi SD Card corruption is a bad power supply. The Pi will (attempt to) draw more power than it can, resulting in a corrupted SD card. I've also run a large part of my internal network on RPis, but have since moved to Intel NUC machines, where i replaced a bunch of Pis with 2 NUCs. Storage like you has always been handled on a NAS. Synology in my case. I don't have need for much computing power, so the NUCs handle that just fine. See my other comment : https://news.ycombinator.com/item?id=17966507 https://news.ycombinator.com/item?id=17966507