goye

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

Hi, community.

 

On public launch day, I upgraded my Macs (Mid 2010 MacBook Pro 15", Mid 2012 MacBook Peo 15", Late 2011 MacBook Air and a Mid 2010 Mac Pro) to OS X El Capitan. In general terms, the upgrade process went smooth.

 

But, I've been presenting an annoying problem:

 

Each time any of my computers go to sleep, if they have an external hard drive connected to an external USB Hub (unpowered), they present a "Disk Not Ejected Properly" error after they wake up again.

 

I didn't have any of these issues with Lion, Mountain Lion, Mavericks nor Yosemite! Only now, when I upgraded to El Capitan, things are getting annoying.

 

Does any one else present the same issues and, do you have a solution to this problem.

 

Thanks for reading.

MacBook Pro, OS X El Capitan (10.11)

Posted on Oct 2, 2015 9:38 PM

Close

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

  • All replies
  • Helpful answers

first Previous Page 8 of 14 last Next
  • by myaka,

    myaka myaka Apr 11, 2016 1:16 PM in response to Kelly Crossley
    Level 4 (2,472 points)
    Desktops
    Apr 11, 2016 1:16 PM in response to Kelly Crossley

    So it goes.  Disk mounted on powered USB 3.0 hub at 9:06 this morning.  At 2:08 this afternoon, it spontaneously unmounted with no input from me.

     

    Note that my machine continues to be set to never sleep, but the Put hard disks to sleep when possible box in Energy Saver prefs is checked.  Maybe unchecking it would offer benefit, but I've got an internal RAID pair that I don't want to spin every blessed second of every day, and that never generates alert messages about ejecting improperly.

     

    I'm back to the Keep Drive Spinning app for my external HD dock so it will only unmount at my command.

  • by Kelly Crossley,

    Kelly Crossley Kelly Crossley Apr 11, 2016 1:22 PM in response to myaka
    Level 3 (720 points)
    Mac OS X
    Apr 11, 2016 1:22 PM in response to myaka

    myaka, I just checked and in my Energy Saver preferences, "Put hard disks to sleep when possible" is unchecked, so perhaps that's the key to this setup.

  • by ComposerGuru,

    ComposerGuru ComposerGuru Apr 11, 2016 1:23 PM in response to Kelly Crossley
    Level 1 (4 points)
    Apr 11, 2016 1:23 PM in response to Kelly Crossley

    Try clearing your user cache and your root folder library cache. They are in your user and mac HD library folders. That temporarily fixed my problem thus far.

  • by myaka,

    myaka myaka Apr 12, 2016 7:44 AM in response to ComposerGuru
    Level 4 (2,472 points)
    Desktops
    Apr 12, 2016 7:44 AM in response to ComposerGuru

    Sadly, deleting user and root cache files (and restarting) had no effect.  What is confusing about this issue is that there appear to have been different fixes for different computers and/or configurations -- that some of them appear to have had only temporary effect muddles things yet further.

  • by Kelly Crossley,

    Kelly Crossley Kelly Crossley Apr 12, 2016 9:08 AM in response to myaka
    Level 3 (720 points)
    Mac OS X
    Apr 12, 2016 9:08 AM in response to myaka

    Did you make sure "Put hard disks to sleep when possible" is unchecked?

  • by myaka,

    myaka myaka Apr 12, 2016 2:37 PM in response to Kelly Crossley
    Level 4 (2,472 points)
    Desktops
    Apr 12, 2016 2:37 PM in response to Kelly Crossley

    When the problem first cropped up, I did try unchecking that box.  It made no difference, unfortunately.

     

    BTW, when I made that test, it was an attempt to see if that Energy Saver setting was an issue -- but I would not run the computer for extended lengths of time (weeks, months) with it unchecked unless I only had SSDs affected by that setting.

  • by Kelly Crossley,

    Kelly Crossley Kelly Crossley Apr 12, 2016 5:31 PM in response to myaka
    Level 3 (720 points)
    Mac OS X
    Apr 12, 2016 5:31 PM in response to myaka

    That's disappointing. I think I'm up to at least a dozen sleeps and my G-Drive is performing great with the USB 3.0 hub. I haven't had one issue with it waking or disconnecting. Do you think a restart AFTER you unchecked "Put hard disks to sleep when possible" would help? What about a PRAM or SMC reset?

  • by Jim Show,

    Jim Show Jim Show Apr 12, 2016 6:53 PM in response to Kelly Crossley
    Level 1 (34 points)
    Mac OS X
    Apr 12, 2016 6:53 PM in response to Kelly Crossley

    Kelly,

     

    FWIW, I have 2 different GTechnology GDrives connected to my 4 week old iMac Retina 5k, one is a 4 Terabyte and the other is a 6 terabyte, both are also only 4 weeks old. Both are connected via USB 3.0 into an unpowered hub, which is then connected to the back of my iMac.

     

    From day one, neither GTechnology drive has had an ejection problem. Both work perfectly, sleep perfectly, wake up perfectly.

     

    My problem is my (also brand new) 6T LaCie RAID drive connected via thunderbolt. That one is unmounted with an error message every time I sleep the iMac and wake it up again. I have tried changing every Energy Saver setting combination I can and every time, I get an error message about the thunderbolt drive upon waking from sleep. The drive disappears from the system profiler and will not reconnect unless I physically unplug and replug the thunderbolt cable.

     

    Even with all the changing of settings in energy saver, the GDrives continue to sleep and wake correctly. Never an issue.

     

    The only odd thing about the GDrives is that one of them is shown in System profiler as an INTERNAL drive on my iMac and one is shown as an EXTERNAL drive. Both are connected to the same hub via USB 3.0. Not sure about that one.

  • by Kelly Crossley,

    Kelly Crossley Kelly Crossley Apr 12, 2016 7:16 PM in response to Jim Show
    Level 3 (720 points)
    Mac OS X
    Apr 12, 2016 7:16 PM in response to Jim Show

    Hi Jim.

     

    Yes, I saw your post earlier, but I must have missed the fact that your G-Drives were connected to a USB 3.0 hub. All of my problems occurred when my G-Drive was connected directly to my MBP. Once I connected it to the powered HUB, all of my problems went away, which is good because it was driving me MAD. Plus, I can't imagine what kind of file damage is being done every time the drive disconnects abruptly.

     

    I'm assuming your LaCie RAID is connected directly to your iMac. If so, that seems to reinforce the theory that there is some kind of a signal that's being cut-off to all directly connected external drives, but it doesn't explain myaka's problem. This is all very strange.

     

    Where is an Apple tech when you need one?

  • by Jim Show,

    Jim Show Jim Show Apr 12, 2016 7:33 PM in response to Kelly Crossley
    Level 1 (34 points)
    Mac OS X
    Apr 12, 2016 7:33 PM in response to Kelly Crossley

    I had trouble for a few days, but was finally able to submit a bug report to Apple. Who knows if it will get read, but this thread keeps floating to the top whenever someone posts... so that might help.

     

    Yes, my Thunderbolt drive is connected directly to the iMac. I have not tried connecting the GDrives directly and I really don't want to mess with them because they have been flawless since I started using them. My USB 3.0 hub is unpowered. It is a cheap Sabrent 4-port hub.

     

    When I spoke to the LaCie tech, she suggested it was a thunderbolt PORT issue. When I plugged the LaCie drive into an old Snow Leopard MacBook Pro via USB 2.0, it worked perfectly with sleeping, waking, shutting down, everything. It remounted no problem. When I put it back into the iMac thunderbolt port, the error/unmounting happened again.

  • by myaka,

    myaka myaka Apr 12, 2016 7:51 PM in response to Jim Show
    Level 4 (2,472 points)
    Desktops
    Apr 12, 2016 7:51 PM in response to Jim Show

    Jim, this is Interesting.

     

    Under System Profiler, one of my two mounted dock drives shows up under the USB heading (the other does not!) and is listed as Detachable.  Under the Storage heading, both show and both are listed as Internal.

     

    It is also strange that you and Kelly have drive enclosures from the same manufacturer but different experiences with them.  I have USB 3.0 enclosures from two different manufacturers, Sans Digital and Xiaboi, but only have issues with the latter.

     

    Glad you managed a bug report.  I have also submitted a bug report that referencee this discussion.

  • by Jim Show,

    Jim Show Jim Show Apr 12, 2016 8:15 PM in response to myaka
    Level 1 (34 points)
    Mac OS X
    Apr 12, 2016 8:15 PM in response to myaka

    Myaka,

     

    I just looked at my system profiler again. I have two USB 3.0 GDrives from the same manufacturer with the same enclosure bought 4 weeks ago from the same store, but one is 4 Terabyte and one is 6 Terabyte. Both are connected to a USB 3.0 hub. The hub is plugged into the back of a brand new iMac.

     

    In System Profiler, under USB tab, one is listed as a USB 2.0 drive and one is listed as a USB 3.0 drive.

    Under the Storage tab, the 4Terabyte is listed as an INTERNAL drive, the 6Terabyte is listed as an EXTERNAL drive.

  • by Jim Show,

    Jim Show Jim Show Apr 12, 2016 8:26 PM in response to Kelly Crossley
    Level 1 (34 points)
    Mac OS X
    Apr 12, 2016 8:26 PM in response to Kelly Crossley

    Well, my GTechnology GDrive flawless streak has ENDED. In an effort to try one more thing to stop my thunderbolt drive problems, I decided to try to reset the NVRAm one more time.

     

    I ejected and unplugged all external drives, shut down the iMac, reset the NVRAM and then plugged all the drives back in as they were and started them up again. Within 5 minutes both G-Drives unmounted themselves and then remounted themselves, both with the "Disk not ejected properly" error message. One happened while performing a backup task. It just disappeared and then came back. The backup task stopped and I tried it again and it worked the second time. The other GDrive did the same thing while the first one was completing it's backup second attempt.

     

    I am very worried now. I had not had a drive eject WHILE it was in use yet. And I had not had one of these GDrives eject in 4 weeks. Now it seems like all drives are fair game. All three 4-week-old drives have been affected. Dammit.

     

    Please help, Apple.

  • by Kelly Crossley,

    Kelly Crossley Kelly Crossley Apr 12, 2016 8:27 PM in response to Jim Show
    Level 3 (720 points)
    Mac OS X
    Apr 12, 2016 8:27 PM in response to Jim Show

    Okay, now I'm totally confused. I just checked my setup with Apple System Profiler and it's reporting that my  G-Drive is connected to a USB 2.0 Bus, but here's the problem. My Mid 2012 MBP i7 ONLY has USB 3.0 ports and my Satechi Hub only has USB 3.0 ports as well. What the heck is going on?Screen Shot 2016-04-12 at 11.23.46 PM.png

  • by Kelly Crossley,

    Kelly Crossley Kelly Crossley Apr 12, 2016 8:31 PM in response to Jim Show
    Level 3 (720 points)
    Mac OS X
    Apr 12, 2016 8:31 PM in response to Jim Show

    **** Jim. I'm sorry to hear that.

     

    [UPDATE]

    I just discovered that you can't swear on the Apple Forums. If your curious, the four letter word I used is the thing that holds water back.

first Previous Page 8 of 14 last Next