Troubleshooting

Troubleshooting

Start by confirming the installed version/channel, hard-refreshing after updates, clearing unintended filters and rescanning. Preserve the exact message and affected workflow.

Symptom	Likely explanation and next step
Too many candidates	Check automatic/manual source roots, stopped-container inventory and Compose verification; compare Details before acting
Expected folder missing	Check filters, ignores, source coverage, saved-template and installed-container references; discovery is not an unrestricted recursive file finder
Blocked with Safe Mode off	Permanent-delete mode does not override ownership, protected paths or incomplete inventory
Broad file-manager mounts appear in Details	Mounts strictly above sources are informational; find the specific blocking reason instead
Source itself is mounted by a container	This remains protective, even if you consider that container a general-purpose viewer
Unverified rows	Inspect Docker/Compose availability and diagnostics reason codes; resolve the issue, then rescan
Selection expired	Scan snapshots expire or belong to a prior session; rescan and reselect
Busy/locked operation	Wait for the current operation and inspect progress/History; do not delete lock files to force overlap
Size still loading/unknown	Calculation is deferred or failed; unknown is not zero
Very old folder timestamp	Directory modification time does not prove contents are unused
Quarantine failed	Check reported path/rename, availability and filesystem conditions; no cross-filesystem backup-copy fallback is promised
Space did not increase	Quarantine moves data; ZFS snapshots/shared blocks may retain space after deletion
Restore conflict	Use skip, suffix or a reviewed new name; do not overwrite the existing destination
Quarantine entry missing	Investigate storage availability and external moves/deletions; do not manufacture registry/marker records
Scheduled purge did not run	Check active deadline, clock, hourly worker, lock contention and paused failure state
Dataset cannot quarantine	Exact ZFS datasets require separately confirmed destruction; see the ZFS guide
Dataset resolution fails	Verify real mountpoint and mapping; a user-share path is insufficient
Template cannot archive	Installed ownership or template revision may have changed; refresh the manager
Template cannot restore	Original filename may already exist; preserve both configurations and review
Wrong theme or stale buttons	Confirm native theme, hard-refresh, close/reopen dialogs and test without conflicting browser overrides
Some text remains English	Check selected Unraid locale and fallback; logs/diagnostics/machine identifiers intentionally remain literal
Export is partial	Read section status and limits; expected caps differ from required collector failures
Request timed out during cleanup	The server may have continued; check History and actual state before retrying

Reporting unresolved problems

Download fresh diagnostics after reproducing. Include plugin version/channel, Unraid version, browser, action and expected/actual outcome. Use sanitized examples for source/mount relationships.

A useful report says “Safe Mode on → select one Discovery folder → Dry run succeeds → Quarantine returns [message]”, rather than only “delete broken”.

Avoid reinstalling as a first troubleshooting step when tracking or template backups matter. Removal deletes plugin configuration. See Installation and Updates and Diagnostics and Privacy.