Disk Location Next

Disk Location Next is a Unraid plugin that maps each drive to its physical bay, hot-swap tray, or PCIe NVMe carrier on a visual tray map, with per-drive…

  • Infrastructure
  • Monitoring & Logging
  • Plugins
  • Tools & Utilities
Disk Location Next is a Unraid plugin that maps each drive to its physical bay, hot-swap tray, or PCIe NVMe carrier on a visual tray map, with per-drive array/pool role, capacity, manufacturer branding, and SMART health history over time. A ground-up rewrite of the original Disk Location plugin concept, it runs as a standalone Node.js service against Unraid's native unraid-api (Unraid 7.2+) instead of a classic PHP webGUI plugin.

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.

48/100 Fair

Maintained
82last commit 16 days ago
Popular
123 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 39 days ago, links checked 4 days ago

GitHub stars
3
Open issues
0
Last commit
2026-11-05
Latest release
v2026.11.05
License
MIT
Activity
declining

Checked 4 days ago - source: GitHub (joshmans/unraid-disklocation-next)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the npm package first Run `npm install --save-dev expo-build-disk-cache` in your project folder. npm is the tool that installs project packages; without this step, the disk-cache feature has nothing to hook into. source
  • Tell the cache where to save files Add a `cacheDir` setting, such as in a `disk-cache.json` file with `node_modules/.expo-build-disk-cache`. That folder is where cached builds live; if the path is missing or wrong, caching can't find or store previous builds. source
  • Keep machine-only settings local If you use Git (the code-sharing tool) and your `disk-cache.json` contains a local path, leave that file out of Git. That stops one computer's folder choice from overriding another person's setup. source
  • Requirements Requires Unraid 7.2+ for the native unraid-api. source

Fetched 46 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I import my layout from the original Disk Location plugin?

Yes, if the classic plugin is still installed. It matches its saved tray assignments to currently connected drives by recomputing the identity hash and previews the match count before changing anything.

How can I find a specific physical drive?

Use the Locate button on an unassigned or already assigned drive. It blinks the real drive's activity LED via repeated smartctl queries.

Can I add my own tray or PCIe carrier graphics?

Yes, tray skins and PCIe carrier shells are plain SVGs you can add to without touching code.

How is the SMART history collected?

It uses periodic smartctl polls to chart temperature, power-on hours, and sector counters. A drive in standby is never woken just to sample it.

Can I restart the service or change its port if it is down?

The Settings tab can start, stop, or restart the daemon and change the listening port even when the daemon itself is down.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads