Volume Management
What this section does
Section titled “What this section does”This chapter explains volume eligibility, identity matching for selected drives, and ignore/eject behavior.
Auto-detection rules
Section titled “Auto-detection rules”A volume is considered eligible when it matches removable/ejectable/local criteria and is not explicitly excluded.
Always excluded:
- virtual drives,
- ignored volumes,
- startup/system volume.
Volume identity for selected drives
Section titled “Volume identity for selected drives”When you choose a specific drive, matching priority is:
- Volume UUID
- Display name
- Security-scoped bookmark fallback
Ignored volumes vs hidden volumes
Section titled “Ignored volumes vs hidden volumes”- Ignored volumes: explicitly skipped during transfer runs.
- Hidden volumes: hidden in settings UI but not a transfer-skip flag by itself.
Eject behavior
Section titled “Eject behavior”- Eject action runs per detected removable drive.
- Failures are collected and shown after attempts complete.
- Eject is blocked while transferring.
- Use ignored volumes for always-on exclusions (backup disks, archive media).
- Keep selected-drive rules for stable, repeatable ingest workflows.
What if metadata can’t be read for a volume?
Section titled “What if metadata can’t be read for a volume?”Fallback behavior treats the volume as eligible instead of silently excluding it.
Why does selected drive sometimes fail?
Section titled “Why does selected drive sometimes fail?”If the chosen drive is not mounted, the run summary reports the missing mount state.
Related guides
Section titled “Related guides”Need help?
Section titled “Need help?”For setup support, contact rockstarui.com/contact.