View Full Version : Dealing with the lack of automatic mounting of local volumes by SD under OSX 10.8

07-26-2012, 10:40 AM
Dave, in yesterday's (2012/07/25) blog post you noted that

> Automatic mounting of local volumes is the one thing we couldn't get to work in time for Mountain Lion's release.

...but that a fix is in the works.

In the interim, what's the recommended practice? Make sure that backup volumes are always mounted, and turn off the eject-on-quit option?

07-26-2012, 05:27 PM
In the interim, yes - that's what has to be done.

12-01-2012, 01:43 PM
Dave, is there still hope for a fix here? In your blog post of 4 September, you said

> A fix for automatic mounting under 10.8 is still in progress (it's not a simple fix, even though we know what to do).

I put off my Mountain Lion upgrade hoping to see this fix first, and I don't regret that since presumably 10.8.2 is more stable, but it would be nice to hear about your progress if any. If it turns out that automatic mounting can't be done, so be it.

Thanks again for an excellent product.

12-01-2012, 02:50 PM
We have to rewrite the scheduler to get this working. It's in progress.

12-02-2012, 03:11 PM
We have to rewrite the scheduler to get this working. It's in progress.

Great to hear; thanks!

12-08-2012, 01:18 PM
Would you mind explaining this issue a bit more; I think I am misunderstanding it.

I have two external drives attached to my iMac: one for SuperDuper and one for Time Machine. I know I could have them both on the same drive, but having them on two physical drives makes me feel more comfortable.

I never eject these drives, but they do go to sleep.

I assume that is not what you are talking about in this thread. Are you talking about a drive that is completely ejected (not visible on Finder) but still attached via USB?

Finally, and most most impactful to me personally, there are occasions where I get a SuperDuper error indicating it could not mount my Clone drive. As I mentioned above, I never unmount these drives so was wondering if these issues were somehow related.

This happened again this morning with Growl (thanks for getting that working again) indicated the SuperDuper copy failed for that reason.

I ejected and remounted the drive, ran SuperDuper again and it worked as expected, so some insight into these intermittent failures would be greatly appreciated along with any suggestions to avoid them.

Much Thanks for Great Software™

12-08-2012, 02:38 PM
Yes, I'm talking about mounting drives that are attached to the Mac but ejected - not visible on the desktop.

Not "finding" your drive is more likely because the drive is read-only due to the system deciding it has low-level errors. Ejecting and reattaching it automatically runs "fsck", which fixes the errors.

02-24-2014, 11:30 AM
Well, after a year and a half it's time to put this topic to rest. The 2.7.2 update restores the automatic mounting and ejecting of backup volumes. I am so very glad that I no longer have those icons cluttering up the desktop; thanks!

02-24-2014, 11:47 AM
Indeed it does... :-)