"Disk Not Ejected Properly" error after EL Capitan goes to sleep and wakes up again.

Jim, Apple does not read these, generally, although my bug report includes a link to this thread. A number of years ago, after filing a bug report about unusual behavior from an external DVD drive, Apple did contact me for more information. My guess is that they are reacting to the issue, if not as quickly as we might like. I have not been contacted on this one, and I can see you haven't been, either. One can only surmise what they are or are not doing. I suspect, however, that we are experiencing an issue related to OS X that may be dealt with in a system software update. The bug reports filed are the surest (and only, at least here in the forums) way to get their attention on this.

Okay, gentlemen add me to the list–again. My MacBook Pro was rock solid this entire week, until tonight. Great! Back to square one. Well at least I won't be afraid to try and SMC reset now.

Myaka, I was contacted tonight regarding my bug report! It was only a request to submit a sysdiagnose error report, but I guess that's something. I replied with the report and hope to hear back from them again.

I am about to try sleeping my iMac for the night. Hopefully my drives come back on in the morning!

-------------------------------------------------------------------------------- -

It has been 0 days since last Disk Not Ejected Properly Error

-------------------------------------------------------------------------------- -

I have done NVRAM and SMC resets several times. So far without success. It is always like Jim is describing: the issue seems to be solved but then it is back again. Unreproduceable. But this is what I am after: trying to force this error so I can report a reproducable bug report.

So far I had no success, although I got the feeling that the ejection of the drive occours every time do a remote access to my itunes media via the apple tv or remote app and the system goes into deep sleep.

Can anyone confirm this?

JNewHome, you hit the nail on the head. None of us have been able to reproduce the problem.

We all know that something is triggering it. We just need to determine what we're all doing that's similar. As for me, I'm not accessing my MBP remotely with iTunes or an Apple TV, but what I do use is Time Machine to automatically backup my external G-drive. Not sure if that's a factor or not.

Okay, so I just got off the phone with G-Technology and they haven't heard anything about this issue.

What I find strange is that my MBP is now correctly reporting that my G-drive is connected to a USB 3.0 Bus, which is when I started to get the "Disk Not Ejected Properly" message again, which means this issue is definitely related to a USB 3.0 or Thunderbolt connection. Now that Apple is taking this matter seriously, I'm hopeful they'll be able to determine what the heck is going on—and soon.

And here's an interesting fact. The tech support rep said that Apple's System Report can't always determine the drive's serial number, so rather than inserting an N/A or something else that's more appropriate it simply inserts random numbers. Nice.

As above. Updated to the latest software on my iMac and now getting copious disk not ejected properly messages (appears to coincide with the hourly time machine back up). The disk in question is Seagate and managed by Time Machine on the Mac. This had happened on a previous update and then fixed - come on Apple this is your fault and needs fixing.

It is frustrating that this error is occurring across so many different computers and drives and types of ports. I'm currently getting the error from my thunderbolt drive, but not my USB 3.0 drives, but others are only getting the error on USB 3.0 drives. I had a run of 36 hours without an error, but the errors have returned for the last two days.

90% of my errors are *immediately* after waking from sleep.

5% of the time it's within 5 minutes of waking from sleep.
5% of the time I can wake the iMac without an error and the drives remount.

-------------------------------------------------------------------------------- -

It has been 0 days since last Disk Not Ejected Properly Error

--------------------------------------------------------------------------

Can I just say, ME TOO!!!

SO, SO FRUSTRATED! WHAT ARE YOU DOING ABOUT THIS APPLE???

Once again let me repeat what works for me. In energy saver set computer sleep to never. Un check "put hd to sleep when possible. I have 2 external hds. One is firewire 800 and one is sata via a OWC PCIe seta adapter. It workes for me in 10.9.5, 10.1 and 10.11.

Having contacted apple support and updated to El Capitan 10.11.4 (I was on 10.11.3) this seems to have resolved the problem (only three hours so far but looks promising. During the conversation with Apple it was mentioned ' that there's a lot on this...' so I suspect Apple were fully aware of the problem in the previous update. Unless it re-emerges later I suspect resolved. I'd rather allow the mac to sleep when I'm not using it...

nealt2, this may be a solution for those using SSDs; it is worth noting that for spinning disks it is likely to result in shortened lifespan -- as, for example, they merrily continue running during the hours a user is asleep or otherwise absent.

Angry again, some of us who continue to experience the issue (I am among them) are running 10.11.4. Some of us who thought they had found a solution discovered many hours later that they had not as the unmounts suddenly returned. I'll hope that your three hours turns into days and weeks, but I suspect it may not.

carmi_m, I understand your frustration, having had enough of my own on this. It would be helpful if you provided information about the particulars of your experience. What computer? What drive or drives are you using. When and how often does the issue appear? What version of OS X are you running? Have you tried any of the suggestions in this discussion that appear to offer some (temporary, in most cases, sadly) resolution? In order to move toward a fuller understanding, some specific information would be of use.

Angry again, I don't want to jinx you but I suspect your success will be short lived. Like myaka said, I too am running 10.11.4 and I am also continuing to have this issue. For me, it's always when waking from sleep.