Disk Not Ejected Properly -- AGAIN AGAIN AGAIN AND AGAIN...

I spotted this thread - I had a similar problem with my iPod classic syncing with iTunes on my iMac - see pic. I think I picked up a comment above and tried it - which was to disconnect the iPod at both the iPod and iMac end and reconnect making sure that it was properly connected. Amazingly and too my relief this worked!

I thought it was just me. LaCie SSD portable drive. I replaced the USB-C cable, but it still occurrs.

Yes, it's maddening...

I'm still using Ventura. I followed one suggestion here and turned off screen saver. Problem solved.

Thanks to whoever...

Jim

Just updated to Sequoia 15.0 and this continues to happen! It even happens when computer is not in sleep mode. Tried connecting to different USB ports, turned off screen saver, auto sleep, etc. Didn't help. I've also had the error below when leaving my Mac in Sleep mode over night, before updating to Sequoia. I'm wondering if it's related to the disk not ejecting properly bug. Hasn't happened again…yet.

Hi, I see you are having an issue with device connectivity. No worries, let's get this fixed!

There might be a possibility you are not using a correct cord. This may cause connection issues between your Mac and the device you are attempting to connect.

If you are using an adapter, check to see if it is an official Apple adapter.

In terms of it happening when your MacBook goes to sleep, it may be shutting off any disks when this happens.

Try keeping your MacBook on when the device is connected. If you are trying to get items from the hard drive onto your Mac or vice versa, you may have to keep an eye on your MacBook while the process is being completed.

Another issue that may cause this is an improperly connected cord. Your cord may not be fully plugged in. Try making sure your cord is fully connected to both the Mac and the hard drive. There may also be foreign objects (dust, lint, dirt, grime, etc.) in the ports. Try cleaning the ports on your MacBook and the hard drive. Do not use water to do this (Yes, people have done this before, yes, it will damage your MacBook). Use compressed air or a toothpick. Do not use a paperclip or anything metal as this may cause a short-circuit and damage components.

A final cause may be the hard drive itself. The hard drive may be incompatible, damaged, or otherwise refusing to connect. Try seeing if your Mac is compatible with the device. It is unlikely as Apple tries to maximize compatibility with external accessories, but sometimes some slip through the cracks and the Mac cannot recognize it.

I hope this all helps!

I am having the same error on a 2018 MacMini running Monterey (10.6.7) with an Crucial X6 external drive corrected directly to one of the four Thunderbolt 3 ports built into the Mini. It happens whenever the Mac wakes after more than a few minutes of Sleep. This appears to be a timing problem. I had this earlier with another External drive USB port connected to the Mini through a USB hub, which I replaced because I thought it might be defective. I then plugged that external drive into a USB port on a 2017 MacMini running Monterey and did not get the Disk Not Ejected Properly error when it awoke from sleep. So this points to some problem that was in the OS at least since Monterey, depends in some way on what Mac is used, and does not depend simply on USB Hubs. I agree this is an Apple bug that Apple needs to address.

Same with me. Ever since I bought a new MBP 2023 M2Max with Ventura, two external USB3 OWC "toasters" with removable bare drives eject multiple times an hour with the machine on or asleep. They never had this problem under Big Sur on my trusty (but slow) 2015 MBP.

It's obviously an OS bug but **** will freeze over before anyone inside the Apple cone of silence ever admits it. We just have to hope that in some future OS security update, it is quietly fixed.

I updated to Ventura a while back and am still having the problem with my 2018 MacMini. It's only with one of my external drives, a Crucial X6 1 TB portable SSD, but it's a pain. It also can obscure problems with other drives when a long list of "Disk Not Ejected Properly" alerts makes you overlook a warning about another drive going bad. Agree Apple needs to fix this.

As far as I can tell, the ONLY drive attached to my MacMini 2018 that triggers "disk not ejected properly" errors is my Crucial XC SSDrive. I get anywhere from one to several alerts when I wake the Mac up in the morning, and one or two sometimes when I take a break during the day. Only rarely do I find any problems with the drive. It is partitioned into two drives used for backup of two drives on the Mac, and once or twice they could not be detected for a backup.

This is wacky and frustrating. SOmewhere I saw a suggestion that the problem might be the Crucial X6 SSD was responding too fast or two slow for the Mini.

I have the same very frustrating issue... hey it's a Mac, so it just works, NOT. I get the message even when I eject the disk before I shut down... so fix the OS please. Oh wait, I wonder if it's fixed in Sonoma, not that I am excited or interested to update to yet another version of OSX... is it just more stuff to fix? It really gets old... and I'm not even a software developer. It's the Apple treadmill that never stops, it just means you need a new machine every few years.

I have some tentative good news. I checked with Bombich, the publishers of Carbon Copy Cloner, because the "disk not ejected properly" triggered backup problems, and they said the problem was most likely a faulty drive, cable, or port. I then checked with support at Crucial, the maker of the drive that had been giving me problems. They went through a series of questions, then suggested the problem was the connection between the Thunderbolt 3 port on my 2018 MacMini and the drive, and had me move to a different port. That seems to have worked; I have not had a repeat in a couple of the problem in a of days.

I would suggest trying that with a couple of caveats.

• I didn't get the "disk not ejected properly" warning every time the Mac wakes from sleep, so I could just be lucky for a few days and it might come back (at which point I will check with Crucial again and ask for a replacement)

• The problem could be a bad drive or cable, so just moving the drive to another connection might not solve the problem.

That said, it's probably worth trying if you have a spare port.

All I can say is that a week after following instruction from Crucial to move my Crucial drive to a different Thunderbolt port on my MacMini 2018 I have not had any more Disk Not Ejected Properly messages. What they said, the problem also might originate with other connections, either a cable or a Hub. I'd suggest it's worth trying or at least complaining to the manufacturer of the drive that's giving you problems.

I spoke too soon. Yesterday I had one "disk not ejected properly error" in the morning and this morning I had three. The problem is back and that tells me that it may be a flaw in the Crucial Drive that was temporarily fixed by switching ports, or that it may be something in the Mac or its software. I will be pursuing Crucial's tech support first.

I have been having this problem with a 1 Tbyte Crucial X6 solid-state drive on my 2018 MacMini and contacted the supplier. At first, they said I needed to move the drive to a different port on the Mini, which stopped the disk ejection errors for about 10 days before it started again. Yesterday I complained to them again and got the following

"We would like to inform that we would request you to update the system and certain models of internal SATA drives might unexpectedly disconnect from your computer after your Mac wakes from sleep. This can occur if your Mac automatically goes to sleep or if you manually put your Mac to sleep. We would like to inform that to resolve this issue, update to macOS Ventura 13.5 or later." This seems to imply that Crucial thinks it may be an incompatibility between the MacOS and the Crucial drive.

I had already updated to Ventura 13.5, but I upgraded to 13.6.1 and will see what happens.