Troubleshooting

"Full Disk Access Required"

The privileged helper hit a permissions wall mounting into a macOS-protected location (Desktop, Documents, Downloads, and similar). Click the alert's button (or open System Settings › Privacy & Security › Full Disk Access) and enable access, then retry the mount. Alternatively, move the volume's folder to an unprotected location — directly under your home folder works.

"This location can't be used" for a folder inside ~/Library/Containers

~/Library/Containers and ~/Library/Group Containers are managed by the macOS sandbox subsystem. Since macOS 14, mounting over anything inside them is denied by the OS at a level Full Disk Access cannot override. This is a hard macOS restriction, not an app limitation. If you were trying to speed up a sandboxed app's container: not possible via this route — choose a folder outside those trees.

The app says the helper isn't available / mounts do nothing

The privileged helper was never approved, or macOS disabled it (this can happen after some updates, or if the app was moved on disk). Check System Settings › General › Login Items & Extensions and make sure the Persist helper is allowed to run in the background. If it's already enabled, toggle it off and on, then relaunch the app. Moving the app back to /Applications and relaunching also forces a clean re-registration (the app re-registers the helper whenever its binary changes).

"Save finished, but the on-disk copy could not be refreshed" (or similar save errors)

The save's final step — mirroring the saved snapshot into your folder — failed. Your data is safe in the app's snapshot and the app now treats that snapshot as authoritative until a save succeeds (details: Data safety). Typical causes and fixes:

• Permissions / locked files — the app already auto-clears the Finder "locked" flag and retries once; if it still fails, check ownership of the folder and its contents.
• Disk full — free space on the volume that hosts the folder.
• Full Disk Access — if the folder is in a protected location.

After fixing the cause, mount and eject the volume once; a clean save clears the condition.

A sync ended with "interrupted"

The RAMDisk disappeared out from under a running sync — usually a force-eject or external unmount mid-save. Whatever was copied before the interruption is in the snapshot; the rest was lost with the RAM contents. Syncs are incremental and self-consistent, so nothing is corrupted — the next successful save simply completes the picture from whatever is in RAM then.

Eject hangs at "waiting on ⟨app⟩"

That app refuses to quit — most often because it's showing its own unsaved-changes dialog. Bring the app forward and answer its dialog, or use the row's Force Quit button (which discards that app's unsaved state). A shell with its working directory on the volume also blocks eject; cd elsewhere and the eject proceeds.

My files look different between the mounted disk and the folder

Check the timing before assuming loss:

• While mounted, the path shows RAM contents; the folder underneath is hidden and only as fresh as the last completed save.
• While unmounted, the path shows the folder — which is exactly what the next mount will start from, including any deletions you made.
• A handful of hidden macOS metadata files are never synced in either direction (list in How it works).

If files you expect are in neither place, check the snapshot and the quarantine folder before anything else: ~/Library/Application Support/RAMDiskManager/sync/<name>-<id>/latest-content/snapshot/ and ~/Library/Application Support/RAMDiskManager/recovered/.

Can I delete things inside ~/Library/Application Support/RAMDiskManager myself?

While the app isn't running, and with care:

• sync/<name>-<id>/ folders for volumes you've already deleted are safe to remove (normally the app cleans these up itself).
• Never delete a sync/ container that contains a mirror-pending.json file — that snapshot is the only copy of a session whose save didn't complete.
• recovered/ entries are yours to triage: rescue what you need, then delete.
• Don't hand-edit registry.json; use the app to add and remove volumes.

Does the app phone home? What telemetry is sent?

The app can send crash reports and diagnostic events (error types, feature usage signals) to help fix bugs. This is gated by the analytics consent setting in the app — turn it off and the app sends nothing. File contents are never transmitted in either mode.