42
NAS Power Consumption
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jun 2025
42 points (95.7% liked)
Selfhosted
46672 readers
641 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
If you can figure out how to get a qnap to spin down its disks, please let me know lol. I've been searching for months and haven't found a reliable solution. I basically only need to access it once a day at MOST, so having the disks spinning away for like 99% of their life sucking down power is something I'd like to avoid. The problem seems to be that even with a perfectly clean slate, no services running, the system set up in their own RAID0 SSD pool, the HDD's, even with 0 bytes of data on them, are being pinged for access at least once a minute. I'm assuming it's some log being written to, but it's not anything visible in the file system, and I haven't been able to find any solution online, lots of people seem to have the same issue.
I'm tempted more and more every day to just grab one of those low-power embedded ITX boards and build up a custom rig. Other than the disk spinning constantly, the TS-462 does everything I need perfectly.
if it's for drive health stats, and the device runs linux, hd-idle could help. it only counts actual block device (so, storage) access as activity
edit: https://github.com/adelolmo/hd-idle
They run a custom vendor-locked distro named QTS, so they're not really as easy to modify as a normal system, I don't think you can even install programs like that.
I'll definitely bookmark it though if I ever get around to building my own solution, thanks!
Wow, QNAPS don't spin down disks? Geez, what a crappy design choice. Thanks for that tidbit, I was considering one for my next NAS.
I have no idea if it's a QNAP-wide issue, or just some specific models, I haven't bothered to do that much research. I'm guessing that the discs WOULD spin down if you have that option selected if they weren't constantly being pinged a couple times a minute. That constant pinging is the part I can't seem to track down.
An excerpt from a post I was reading while researching this sums it up prettt well: "700 posts about spindown/sleep/standby not working in the QNAP HDD Spin Down Forum. No one seems to be able to resolve it. Qnap clearly couldn't care less."
The only solution that I've found that seems to work is to install some other operating system on it, which kind of defeats the purpose of buying a turn-key NAS, and is slightly outside my comfort zone right now. I just ordered a kill-a-watt, so I'll see how much power it's taking with/without drives and go from there if it's worth my time to dive into an OS swap, or building a custom rig.
I remember to have it working with default software I got but it was 10 years ago.
Then they added this bloatware like media streaming addon or notification center. I have now entware with minidlna and set minidlna scanning disk once per day because media streaming was scanning all the time.
I haven't figure out how to permanently kill their /usr/local/sbin/ncd, ncdb, qNoticeEngined, qulogdb, NotificationCenter, mariadb processes. If I figure out it it probably start working again.