Cache / Array Share Control

Cache / Array Share Control is an Unraid 6.12+ plugin that gives each user share three explicit, mutually exclusive choices: Cache -> Array (primary on the…

  • Cloud
  • Plugins
  • Tools & Utilities
Cache / Array Share Control is an Unraid 6.12+ plugin that gives each user share three explicit, mutually exclusive choices: Cache -> Array (primary on the chosen pool, secondary Array), Cache only (primary on the chosen pool, no secondary), or Array only (runs Mover first, verifies every mounted pool is clear, with an optional Force remaining transfer for stubborn leftovers, before applying the policy). It uses Unraid's native /update.htm share-update interface, creates a timestamped backup before every batch, verifies every applied change, rolls back completed changes if a later share fails, and can restore the most recent un-restored batch. It never runs Mover automatically outside of an Array-only operation.

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.

42/100 Fair

Maintained
77last commit 56 days ago
Popular
00 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 3 days ago

GitHub stars
0
Open issues
0
Last commit
2026-09-26
License
GPL-3.0
Activity
stale

Checked 4 days ago - source: GitHub (RayMunro/unraid-cache-array-share)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Add Cache with Carthage Put github "hyperoslo/Cache" in your Cartfile so Carthage can download the library, and add SwiftHash.framework to your copy-frameworks step (the Xcode part that copies helper libraries) so your app can link it at launch. source
  • Set disk and memory limits first Create your storage with a DiskConfig and MemoryConfig before saving anything. These settings tell the cache how much disk space and memory it may use, so it does not grow without a limit. source
  • Old files are deleted when full DiskConfig’s maxSize is a ceiling: once the disk cache gets bigger, it removes expired items and then the oldest files until it is at most half of that size. So only cache things that are safe to re-download or rebuild later. source
  • Install Requires Unraid 6.12 or later. Install the plugin from the Unraid Community Apps store, then manage each user share's storage policy (Cache to Array, Cache only, or Array only) from the plugin interface. source

Fetched 46 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does the plugin run Mover automatically for every share change?

No, it never runs Mover automatically outside of an Array-only operation. For an Array-only selection, it temporarily sets the shares to Pool -> Array, starts Unraid's global Mover, and waits in a background job.

Does switching a share to Cache-only move files already on the Array?

No, Cache-only directs new writes to the chosen pool and does not move existing Array files onto the pool. In a mixed operation, those shares are not included in the post-Mover remaining-files check for Array-only shares.

How does the plugin protect share settings before applying changes?

It creates a timestamped backup of the original share policies before every batch and verifies every applied change. It can restore the most recent un-restored batch.

Do I need to stop Docker and VMs before using Force remaining?

Yes, stop Docker and VMs before forcing files so an application cannot modify a file while it is being transferred. Docker containers or VMs can keep files open and cause files to remain on the pool.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads