← Directory

Disk Usage (duc)

An Unraid plugin that packages duc to index shares and disks on a schedule, then browse disk usage instantly from the webGUI without rescanning disks every…

  • Plugins
  • Tools & Utilities
An Unraid plugin that packages duc to index shares and disks on a schedule, then browse disk usage instantly from the webGUI without rescanning disks every time. duc stores the results in a database, so browsing is instant and the disks are not rescanned until the next index run. Browse from the webGUI under Settings, User Utilities, Disk Usage, with a sunburst chart and a sorted folder listing showing size on disk, apparent size or file count. Index several roots at once, for example /mnt/user for usage per share and /mnt/disk1 or /mnt/cache for usage per disk. The full duc command line is included too, including the duc ui terminal browser. Note: an index run reads directory metadata on every disk it covers, so spun-down disks will spin up during a run.

Platform availability

Available on 1 of 9 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)

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.

43/100 Fair

Maintained
72last commit 16 days ago
Popular
102 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

GitHub stars
2
Open issues
0
Last commit
2026-10-06
Latest release
2026.10.05
License
MIT
Activity
rising

Checked 2 days ago - source: GitHub (jamesfreeman959/unraid-duc)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the build cache package first Run `npm install --save-dev expo-build-disk-cache` in your project, where npm is the package manager used to download needed tools. This installs the disk-cache plugin so build files can be saved locally and reused instead of being rebuilt from scratch. source
  • Set the cache folder where files go Set `cacheDir` in `disk-cache.json`, `app.json`, or `package.json` to a folder with enough free space. This tells the tool where to store cached build files, so you can clean them up later and avoid surprises from large files. source
  • Keep personal cache settings local If you use Git, put machine-specific settings in `disk-cache.json` and keep that file ignored by version control. This stops your local cache folder choice from being committed and confusing other people’s machines. source
  • Browse results after install After installing the plugin, the duc index runs on a schedule, and results can be browsed under Settings, User Utilities, Disk Usage in the Unraid webGUI. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I index multiple paths such as all shares and individual disks at once?

Yes. You can index several roots, for example /mnt/user for usage per share and /mnt/disk1 or /mnt/cache for usage per disk. Paths are stored comma separated, so paths containing commas are not supported.

Will a scheduled index spin up disks that have been spun down?

Yes. An index run reads directory metadata on every disk it covers, so spun-down disks will spin up during the run. The docs suggest scheduling the index for a time when that is acceptable.

Where is the duc database stored, and should it be placed on the Unraid flash drive?

By default it is stored at /mnt/user/appdata/duc/duc.db. The docs advise keeping it off the USB flash drive because it is rewritten on every run. If the database folder is unavailable, such as when the array is stopped, the run is skipped.

Is the old index still available while a new index is being built?

Yes. The previous index stays browsable while a new one is built. The new database only replaces the old one once indexing has finished.

Can I use the terminal duc browser with the plugin database?

Yes. The full duc CLI is included, including the ncurses browser. You can run duc ui against the plugin database, for example to browse /mnt/user.

Answers sourced from github.com

Community

Collected yesterday - public community threads