4 ms·
Ugh. Agree with this. My Synology NAS was failing. Saw that as a great opportunity to set up a proxmox box on a reasonably powerful used HP SFF, run TrueNAS on
by bdavbdav 3y ago
Ugh. Agree with this.
My Synology NAS was failing. Saw that as a great opportunity to set up a proxmox box on a reasonably powerful used HP SFF, run TrueNAS on it. Plenty of time to get proxmox, TrueNAS, Gitea, a docker host, … just right.
It’s sat there with 4/16TB used, no real data transfer apart from TimeMachine from my Mac and my git server, sucking power at European rates.
Wish I hadn’t bothered, and had just gone with another Synology.
- sangnoir 3y ago> It’s sat there with 4/16TB used, no real data transfer apart from TimeMachine from my Mac and my git server, sucking power at European rates I have a similar setup with SFF running backups & ProxMox. However, I have smart plugs for my SFF and have a script to turn it on/off using cron (or on demand) from an always-on Pi. Wake on LAN would have worked too. I'm considering making my Raspberry Pi the gateway proxy/"Load Balancer" to the SFF; turning it on if needed. It's trivial to proxy HTTP (Pi works as a Caddy-based proxy with long timeouts, powers on SFF in background if off. Things got trickier for proxying NFS & iSCSI)
- bdavbdav 3y agoThis is a genius idea. I may try similar. The box is on another routed subnet - I wonder if I could firewall rule a “start” trigger.