Disk not ejected properly "Backups of ..." on Ventura

Same experience here on an M2 MacBook Pro 16 and an iMac Pro.

With Time Machine configured to back up to a Synology NAS over the SMB/CIFS protocol, I get this issue if I configure the machines to sleep when not used. Neither has an issue if I disable sleep.

smarrinan wrote:

If I don't let my computer sleep, the errors stop.

If I enable "Prevent automatic sleeping when display is off"

Under Displays->Advanced...

A workaround that many of us use is to uncheck this checkbox to prevent the Mac from sleeping. Instead just use the screen saver:

And shut down the Mac at night instead of sleeping. That has an added benefit due to shutting down and rebooting in the AM clears out temporary system and application cache and swap files which helps system performance.

I had a similar issue with MacBook Pro (M1 Max) when upgrading to OSX Ventura 13.4. TM backup to Synology NAS (DS1515+, DSM 6.2.4.x) was giving me "Disk not ejected properly" message and I was able to resolve the issue after researching the matter as follows:

1. Reinstalled Ventura 13.4
2. Upgraded Synology NAS to DSM 7.1.1.x
3. Ran initial TM Backup from Macbook Pro to a new folder on the Synology NAS in Safe Mode

It was important to run the 1st run of TM Backup in Safe Mode, otherwise I continued to receive the "Disk not ejected properly" message.

Hope this helps ...

It seems like Ventura 13.3 has fixed the issue. Since the update, I haven't had any disk ejected messages.

If I don't let my computer sleep, the errors stop.

If I enable "Prevent automatic sleeping when display is off"

Under Displays->Advanced...

I have the exact same problem with my Mac Studio M1 and QNAP. It is on Ventura 13.3.1 now and still happening. It seems like the system/network sleep causes these disconnects. If my computer is active, they all work fine.

I also have a similar issue with my SuperDuper backups to the same QNAP NAS. If I run the backups manually, which would have the computer awake already, everything works fine, SuperDuper and Time Machine. If I let the machine go idle and wake it up with the keyboard, I see a bunch of these errors.

There are many suggestions in this thread that this problem is related to the Mac sleep settings. This I find is true, in a non-intuitive way. Following different hints about the lock screen I made several changes and the problem of getting the messages about the disc being ejected improperly has ceased. I don't ever select the sleep command any more, either. Setting the screen saver to come on after one hour might be key, and Turn display off on power adapter is set to one hour, 30 minutes.. Give this a try, it worked for me.

-Carl

Not sure the drives are the problem for this error, my testing points to a problem in Time Machine or a change in the drivers for storage causing an incompatibility. As given in long version below, I only have this problem on drives when they are in use by Time Machine.

Use two hard drives for Time Machine of 5 external drives all on Thunderbolt/USB hub. 1 2TB, 1 4TB NVME and 3 3TB Hard drives.

After getting the Time Machine Disk Not Ejected Properly on the two 3TB Hard Drives only, not on volumes, EVEN after awakening from a sleep, I removed them and changed in the 2TB and 4TB NVME drives to Time Machine, the thought being the NVME devices are new, maybe the HDs are too old or there is some incompatibility with platters. Same Problem, still get the message Every time I shut down without ejecting and whenever the MacBook Pro sleeps a long time, like overnight.

Now I have switched back to the 2 3TBs on Time Machine and the NVME drives just volumes. And in another workaround to solve a problem I see online all the time that apple won''t fix or tell us the status of, I live with the errors after sleep and do a shut down instead of just closing the lid to prevent some of the failures. Very annoying.

I have not tried deleting the Time Machine drives and then going into safe mode to reinstall them and do the complete first backup in safe mode.

equipped with MacBook Pro 2023 16"

All drives APFS. NVME 4TB WD Black 870, 2TB similar, 3 3 TB are Seagate 7200 and old but little used.

I am registering the same experience. I have a 2022 MBP 16" running the latest version of Ventura. Time Machine is configured to save backups to a network drive (a nas device). This has worked flawlessly for years. Coincident with the Ventura upgrade, I now get a random "Disk Not Ejected Properly" error message from MacOS when I wake the laptop. Note that I ensure that any running Time Machine backup has fully completed and cleaned up before sleeping the machine. There is most certainly a bug that was introduced with Ventura that causes the machine to think that the network drive was improperly ejected after lid close/sleep. After wakeup, the machine resumes Time Machine backups without issue.

For the reply by Neil224, while appreciated, I don't believe you understood the issue. The remote drive (hardware) remains mounted to a second Mac and shared as a Time Machine drive. The problem is the sparsebundle on that drice. Time Machine is somehow not unmounting the disk image correctly, and we get the "disk not ejected properly" message for the sparsebundle disk image, not the physical drive. This is happening to me constantly. And whatever it's doing, one time it corrupted the sparsebundle (the one on the shared drive attached to the remote mac) rendering it unopenable.

I use an external disk directly connected to my MacBook Pro running Venture 13.6

It is the latest version available as of 10/1/2023.

What worked for me was keeping the cursor over the icon of the time machine

on the very top of the screen until the backup is finished.

I know it sounds crazy, but it worked.

I finally got frustrated and bought a new SSD dock (holds 2 cards) https://www.amazon.com/dp/B09646W9PX?psc=1&ref=ppx_yo2ov_dt_b_product_details and a new 10 Port USB hub https://www.amazon.com/dp/B07Q3TYF15?ref=ppx_yo2ov_dt_b_product_details&th=1.

Somehow I think that the software upgrade made on OS X by Apple didn't play nicely with the software in these devices. Or there was a chip overheating in one of them. For now this seems to have fixed what was a regular occurrence. Hope that I haven't spoken to soon. I'll let everyone know.

Hello Paul Collins,

The following resource can help resolve connection issues with another computer: If your Mac can’t connect to another computer - Apple Support

Cheers.