iPhabio

Q: Disk not ejected properly

Hi I'm having this issue since I upgraded to Mavericks where almost every time I put my computers to sleep I get the "Disk not ejected propoerly" message and every disk but the system one is not mounted and cannot be found by Disk Utility.

 

I have a Mac Mini late 2009 and a Macbook Pro 15 mid 2009 and I'm having this issue in both machines. Never had any issues before in any of my machines, not in Leopard, Snow Leopard or Lion.

 

On my Mini I have two external USB drives and on my MBP I have a SSD, where the system is installed, and a HD (I replaced my optical drive with a bay to install the extra disk).

 

I researched the issue and found a couple of threads where people sugested to buy a 3rd party app that would unmount the disks at sleep and remount them at wake, but I think this shouldn't be a issue, since it never happened with any version of OSX I had used before.

 

Is anybody else having this issue as well? Is there any word from Apple on this subject? Can I hope for a fix?

 

Thanks

MacBook Pro, OS X Mavericks (10.9)

Posted on Oct 28, 2013 9:55 AM

Close

Q: Disk not ejected properly

  • All replies
  • Helpful answers

first Previous Page 12 of 32 last Next
  • by Richard W J,

    Richard W J Richard W J May 28, 2014 10:35 AM in response to iPhabio
    Level 1 (0 points)
    May 28, 2014 10:35 AM in response to iPhabio

    What with this and the nightmare over Pages is Apple Mac going off the boil? I have an old MacBook running mavericks and I expect to look for a replacement in the next year or so ... will I be looking at a PC? Jury is out at the moment.

  • by mmanna1,

    mmanna1 mmanna1 May 30, 2014 10:44 AM in response to mmanna1
    Level 1 (4 points)
    May 30, 2014 10:44 AM in response to mmanna1

    After spending way too much time on this issue, I decided to purchase a new external hard drive with a USB 3.0 connection.  At a local store that only sells Apple equipment, I purchased a Western Digital 1TB "My Passport" drive.  It utilizes a USB 3.0 connection.  I did not install any of the included WD software.  I installed it yesterday and selected it through Time Machine as the backup.  Since then there has been no self ejection and the unit has done backups as directed by Time Machine.  I consider the problem solved for me.  It is well worth the money.

  • by gvca,

    gvca gvca May 31, 2014 6:48 PM in response to mmanna1
    Level 1 (12 points)
    Mac OS X
    May 31, 2014 6:48 PM in response to mmanna1

    That's interesting, mmann1, my Seagate that kept ejecting has a USB 3.0 connection.  I got it it to replace my Western Digital "my Passport", because the Western Digital wouldn't mount after I got my new iMac running Mavericks (it worked fine on my old iMac running Snow Leopard).  Since I have had the Seagate plugged into a powered USB hub, I haven't had the problem of it ejecting improperly anymore.

  • by kcft,

    kcft kcft Jun 4, 2014 4:54 AM in response to iPhabio
    Level 1 (10 points)
    Jun 4, 2014 4:54 AM in response to iPhabio

    I just wanted to add that I also experienced this problem after installing the Yosemite Beta.  Fortunately, Robin's solution worked like a charm.  Thanks!

  • by mmanna1,

    mmanna1 mmanna1 Jun 4, 2014 12:45 PM in response to gvca
    Level 1 (4 points)
    Jun 4, 2014 12:45 PM in response to gvca

    It has been 6 full days since I installed the WD Passport drive that uses a USB 3.0 cable on my iMac with 10.9.3 Mavericks.  I have experienced no "disk not ejected properly" error messages.  As an experiment, I took my old Maxtor OneTouch4 external hard drive with it's USB 2.0 connection that would not work on the 10.9.2 Mavericks and installed in on our church iMac that is using 10.7 "Lion" software.  It mounted fine and has experienced no ejections.  There must either be a USB connection issue or a software issue.

  • by Svenissimo,

    Svenissimo Svenissimo Jun 8, 2014 4:03 AM in response to iPhabio
    Level 1 (0 points)
    Jun 8, 2014 4:03 AM in response to iPhabio

    I am on mavericks and this has just started to happen for me on iMac mid 2011.

     

    Before(no issue) I had :

    Standard 1tb internal drive and a nas media centre type 500gb connected via the Ethernet..

     

    Now eject errors on my external 1tb seagate connected through usb2

    I have also got the original 1tb in an enclosure connected via usb2 and this does not have an issue. It does have an external power supply.

    The internal,drive is now a crucial 256 SSD.

     

    on wake from sleep I see the error message for both partitions of the 1tb seagate external drive..

     

     

    My gut feeling is that there is some power management issues. I'm going to scan through the Eco settings and see if there is anything going on on the seagate forums.

  • by ataynay,

    ataynay ataynay Jun 8, 2014 7:51 AM in response to Svenissimo
    Level 1 (0 points)
    Jun 8, 2014 7:51 AM in response to Svenissimo

    I doubt that it is power issues, because it is happening with my iPod and with a 1GB thumb drive.  I don't have any heavy external drives.  I have been wanting to connect my Time Capsule to run a backup but am very much afraid to now, with this problem.

  • by slbenfica,

    slbenfica slbenfica Jun 8, 2014 2:50 PM in response to slbenfica
    Level 1 (0 points)
    Jun 8, 2014 2:50 PM in response to slbenfica

    Another update to my series of posts earlier. Now that all the boxes are unchecked in the energy saver, and now that I have the hard drive and display set to never sleep, I do not get the disk ejected message anymore. I have updated to 10.9.3, which may or may not matter - I'm going to check some boxes in the energy saver later today and let the hard disk try to sleep to see what happens while I'm out of the office. In the meantime, I have told the computer to go to sleep manually several times, and after short naps the computer wakes with the disk still connected. So the current setup works, but saves no energy. I'll update again when my energy saver settings are adjusted back to slightly-more-eco-friendly. Thanks again, Apple, I *really love* your new free OS with all its glitches (external display with their own software can be its own horrible problem...) - worth only slightly less than I paid for it.

  • by slbenfica,

    slbenfica slbenfica Jun 11, 2014 2:25 PM in response to slbenfica
    Level 1 (0 points)
    Jun 11, 2014 2:25 PM in response to slbenfica

    Final update (I hope): It appears that Mavericks 10.9.3 dealt with my issue, because after I did everything discussed above, my problem was not resolved. After the update to 9.3, I have returned all energy savings settings to their original (10.8.something) levels, and three days later with abundant sleeps in between, I have yet to experience the disk not ejected properly issue. I hope everyone else has experienced the same improvement with that update!

  • by gvca,

    gvca gvca Jun 11, 2014 11:43 PM in response to slbenfica
    Level 1 (12 points)
    Mac OS X
    Jun 11, 2014 11:43 PM in response to slbenfica

    sibebfica, I am glad that the Mavericks update 10.9.3 solved this issue for you.  I still had the problem with Mavericks10.9.3.   The only thing that worked for me was using a powered USB hub that doesn't allow the Seagate to go sleep. However, I see that my solution didn't work for others in this forum.

     

    kcft:  well, I guess Yosemite isn't much better!

  • by KenV54,

    KenV54 KenV54 Jun 19, 2014 11:42 AM in response to gvca
    Level 1 (5 points)
    Jun 19, 2014 11:42 AM in response to gvca

    FWIW, I have a WD MyBook USB 3.0 1.5 TB external drive connected to a powered (low powered, not high) 3.0 USB hub connected to a MacBook Pro Retina 15" mid-2012 with a recently replaced logic board (because of HDMI problems), using 10.9.3.

     

    I have always had spontaneous disconnects of the external drive. All the WD software has been removed both by their uninstall program and manually for whatever was left. I get these disconnects whether connected to the hub or directly to the USB 3.0 port on the computer, but probably more often with the hub.

     

    Here is the latest Console log of messages before and at the time of the disconnect, and after it reconnected spontaneously. I did have "put hardware to sleep" in the power saving preferences, and I've just unchecked that based on some earlier posts here.

     

    6/19/14 12:56:31.000 PM kernel[0]: disk1s2: media is not present.

    6/19/14 12:56:31.000 PM kernel[0]: jnl: disk1s2: do_jnl_io: strategy err 0x6

    6/19/14 12:56:31.000 PM kernel[0]: jnl: disk1s2: write_journal_header: error writing the journal header!

    6/19/14 12:56:31.000 PM kernel[0]: hfs: unmount initiated on MyBook on device disk1s2

    6/19/14 12:56:31.000 PM kernel[0]: jnl: disk1s2: close: journal 0xffffff803846ac20, is invalid.  aborting outstanding transactions

    6/19/14 12:56:31.000 PM kernel[0]: USBMSC Identifier (non-unique): 5743415A4138363735383138 0x1058 0x1140 0x1025, 3

    6/19/14 12:56:31.509 PM fseventsd[76]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/00000000000bbe06 (No such file or directory). mount point /Volumes/MyBook/.fseventsd

    6/19/14 12:56:31.509 PM fseventsd[76]: disk logger: failed to open output file /Volumes/MyBook/.fseventsd/00000000000bbe06 (No such file or directory). mount point /Volumes/MyBook/.fseventsd

    6/19/14 12:56:32.639 PM mDNSResponder[66]: ERROR: mDNSPlatformReadTCP - SSLRead: -9806

    6/19/14 12:56:32.639 PM mDNSResponder[66]: ERROR: tcpCallback - attempt to read message length failed (-1)

    6/19/14 12:56:45.000 PM kernel[0]: jnl: disk1s2: replay_journal: from: 17653760 to: 21299200 (joffset 0x2baa000)

    6/19/14 12:56:53.000 PM kernel[0]: jnl: disk1s2: journal replay done.

    6/19/14 12:57:00.000 PM kernel[0]: hfs: Removed 0 orphaned / unlinked files and 504 directories

    6/19/14 12:57:00.000 PM kernel[0]: hfs: mounted MyBook on device disk1s2

    6/19/14 12:57:00.961 PM fseventsd[76]: event logs in /Volumes/MyBook/.fseventsd out of sync with volume.  destroying old logs. (14714 15 14714)

    6/19/14 12:57:01.369 PM fseventsd[76]: log dir: /Volumes/MyBook/.fseventsd getting new uuid: FE177170-818E-46AB-B21B-6556CEEE75D6

    6/19/14 12:59:20.703 PM mdworker32[5665]: CGSConnectionByID: 0 is not a valid connection ID.

    6/19/14 12:59:20.704 PM mdworker32[5665]: CGSGetSpaceManagementMode: No connection with id 0x       0

     

    Is there anything in the first part of these messages that gives a clue as to why it disconnected (unmounted)?

  • by Camraom,

    Camraom Camraom Jun 28, 2014 2:00 AM in response to iPhabio
    Level 1 (0 points)
    Jun 28, 2014 2:00 AM in response to iPhabio

    I to am having this problem, I have two Seagate 3TB external Thunderbolt drives and one is permanently ejecting its self, I have given up on it now but feel that it is time that Apple dealt with this problem that only started with the arrival of Mavericks. Could it be that they no longer care about their reputation of being head and shoulders above Microsoft, because that is how it looks to me. If I could go back to Mountain Lion I would without hesitation!! It is all very well giving Mavericks away for free but looking at all the people with this problem I think we would all have rather given it a miss!

  • by flarestar,

    flarestar flarestar Jun 28, 2014 3:05 AM in response to iPhabio
    Level 1 (0 points)
    Jun 28, 2014 3:05 AM in response to iPhabio

    Just got a new LaCie 2big (8TB) with Thunderbolt 2. 

     

    Same problem. Randomly, while working, it gives me the "Disk Not Ejected Properly". 

     

    Seeing all the messages here, i guess its not the drive but something in Mavericks?

  • by Linda Cameron,

    Linda Cameron Linda Cameron Jun 30, 2014 7:22 AM in response to Camraom
    Level 1 (28 points)
    Mac OS X
    Jun 30, 2014 7:22 AM in response to Camraom

    I agree with you. This discussion has gone on a long time with no help from Apple. The only external drive that I have which does not eject itself on Sleep is a LaCie which I am connecting via FireWire 800. I have 2 other external drives--one Seagate USB 3.0 (connected to a CalDigit PCI card) and, a WD drive connected to the same CalDigit card but with eSATA. I have plugged the WD and Seagate into a USB 2.0 with the same results. Is anyone having this problem with FireWire?

  • by houstonwehaveaproblem2014,

    houstonwehaveaproblem2014 houstonwehaveaproblem2014 Jul 20, 2014 5:22 AM in response to Linda Cameron
    Level 1 (0 points)
    Jul 20, 2014 5:22 AM in response to Linda Cameron

    A couple of months after giving up on the possibility of a solution to the DNEP problem, I noticed a folder named “Seagate” (the brand of my external HDD) in the Home/Library*/Application Support folder. Believing it was a left-over from when I used it with my 6 month old Macbook Air the very first time (when it automatically installed something called the Seagate Dashboard) I decided to delete it.  I also deleted the Seagate Dashboard icon from the System Preferences drop down.  The next time I connected my HDD to do a time machine backup, I let the screen timeout. When I hit the spacebar to bring the screen back, the DNEP message didn’t appear and it hasn’t appeared for a week since I made this simple change.

     

    The Seagate folder has since recreated itself in the Library folder, likewise the Seagate Dashboard icon in System Preferences (not sure how or why) but the DNEP problem appears to be gone. Fingers crossed.

     

    I've made no changes to my system since my last post, so this isn't the result of an update - I'm still on 10.8.5.

     

    Peter

    *The Library folder is not normally visible. I made it visible to do something unrelated – I can’t remember what – but it’s necessary to find the relevant folders.

first Previous Page 12 of 32 last Next