Disk Talkers

Disk Talkers is an Unraid plugin that identifies the apps, containers, VMs, and host services touching your disks, surfaces /mnt/user and array-backed mounts…

  • Home Automation
  • Plugins
  • Tools & Utilities
Disk Talkers is an Unraid plugin that identifies the apps, containers, VMs, and host services touching your disks, surfaces /mnt/user and array-backed mounts that may cause avoidable spin-ups, and provides lightweight historical attribution with estimated energy and cost.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
83last commit 40 days ago
Popular
61 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 4 days ago

GitHub stars
1
Open issues
1
Last commit
2026-10-12
Latest release
2026.10.12b
Activity
stale

Checked 4 days ago - source: GitHub (silkyclouds/unraid-disk-talkers)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the cache plugin first Run npm install --save-dev expo-build-disk-cache in your project folder. Without this step, Expo can’t find the disk-cache plugin and your builds won’t be cached locally. source
  • Choose where cached builds are saved Set cacheDir in app.json, package.json, or disk-cache.json to choose where cached app builds are saved. If you skip this, the cache may use a default location that is easy to lose track of, and local-only settings can accidentally get shared if you do not ignore them. source
  • Optional: connect EAS remote cache If you use EAS cloud builds, add remotePlugin: "eas" to the cache options so cached build pieces can be reused in remote builds. Without this, remote builds may not reuse the cache and can take longer. source
  • Prerequisite Install Python 3 for UNRAID (6.11+) from Community Applications before using Disk Talkers, or install it afterward and refresh Disk Talkers. source
  • Install prerequisite Install the 'Python 3 for UNRAID' plugin (version 6.11 or newer) from Community Applications before using Disk Talkers, as it is a required dependency; if installed afterward, refresh the Disk Talkers page. source
  • Prerequisite: Python 3 for UNRAID (6.11+) Requires the 'Python 3 for UNRAID' plugin (version 6.11+) on the Unraid host. Install it from Community Applications first — or install it afterwards, then refresh the Disk Talkers plugin before it will work. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where does Disk Talkers show up in Unraid after installation?

It adds a dedicated WebUI page to Unraid. This page shows which containers, VMs, or host services are probably keeping each array disk or pool busy.

Can it identify host-side activity as well as apps and containers?

It is intended to show which apps, containers, VMs, or host-side activity are touching your storage. It helps make it easier to see what may be keeping array disks and pools spun up.

Does Disk Talkers include pools, not only array disks?

Yes, it reports per-disk activity for array disks and pools. It can show what is probably keeping each array disk or pool busy.

Does it flag /mnt/user or array-backed mounts that can cause extra spin-ups?

It can surface /mnt/user and array-backed mounts that may be causing avoidable spin-ups. This is part of its goal to help reduce unnecessary storage access.

Does it provide estimated energy and cost from disk activity?

It provides lightweight historical attribution with estimated energy and cost. This gives a rough estimate tied to disk usage history.

Answers sourced from ca.unraid.net, forums.unraid.net, github.com

Community

Collected 48 days ago - public community threads