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

Well my G-Drive is waking from sleep again. The reason? Once again, it thinks it's connected to a USB 2.0 port, when it's actually connected to USB 3.0. This is very weird.

Kelly, My USB 3.0 GDrives show up under the "USB 3.0 Bus" on the main tree, but then under "USB 2.0 Hub" when I drill down a level...

Those G-Drives are USB 3.0 drives plugged into a USB 3.0 Hub, plugged into a USB port on my brand new iMac.

My two USB 3.0 drives have only ejected themselves once in the past 7 weeks. However, my Thunderbolt LaCie drive is STILL ejecting itself after waking the iMac from sleep. It's happened every day this week. It used to be ejected immediately upon waking, but now the trend is it ejects itself about 1-2 minutes after waking. I was less concerned when the iMac would wake up and the drive would just not be there, but now I really don't like that it ejects after everything has spun up.

Come on Apple. What is up???

Okay, well my MacBook Pro once again decided to place my G-Drive under the USB 3.0 bus, which means I'll likely start to have sleep issues again. To the people on this thread who were contacted by Apple, are they working on the problem?

Kelly, I submitted a bug report and after a few days, I got a response asking for a sysdiagnose report. I submitted one right away and then another a couple days later. I never heard anything back. It's been a couple weeks.

I'm still getting my errors daily. Nothing has changed.

(Off Topic - Has anyone else noticed how incredibly awful these discussion pages are to read and navigate on an iphone?)

I ran Disk Utility and it did not find errors but it said it updated my very old iomega drive. If it gives me the eject message again that I have gotten for about a week I will buy a new cable, Very strange as I have been using El Capitan for many months before this happened.

Okay guys, I just updated to Mac OS X 10.11.5 and once again my G-Drive is showing up under the USB 3.0 Bus. Getting ready to hit the hay. Let's see if the G-Drive wakes up later this morning. Fingers crossed.

I probably shouldn't get too excited, but this morning my G-drive was still listed under the USB 3.0 bus and it WOKE UP! That's one wake from sleep. Let's see if it keeps doing it. 🙂

I've now let my MacBook Pro go to sleep around a dozen times and I haven't had any problems with it waking up. And yes, it's still listed as being connected to the USB 3.0 Bus. Way to go Apple! I think you may have solved this problem. Curious to see how others are doing.

Thanks for posting, Kelly.

I am sometimes reluctant to update. If 10.11.5 is working for you, that helps.

(My problem was slightly different. earlier in this thread.)

I have not upgraded to 10.11.5 and my problem persists, but I wanted to give a report on the Apple Bug Reporter... I reported this as a bug over a month ago. Their response was slow, but I was asked for a few different pieces of information over several weeks. In the end, they closed the report stating that it could not possibly be Apple's fault. They stated it has to be a drive issue and I should deal with Lacie. This is after reiterating that the drive works fine on a Macbook Pro running Snow Leopard with USB2.0 and on my iMac with ElCapitan via USB 3.0. The only trouble is when it's connected to the Thunderbolt port on the iMac. But Apple deduced that it has to be the Lacie drive... deal with them... case closed. I'm SOL.

Thanks Apple.

I did a clean install of 10.11.5 as I was having other issues so decided it was time!! I did not import any old preferences, only the apps from a TM backup. I'm still getting the same error every time I sleep the iMac with my LaCie 2Big TB drive. All other USB 3.0 disks are not affected so it's quite possible that there is a problem with LaCie drives. And LaCie desktop RAID manager doesn't work at all if using HW RAID configuration. And the HDD's in the LaCie are already showing as 45.7% health in DriveDX and not even one year old. Seagate 3tb Barracudas are the worst drives on the market. As soon as they fail I don't even want warranty replacements. Instead I'll switch the WD Red NAS or HGST Desktop NAS drives!!

Sadly, Kelly, my early 2009 Mac Pro's spontaneous drive ejections continue after the 10.11.5 update.

I use a third-party USB 3.0 PCIe card, which I don't consider to be the problem since it works just fine with USB 3.0 drives in a SansDigital enclosure.

As my affected drives are mounted in a Xbiaoi drive dock, I conclude the drive dock's USB 3.0 circuitry must be at fault. But Keep Drive Spinning continues to be a solution that makes the dock (which i don't intend to permanently mount drives in) workable for my intended use.

A positive note: a recently purchased late 2012 Mac Mini running 10.11.5 with a connected external SansDigital USB 3.0 enclosure has had no difficulty with sleep or ejection or mounting.

Hey guys, I'm really sorry to hear that you're still having problems. As for me, I have not had a single issue since I installed 10.11.5.

Here is what happened to me:

• Have the same problem, disk not ejecting properly after upgrading to El Capitán. Cannot use my transcend JetDrive, it keeps unmounting all the time.
• Tried updating to every Beta. No luck.
• Take my computer to the Apple Store, a specialist took a look and tried booting a clean 10.11.5 to check that the problem persists.
• The problem was solved in the clean 10.11.5.
• Installed the clean 10.11.5 image on my Mac and the problem stopped.
• After a few weeks without issues I installed Java 6 and MacPorts. The problem appeared again!

I am trying to figure out if the problem is related to any of these (Java 6 or MacPorts) I will install 10.11.5 from scratch again in a few days and then will try installing everything again until I find what is the problem.

Is any of you using any unusual software that could be related to this issue? It would help me to figure out what could be going on here.

Thanks for your help!

Danko

Add me to the list of those suffering from this issue, although it has gone from sporadic to EVERY time my computer sleeps for awhile since changing out my USB Hub.

I am running 10.11.5 on a mid-2015 MacBook Pro. I was using a Belkin 4-port Travel USB Hub. It was fairly inexpensive and non-powered. After upgrading to El Capitan, I did sporadically see this issue and while annoying, it wasn't constant, so I didn't worry too much about it.

Now, I have changed to an AmazonBasics 4-Port USB 3.0 Powered Hub and it happens EVERY. SINGLE. TIME my computer sleeps for an extended period (a few hours?). There are literally error messages down the entire right side of my screen when I wake it up.

That being said, my external hard drive (WD 1TB MyBook) is still connected and works with no issues. However, it does not seem to be backing up in the middle of the night anymore and starts backing up when I wake it up in the morning.

I read through this entire thread yesterday, hoping for a solution, and have tried a couple things (to no avail). I wanted to start small, because I'm no computer expert.

I started with switching my browser to Chrome, because I have had nothing but issues with Safari since upgrading anyway. It freezes on me all the time and I have been force quitting it for months. I thought it was worth a shot. I changed the default browser to Chrome, shut down all programs and restarted the machine. Left for the afternoon and when I came home, no joy! Error messages galore! 😟

So I then tried unchecking the Enable Power Nap box. This morning, still no joy. And now I was just away from the computer for a short couple hours and the entire right side of the screen was still laden with error messages upon wake.

And finally, I will note that it looks like my computer does not seem to recognize the Amazon Hub as 3.0; it thinks it's a 2.0 Hub? I have no idea if it's not compatible, defective or what, but it sure looks like the 4 devices I have plugged into it are plugged into a 2.0 Hub (unless I'm just reading that wrong, because it does also say 3.0 Hub in there, but the menu under the 2.0 Hub is collapsible and contains the items that are actually plugged in):

Sorry I don't have anything to add to the conversation, but I wanted to chime in and say that I, too, am having this issue and it's extremely frustrating. 😟