• v0.2.0 77929de645

    nosignal released this 2026-06-04 15:28:39 +00:00 | 1 commits to main since this release

    Drives on a headless Jellyfin box ran hot 24/7: NAS-class drives (WD
    Red, IronWolf) ship with no idle timer at all. v0.1.2 stopped tuistream
    from keeping them awake; this makes them actually go to sleep.

    Spin-down is a DEFAULT, not a feature: when the inventory shows
    spinning media drives, the TUI silently installs/syncs the mechanism
    and flashes what it did. [s] on Setup is the opt-OUT, remembered via
    /etc/tuistream/spindown-off so the default never fights the user.

    The mechanism is a tiny systemd service (tuistream --spindown-watch)
    that samples /proc/diskstats and issues hdparm -y to any target drive
    idle past 3 minutes. We deliberately do NOT use the drive's own standby
    timer (hdparm -S): the 10TB helium WD Reds advertise it and then ignore
    it — verified on real hardware (fresh -S 36, zero I/O, four minutes,
    still active/idle). Forcing standby from outside works on everything.
    An rc shipped the udev+hdparm -S approach; the plans clean its rule up.

    Safety: targets are spinning (sysfs rotational), top-level, real disks,
    never a system disk — same classifier the rest of Setup trusts. The
    watcher's own probes can't disturb drives: /proc/diskstats and sysfs are
    kernel memory, and hdparm -C (CHECK POWER MODE) doesn't wake or reset
    anything. The unit's ExecStart points at the running binary and the
    auto-sync rewrites it when the content goes stale (e.g. binary moved
    from a dev path to /usr/local/bin).

    hdparm joins the dependency pre-flight. Verified end-to-end on moviebox
    (2x WD Red 10TB SATA + IronWolf 10TB USB): auto-applied on launch, all
    three drives reached standby after 3 idle minutes, Monitor shows them
    as "asleep" without waking them.

    Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

    Downloads