I think for me spin-down was working initially. But then I added some Docker containers and those could only be run on the HDDs, blocking spin down. With Debian I just put the containers on the smaller SSD, allowing the HDDs to spin down.
- 0 Posts
- 5 Comments
I like being able to drop in whatever disk I need to for expansion or replacement.
I didn’t move that far away (to Debian + ZFS), so that limitation still remains. Although the addition of Raid-Z expansion should alleviate things quite a bit.
My NAS/home server takes about 180 kWH/year, or 20W on average (costs me about 5 Euro/month). This feels like a lot to me and makes up a good chunk of my total energy usage.
What I did to optimize it is mostly select a “low-power” x86 platform, and limit the number of disks. I also decided not to use TrueNAS because it couldn’t let the disks from going to sleep.
The machine hosts 10 TB of usable storage (+RAID 1), syncthing, immich, file server, Influx DB, Grafana, and a few other services.
stuner@lemmy.worldto
Linux@lemmy.ml•Canonical Announces Official Ubuntu Desktop Images for RISC-V
9·11 days agoThe kernel has supported it for a few years now and it’s a supported architecture for Debian.
For me, the main thing holding me back from getting a RISC-V SBC/computer is the lack of high performance processors. But they seem to be making progress there too.

And it’s like 5 sentences apart in the article xD