USB Guardian

Conservative safe-eject protection for supported USB mass-storage devices managed by Unassigned Devices.

  • Plugins
  • Tools & Utilities
Conservative safe-eject protection for supported USB mass-storage devices managed by Unassigned Devices. USB Guardian grants permission to unplug only after strict identity, usage, unmount, cache-flush, logical-removal, and shfs health checks pass.

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.

41/100 Fair

Maintained
74last commit 64 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 4 days ago

GitHub stars
0
Open issues
0
Last commit
2026-09-18
Latest release
v2026.09.18a
License
MIT
Activity
stale

Checked 4 days ago - source: GitHub (xO-ox-ai/unraid-usb-guardian)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the ready-made ROS 2 package Run the apt-get command from the docs and replace <ros2-distro> with your ROS 2 (robotics software stack) distribution name. This is the safest first step because it brings in the app and its needed pieces without compiling from source. source
  • Start the camera node correctly Use the documented ros2 run command with default settings, or pass your YAML params file if you customize the camera. If you start the wrong command or skip the needed settings, the camera may not come up or may use the wrong device options. source
  • Pick a supported resolution and frame rate Before configuring the stream, check the supported formats list from the node output. Choosing a size or fps the camera does not support can make capture fail or run slowly. source
  • Requirements Requires Unraid 7.2.4 or newer, x86_64, and Unassigned Devices 2025.08.07 or newer. source
  • System requirements Requires Unraid 7.2.4 or newer (x86_64) and Unassigned Devices 2025.08.07 or newer; the plugin performs runtime capability checks against the installed UD version. source
  • Minimum requirements Requires Unraid 7.2.4 or newer (x86_64) and Unassigned Devices 2025.08.07 or newer; source compatibility verified through 2026.09.15. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What checks does USB Guardian run before showing “Safe to unplug”?

It shows safe removal only after normal unmounting, a second usage scan, cache flushing, logical USB removal, and shfs stability checks all pass.

Which USB storage devices are eligible for safe ejection?

Only fully verifiable USB mass-storage devices with a single disk are supported, and only one target mount may be active at a time. LUKS, ZFS, RAID/LVM members, multi-LUN enclosures, composite USB devices with non-storage interfaces, and devices with unproven identity are blocked with a reason.

What Unassigned Devices settings can prevent USB Guardian from ejecting a drive?

UD Share must be disabled for the target partition, UD Destructive Mode must be off, and no disk, partition, User Script, or Common Script configuration may be present.

Does the plugin force unmount or kill processes when a USB drive is in use?

No. It never uses lazy or forced unmounting and never kills processes automatically. If usage cannot be released safely, it stops and leaves the device connected.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads