Disk not ejected properly

Hi,

This is not quite right as you cannot just pull that folder to the desktop, for one it copies it by default, and 2 it contains boot.plist which cannot be deleted. So this needs editing.

I have had this issue for a very long time, it was fixed on my 27 iMac retina simply by installing Sierra as if my magic, but then this week I bought a brand new MacBook Pro 15 (with the silly touchbar) and did NOT restore it but set it up from brand new, and this issue has returned. I noticed it did it on screen saving or screen dimming, so disabling that so the screen never dims or saves seems to have stopped the issue.

I will try a corrected version of your list and report back if it fixes it or not.

NicW

Interesting.

I followed the steps and pulled it to my desktop.

I renamed the machine.

What is interesting was when I pulled up finder, all of my customization was gone so I had to start putting things back to the way things were.

Something definitely changed.

Perhaps one can pull the SystemConfiguration folder, but what it does is replace it with a default of some sort? Maybe this clears out some of the configuration files that are corrupted or at least are the ones which are causing folks problems with the Disk Ejection messages and in my case legit Mail showing up always as "Junk".

Anyhow. I am not sure it works for everyone or exactly how it works, but for me it was successful and maybe it will be for some others who are having perpetual problems as well.

Upgrading to Sierra would likely have fixed my issue as well especially with a clean install, but perhaps if I migrated the problem could have persisted as it did in Yosemite.

Anyhow... it would be great to hear how things go with your issues and how you fix them. Be sure an post your corrections and solutions.

Thanks

I wanted to reply to this thread and its followers with my experience. I started having "Disk not ejected properly" popups on my mid-2015 iMac 27" Retina for my external firewire Time Machine drive. This Mac is running Yosemite. It seemed occasional at first but then started happening very frequently. My first assumption was the drive so I changed cables with limited success; then I suspected a problem with the firewire bus on the drive so swapped the hard drive into a newer drive enclosure. Everything I tried seemed to work initially - until I stopped use of the iMac for the day and then went back to it later to see it had happened again... when I woke the iMac from sleep.

When I noticed the drive that "improperly ejected" was usually still mounted on the desktop, I searched these communities to see if anyone else had this problem and found this and other threads. Based on what I read and found people talking about the unchecking the option to "put hard drives to sleep when possible."

So I unchecked the option. It's been 5 days now and there have been no more "Disk not ejected properly" alerts so far. I think modifying that one checkbox in my system preferences has resolved it.

So, perhaps by sharing my apparent solution it will help someone else. I'm thankful in my case it seems to have been this simple.

Thanks

JScott has mentioned that he's seeing the DNEP error with Firewire-connected drives. The thread has gotten too long to easily read all 33 pages, but I thought I'd ask if anyone following has seen it with Thunderbolt-connected drives.

Since upgrading to macOS Sierra, my USB connected drives have mostly been error free, but I now see the DNEP message for my TB drives every time after my iMac 5K has been sleeping overnight (sleeping it for an hour or two during the work day does not seem to do it). Only once have I experienced an actual problem other than the annoyance of deleting the error messages. On one occasion, Sierra somehow created an alias for my external drive, and I suspect that it was related to this DNEP issue. That changed the name of the drive's Mount Point ("Data 1" was changed to "Data 1 1", and that name change caused confusion for several applications that were set to create backups to that drive.

Anyone seeing the DNEP with Thunderbolt-connected drives?

Actually, my FireWire drive is connected to my 2015 iMac via Thunderbolt (failed to include that detail, I see). I use an Apple Thunderbolt to FireWire connector. So, yes, technically my drive is Thunderbolt connected.

Since I posted my update on January 7th, I have seen a few more DNEP errors, though not as many as I had been seeing in December. They do occur after overnight or longer sleep, not after brief sleep, like Milleron's report. I have not experienced seeing an alias getting created. I am still on Yosemite but will upgrade to Sierra one of these weekends.

There's been much talk of this issue going away with an upgrade to Sierra. For me, that is not the case. My mid-2009 Macbook Pro running Yosemite was handling my 3 external LaCie drives just fine. 2 are daisy-chained Firewire, and 1 is USB. None of these drives have their own power-supplies, but are powered by the data ports (travel-drives). They've always treated me great.
Last month I bought a new MacBook Pro and migrated my system from my old machine. The new machine came with El Cap and the involuntary dismounts (also a mtn. biking term) started right away. I can get a dozen error messages on my desktop. I read this thread and was inspired by the theory that Sierra was the fix, so I jumped on that upgrade. Nothing has changed. Interestingly, it seems to only be the Firewire drives (now running through a Thunderbolt adapter) that are having the issue. The USB drive seems to be solid. I have tried both suggested fixes: Energy Saver "Put HDs to sleep...." setting; and the Spotlight, adding drives to Privacy list...with a system restart for good measure...to no avail. I have Time Machine disabled (using it manually, periodically). Since my machine is new, I'm going to call Apple support and try to get a fix, or at least some acknowledgment, right from the horse's mouth..

"Plus one" on the Sierra doesn't fix the problem. Neither does moving to a new Macbook Pro.

I have a brand new, MacBook Pro (15-inch, 2016) with touch bar, etc. that came stock with macOS Sierra (upgraded now to ver. 10.12.4.) I get 14 DNEP errors on my desktop every time I come back to my desk and wake my machine. I have one 2TB Seagate GoFlex Desk Media drive that I use for Time Machine backups.

C'mon Apple. This is an ISSUE. Please address it.

BTW, this also happened on my last MacBook Pro, which was a 2013 model. This is an OS issue. It is not drive or cable or even Apple machine version dependent. Please put some unimaginably smart engineer (I know you have many of them) on this and find the bug. It's certainly not hard to reproduce, and you have about a thousand of us that have the problem who would love to test it for you.

Please? Please, oh please.

I'm going crazy, imac retina 5k and new usb 3 seagate 2tb i got ever "Disk Not Ejected Properly" telephone support will not admit the bug, told me that the disc is defective. I have no words...

Same issue with a 27" iMAC, 1 week old.

Same issue, iMac Late 2013

Same issue with my MacBook Pro 15-inch, Early 2011

I too had the same issue. Apple support didn't have a solution. Bought the app "Jettison" and it totally solved the problem.

Just had a chat with Apple Support. They suggested enabling Power Nap. I'll give it a try this weekend (with a non-critical drive) and post whether or not it helps.

I don't believe the Power Nap option will work. I have the same problem and have had that enabled for a while. If you get better results, let us know.

Sounds like you took the same path that I took. I too purchased Jettison which seems to be working. And yes, you would think that Apple could provide an even better fix - long overdue IMO