Disk Identificator
A Unraid plugin that lights up the identification (locate) LED of a drive bay from the web UI so you pull the right disk.
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.
40/100 Fair
- Maintained
- 72last commit 12 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
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-10-10
- License
- GPL-2.0
- Activity
- rising
Checked 2 days ago - source: GitHub (vanarebane/unraid-disk-identificator)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Install the disk cache package In a terminal, run npm install --save-dev expo-build-disk-cache, where npm is the package manager for Node.js. Without this step, the disk cache plugin is not available and your builds will not use it. source
- Choose a safe cache folder Set cacheDir in disk-cache.json, app.json, or package.json to a folder on your machine that you plan to keep safe. This folder stores the cached build files, so if it is deleted or moved, the cache can break and you may have to rebuild. source
- Optional: add EAS remote cache If you build with EAS, set remotePlugin to "eas" in the buildCacheProvider options. This is optional and mainly helps remote builds reuse cached pieces, but local disk caching works without it. source
- Configure LED settings After installing, go to Settings > User Utilities > Disk Identificator to set the LED colour per enclosure, remap slots to LEDs if backplane cables are crossed, and add a location label for each bay. ID buttons then appear on the Dashboard and Main pages. source
Fetched yesterday - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need to install Broadcom's sas2ircu or sas3ircu separately?
No. The Unraid plugin package installs both bundled utilities to /usr/local/bin. Nothing is downloaded from third-party sites.
How do I map the ID buttons if the backplane LED cables are crossed?
Use Slot to LED mapping in Settings > User Utilities > Disk Identificator to choose which LED sits on each bay. Click Test to check the mapping.
Does the plugin know which LEDs are on after a reboot?
No. The utilities cannot read LED state back, and the plugin's memory of which LEDs it turned on is lost on reboot.
How do I refresh the drive list after adding a disk?
The controller and drive list is cached for 10 minutes. Click Rescan in the plugin settings to refresh it.
How does it match a Unraid disk to the physical slot?
It matches the disk to a slot using the SAS address from the HBA utilities. If that fails, it falls back to the serial number and then the WWN.
Answers sourced from github.com
Community
No community discussions collected yet.