External drives and daily use
Prepare storage and plan connections, ejection, backups and drive changes.
The external drive becomes the real storage location for moved apps or data. Stable connectivity and enough space matter more than advertised speed. An external SSD is usually better for frequent app launches and small-file access.
Which operations require APFS?
| Task | Storage requirements |
|---|---|
| Mount migration of container data | Currently requires APFS and passing preflight checks. |
| Moving ordinary apps, tool directories or custom folders | Depends on content, filesystem capabilities and permissions; container requirements do not apply universally. |
| NAS or network-mounted location | Connectivity, file attributes and app compatibility vary. It does not substitute for container APFS mount migration. |
You do not need to reformat a whole disk merely to move an ordinary app. If its format is unsuitable for container data, choose another destination or keep that data local. See data migration methods.
Prepare APFS storage
- Back up existing disk contents and inspect device and volume formats in Disk Utility.
- If suitable APFS storage already exists, select it in AppPorts and check again.
- If a format change is necessary, confirm the backup is usable and follow Disk Utility's instructions. Erasing deletes data on the selected object; it is not an ordinary settings toggle.
AppPorts creates dedicated data volumes for mount migration. You normally do not need to create one per directory or assign a fixed size yourself.
Encrypted external drives
2.0.0 can create an independently encrypted data volume on an encrypted APFS destination. After preflight, enter and confirm a new data-volume password before continuing. The volume does not inherit the existing drive password, and existing passwords and files are unchanged. Multiple new volumes in a split WeChat migration share this setup.
The option to save the password in this Mac's Keychain for automatic unlocking is selected by default and can be cleared. Saved passwords remain on this Mac and do not sync. Without a saved password, or when Keychain is unavailable, unlock manually; the background agent does not repeatedly show password dialogs. Passwords are not written to migration records or logs. Unsaved passwords are held temporarily in the process, and may need entering again after quitting. Keep the password safe: forgotten passwords cannot recover encrypted data.
Ordinary unencrypted APFS destinations also work, but someone finding the disk may be able to read the data. Another encrypted volume on the same disk does not encrypt the new volume. Read preflight prompts and confirm the new volume's protection; do not remove existing encryption just to pass a check.
Does the external drive remember file owners?
Some macOS storage does not record file ownership: exFAT and FAT32 have no such field, and HFS+ mounted with ownership ignored writes new files as a placeholder user. Ordinary reads and writes are unaffected, but a few apps that check ownership as an administrator — clash-verge with its privileged service, for example — refuse to work and suggest a chown fix. On such volumes the kernel silently drops that command, so it looks successful while changing nothing.
APFS keeps the real owner even when mounted with ownership ignored, so it is out of scope here. When migrating an ordinary data directory or a custom folder, AppPorts explains the target's situation in the confirmation dialog without blocking the operation. Prefer keeping such app data local, or use an APFS disk; for HFS+ you can untick “Ignore ownership on this volume” in Finder's Show Info and migrate again. exFAT has no such switch.
Everyday connection and disconnection
- Connect the drive before use. Open AppPorts if necessary and confirm Mounted or a working link.
- Save work, quit apps using external data and eject the storage normally before disconnecting.
- After restart or reconnection, automatic reconnection waits for the drive, unlocking and system authorization. It cannot guarantee it will precede every login app.
- Open AppPorts once after moving or updating it so the background task can verify its program location.
Migration is not a backup. Check whether your backup tool covers external storage, especially important messages, projects and personal files.
Space, drive changes and offline storage
Leave room for updates, copies and recovery rather than filling the disk to the current folder size. APFS volumes may share capacity, and available space may take time to update after deletion or restoration.
Before changing drives, restore data locally, then select the new destination and migrate again. Dragging managed data elsewhere or changing volume names or directory structure can break existing entries. If a drive or data connection is missing, start with troubleshooting.
Signature originals on external storage
After manually re-signing an official app, a visible AppPorts Backups folder may appear externally. AppPorts automatically selects a suitable drive for complete official originals. Its README.txt explains the purpose and consequences of deletion. This also applies when the installed app remains internal. Connect the drive that holds the original for recovery and keep the folder in place.
Originals do not contain personal data and are not a separate disaster-recovery backup. Re-signing an internal app still needs temporary space; internal originals are removed only after a cross-volume save is verified. See signature originals for selection, inspection and cleanup.
Evidence: unexpected disconnection and restart and automatic reconnection.
Eject the entire external disk from AppPorts
- Save work, quit programs using apps or data on the drive, and wait for active file operations to finish.
- In the external-storage area's eject menu, choose Eject External Disk. This targets the entire physical disk and all its volumes, including dedicated volumes mounted at local data paths, rather than only the selected app library.
- AppPorts pauses automatic mounting for that disk before asking Finder to eject it. Sending the request does not mean ejection has completed. Confirm the system result and menu state before unplugging.
- If volumes remain mounted or the system refuses, quit programs using them and choose Retry Eject. Do not pull the cable to force ejection.
Automatic mounting stays paused after an explicit eject request, even if Finder's ejection is cancelled or all volumes have unmounted. Unplug and reconnect the device; mounting resumes after a new connection of the same disk is recognized. Refreshing the list, reopening AppPorts or waiting for a timeout does not replace reconnection. There is no manual button to cancel the pause and resume mounting. For permission errors, check Finder automation permission and keep the message.