Mac can open files yet cannot add new files to portable SSD. A partial failure matters: one capability still functions, while a closely related step does not. This guide focuses on isolating that difference in storage and backups, not on indiscriminate resets. Use the known-good behavior as your control, change one variable at a time, and retest the original scenario after each intervention.
Practical six-point diagnosis
- Reproduce: Mac can open files yet cannot add new files to portable SSD.
- Compare: Identify filesystem format in macOS Disk Utility without erasing.
- Check: Drive formatted NTFS and macOS mounts read-only, without adjusting unrelated settings.
- Check separately: Permissions prevent writes.
- Correct: Use compatible read/write format for future files or approved software after safely copying data.
- Verify: Files can be safely copied both directions using supported arrangement.
Baseline test: Identify filesystem format in macOS Disk Utility without erasing. Record the current device model, OS or firmware version, and whether this occurs with one file, account, network or source. A reproducible contrast is more informative than a vague message such as “not working.” If the control fails too, stop treating this as a feature-specific problem and investigate the shared dependency first.
Possible explanations
| Hypothesis | Evidence worth checking | Next decision |
|---|---|---|
| Drive formatted NTFS and macOS mounts read-only | Compare a harmless test file with the affected storage item and inspect available capacity and mount state. | If the control still works, focus on the affected path rather than resetting the whole device. |
| Permissions prevent writes | Inspect the permission, account or entitlement attached to this feature, without changing any other user profiles. | If this condition is not present, leave the associated setting unchanged. |
| File system reported errors | Compare a harmless test file with the affected storage item and inspect available capacity and mount state. | Only escalate to this branch if the simpler comparison did not explain the failure. |
Choose the appropriate route
Route A — Correct the observable mismatch
Use compatible read/write format for future files or approved software after safely copying data. Start only after capturing the baseline. When the recommended control is not present on your model, look for its supported equivalent in the product documentation rather than following screenshots from another version.
Return immediately to the failing task and check whether the outcome changed. If it did, preserve the working setting and avoid piling on additional changes. If it did not, undo the change where appropriate before moving to deeper checks.
Route B — Test the underlying dependency
Compare second known-good drive and Disk Utility First Aid report before changes. This advanced comparison is worthwhile only if the simple check did not resolve the problem. The first two possibilities to separate are drive formatted NTFS and macOS mounts read-only and permissions prevent writes. Do not interpret their presence as proof of a diagnosis; a compatible device and a partially failed service may coexist.
Route C — Handle a limitation or persistent fault
A third explanation is file system reported errors. Check whether the feature requires particular hardware, account privileges, region settings or source formats. When a feature is unsupported, there may be no legitimate settings-only fix; use the vendor-documented alternative rather than an unsafe workaround.
Protect your setup: Never erase or reformat until independent verified backup exists. Protect the only copy of data first. For disks, cards and backups, do not format, repair in place or delete historical copies before independently verifying a backup.
Step-by-Step Troubleshooting
Follow the Beginner steps first. Advanced steps are for isolating hardware, application or network-specific causes after a safe baseline test.
Confirm the boundary
Mac can open files yet cannot add new files to portable SSD. Do not assume this is a complete outage. Identify filesystem format in macOS Disk Utility without erasing. Keep the account and connections unchanged between attempts.
Capture a useful baseline
Write down the affected model, software version, active input and when this started. Identify filesystem format in macOS Disk Utility without erasing. A working comparison tells you which part of the chain is still healthy.
Use the least disruptive correction
Use compatible read/write format for future files or approved software after safely copying data. Apply one supported change at a time; stop if your model uses a different setting or does not advertise the feature.
Confirm the expected outcome
Files can be safely copied both directions using supported arrangement. Try the original failing action again, not an unrelated easier test; retain the old setting until you know the change helped.
Test the first dependency
Investigate whether drive formatted NTFS and macOS mounts read-only. Specifically, compare a harmless test file with the affected storage item and inspect available capacity and mount state. Compare the result with the working baseline from the beginner route.
Separate another possible cause
Assess whether permissions prevent writes. For this branch, inspect the permission, account or entitlement attached to this feature, without changing any other user profiles. Do not change that configuration unless the evidence supports it.
Inspect the third branch
Compare second known-good drive and Disk Utility First Aid report before changes. Also consider file system reported errors. Record the exact point of failure and check product-specific support limits.
Validate and plan a rollback
Files can be safely copied both directions using supported arrangement. Never erase or reformat until independent verified backup exists. If the last change made matters worse, restore it and request supported assistance with a redacted troubleshooting summary.
Verify the result
Success looks like this: Files can be safely copied both directions using supported arrangement. Run this check on the same device and account that originally failed. A different device passing is useful as a comparison, but it does not prove the original issue is fixed.
What to check if it still fails
Before contacting support, collect the exact model and version, the outcome of the baseline test, and whether the controlled correction changed anything. Keep passwords, private media, account identifiers, serial numbers and network keys out of screenshots or shared logs. Never erase or reformat until independent verified backup exists.
Solution Checklist
After the fix
Repeat the original action once under normal conditions and once after a routine reconnect or reopening, if relevant. Files can be safely copied both directions using supported arrangement. Keep a brief note of the app, input, account or firmware state that changed so you can recognize a recurrence.