Comment on NAS Power Consumption

LeTak@lemm.ee ⁨1⁩ ⁨day⁩ ago

• Onomatopoeia@lemmy.cafe ⁨1⁩ ⁨day⁩ ago

  In my experience using a PC as a NAS, the power draw isn’t necessarily the drives as they spin down when idle.

  I have an old desktop setup as NAS - with 2 drives or eight drives, idle power draw is virtually the same, about 100w, regardless of the OS (Windows, Linux, UnRAID, Proxmox).

  I also have an old consumer NAS, with five 4TB drives, and it idles under 20w (I think last I checked it was ~15w… I need to check it again and write that down).

  Two very similar systems, one designed to be a NAS, the other a desktop. It really comes down to the motherboard design and capabilities.

  And don’t think that SSD drives would do better - spinning disk drives generally have far better idle power than SSD does, and usually much better write power consumption.

  source

  • LeTak@lemm.ee ⁨13⁩ ⁨hours⁩ ago

    Good point. I looked mostly at the spec sheet from the manufacturer and for example the Samsung 870 Evo vs Seagate IronWolf NAS Drive. Side note, AFAIK NVME drives have a higher power consumption. Especially PCIe 5.0.

    My NAS with 2 HDDs from Seagate has a total powerdraw of around 30-40w. And I don’t spin the drives down.

    1. Latency of accessing files/loading times
    2. Lifespan reduction because of spin up / spin down Head moves (the most common for head crash, as I learned from my Teacher)

    source
  • WhyJiffie@sh.itjust.works ⁨1⁩ ⁨day⁩ ago

    And don’t think that SSD drives would do better - spinning disk drives generally have far better idle power than SSD does, and usually much better write power consumption.

    I wonder if they can be “spinned down” like hard drives. their startup time would be much faster, so it’s shutdown could even be on a tighter schedule. I mean probably they dont have an internal idle timer, but who cares if you can just have something like hd-idle that shuts it down according to a better schedule.

    source
  • WhyJiffie@sh.itjust.works ⁨1⁩ ⁨day⁩ ago

    In my experience using a PC as a NAS, the power draw isn’t necessarily the drives as they spin down when idle.

    that’s not always the default setup, especially with enterprise drives. also if you have some kind of monitoring, that can keep the drives from going down (for that, use linux hd-idle instead of drive internal idle timer), and it can also wake them up (for that, prometheus node exporter’s smart collector first checks whether a drive is up, and only then collect stats). Interestingly, checking temps with smartctl always spins up my drives, while linux hwmon can give me live temp stats even while the drives are down

    source
• Bags@piefed.social ⁨1⁩ ⁨day⁩ ago

  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, all 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.

  source

  • WhyJiffie@sh.itjust.works ⁨1⁩ ⁨day⁩ ago

    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.

    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

    source

    • Bags@piefed.social ⁨1⁩ ⁨day⁩ ago

      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!

      source
  • vane@lemmy.world ⁨1⁩ ⁨day⁩ ago

    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.

    source
  • Onomatopoeia@lemmy.cafe ⁨1⁩ ⁨day⁩ ago

    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.

    source

    • Bags@piefed.social ⁨1⁩ ⁨day⁩ ago

      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.

      source