external drive ejects at sleep

Sorry to hear that Time Machine restores would not help in this situation.

Decided to bite the bullet and roll back to 10.8.4 via a SuperDuper backup from last Thursday. 10 minutes and a few settings changes, and I am back in business.

Going to wait for Mavericks (and a few weeks after it comes out) before taking the dive again.

I decided to revert back to 10.8.4. There seems to be some confusion on whether Time Machine can be used to roll back to a previous version. I'm not sure if this would work in all cases, but I did manage to do this using Time Machine on my latest model iMac.

I used the guide at http://pondini.org/TM/14.html, booted to the Recovery HD partition and selected Restore From Time Machine Backup. When selecting a backup, the OS X version is shown against each entry, so I simply selected the most recent 10.8.4 backup. This worked perfectly and now I am back to a functioning 10.8.4.

Sincere apologies to all.

I should have explained that when I meant using time machine, I meant going into time machine when you've already logged in to your user account. I didn't realise we could also use time machine before booting into Mac OS X. I've since restored back to 10.8.4 using the method ian2828 has posted above and all is back to normal again, no ejecting of the drive. Wey-hey! (BTW, to get to the Recovery HD you need to press and hold command & R when booting up. It doesn't appear to state this in the link)

If you try to restore from time machine when you've already logged into your user account, that's when restoring will not work.

Sorry about that 😊

For what it's worth, I've been able to temporarily alleviate this problem by going to the Energy Saver settings in System Preferences, and disabling the display from sleeping. Although this is sub-optimal, since it means my monitor is always on, it's certainly preferred to the problem with my external drives disconnecting for no good reason.

same problem here, everything was fine under 10.8.4. Since updating to 10.8.5, my lacie 2big USB3.0 hangs the computer when I try to access it after waking from sleep.

It is a 10.8.5 bug for sure, Apple get a finger out....

I'm having a similar problem. My two external Firewire disks seem to spin down if the computer is idle (but logged in). When I go to access the cloned Firewire disk or when TIme Machine accesses the other Firewire disk, there is a delay of a couple of seconds and I can hear a disk spin up. This only happened after I updated to 10.8.5.

Tom

same issue here with WD MyBook Thunderbolt Duo. I'll try to deactivate the monitor to sleep later...

No need to disable Monitor sleep, just disable the computer sleep. You can let the monitor sleep, no problems.

i've also the issue, that the thunderbolt duo spins down after 20min of idleing. For this there is no fix? In addition the 'WD Drive Utily' doesn't see the HD anymore...😠

i'm not at home. So i cannot try the follwing:

sudo pmset -a autopoweroff 0

Does this fix the spin-down-problem?

it's not working😮

Simply telling the system not to sleep doesn't resolve the issue. My system never sleeps but the monitor turns off to save power. I left my monitor on (disabled in Preferences) all weekend the issue didn't occur. This morning, the monitor turned off for less than an hour and I saw the eject error.

I reported the bug to Apple, has anyone actually talked to support?

not talking to support yet, but i'll try this thing with monitor-sleeping this night...

Voltaic wrote:

Simply telling the system not to sleep doesn't resolve the issue. My system never sleeps but the monitor turns off to save power. I left my monitor on (disabled in Preferences) all weekend the issue didn't occur. This morning, the monitor turned off for less than an hour and I saw the eject error.

I reported the bug to Apple, has anyone actually talked to support?

Hi,

I've contacted support. They didn't do much other than have me repair permissions and verify the external disk.

I have a case number though to contact them again if/when it happens again.

Hoperfully the more support calls they get, the faster they'll fix it...