-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with SSD Ejection on macOS Sonoma with Ejectify #78
Comments
Are there any glues in the Console app that could reveal this behavior? It's very hard to diagnose the issue as Ejectify is just instructing the operating system to unmount and mount. Something goes wrong in the underlying system. |
Just to add, I am having the same issue as the original poster described with an SSD connected to my MacBook via an Apple Studio Display. As far as I can recall, the issue only began after updating to macOS Sequoia. I might need a bit of coaching to get there, but I am happy to provide any info you might need to diagnose the issue. Just let me know... |
Please check this FAQ and try its suggestions. If they don't work, please check the Console app as instructed to see if that gives any information of why things aren't working as expected. |
Issue with External SSD Not Reconnecting After Laptop Wakes from Sleep on macOS Sonoma
Description:
I’m encountering an issue with my external SSD while using macOS Sonoma (version 14.6.1) on an Apple M1 Max, connected via the Apple Studio Display. The SSD is primarily used for Time Machine backups, and I have been using your Ejectify application to manage its connection during sleep.
Issue Details:
Inconsistent Reconnection:
Ejectify Configuration Attempts:
Observed Behavior:
Expected Behavior:
Given the nature of this issue, I’m reaching out directly to you for any insights or suggestions that could help resolve it. Since you developed this application on your own, your expertise would be invaluable in understanding what might be happening and how I can address it.
Thank you for your support.
The text was updated successfully, but these errors were encountered: