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

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.

For anyone who has been experiencing this problem and has set their Time Machine destination to a Synology NAS product that is still running the legacy Synology DSM 6.x series operating system, there may be a fix (unconfirmed). Synology just released an update that includes the following fixes:

Fixed Issues

1. Fixed an issue where files shared via SMB may not be discoverable through macOS Ventura's Spotlight search.

2. Fixed an issue where files shared via AFP may not be discoverable through macOS Ventura's Spotlight search.

Here is the link to the Synology DSM release notes: https://www.synology.com/en-us/releaseNote/DSM

Again, I have not confirmed that the issue in this thread is addressed by this Synology update. The Spotlight file indexing service may be unrelated to a macOS Ventura machine losing its connection to network based Time Machine store after sleep.

I realize that people who use a Synology 6.x NAS as their Time Machine target may be a narrow audience. I will re-post once I confirm whether this is fixed or not.

The Synology update did not fix this issue. While I only occasionally experience the "disk ejected improperly" error, I did see the error again after updating my Synology 6.x DSM operating system. I have my Time Machine backups on manual and I do not let my MBP sleep while performing a backup. But occasionally upon lid open/wake I will get the error.

I also do Time Machine on a Synology running DSM 7.1.1, and I experience this issue on 3 ventura machines: A MacStudio M1 ultra, a MacBook Pro Intel and a MacBook intel (all upgraded to Ventura 13.3). What is different between the different clients is the amount of messages. On the MacStudio after a night in sleep I normally find between 4 and 8 "Disk not ejected properly" messages. On the other two the messages come out only occasionally

I too have been using Time Machine on a Synology for many years and have been suffering from this bug since upgrading to Ventura. Currently, I'm running Ventura 13.3.1 on a MacBook Pro and backing up to Synology NAS running DSM DSM 7.1.1-42962 Update 5. Every time my MacBook goes to sleep, I see the Disk not ejected properly "Backups of ..." message upon resuming. The backups have become very unreliable. For instance, at this moment, when I browse Time Machine Backups, I can only go as far back in time as yesterday. Can't go back any further. It's been over six months since Ventura was released and people reported this problem. Still no fix from Apple?

thanks for the suggestions, but that seems like a lot of bother compared to clicking dismiss on the notifications. It's easy to make them go away; they're just annoying. Hopefully Apple will resolve this quickly.

Interestingly, this problem does not seem to occur on our equally new 14 inch MBP. Both the Mini and the MBP have the same M2 Pro processor.

I can tell you that Ventura 13.4.1 has the same problem. The best part of this conversation is knowing that this is simply an annoyance not a real problem . My Seagate remounts, and life goes on. Someday they will fix it, one hopes.

Oh well we'll see what people say about 13.5; I haven't seen that update notification (and I wonder why....)

-Carl

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.

Level 0, 0 points

To those with Synology backup equipment, you are not alone with the "Disk Not Ejected Properly" problem. I have been doing my Time Machine backups on an AirPort Time Capsule (version 7.9.1) for a long time, and I have now been getting the same message, seemingly since I upgraded to Ventura. I have a 2017 iMac (3.8 Ghz Quad-Core Intel Core i5, for you youngsters) now running Ventura 13.6.1. The "disk eject" message started happening a couple of updates ago. I fear that built-in obsolescence will prevent me from receiving another Ventura update with a solution, since I already can't upgrade to Sonoma with this system. Another Community Specialist or Level 10 solution won't help me much either, given my limited, level 0 abilities. I share my Airport with another, even older Mac, so I am guessing that the Ventura testing regimen might have missed this problem scenario, but I see that others who are running more current systems see it too. Has anything simple been suggested lately to make this annoying message go away?

No suggestions from me-- but I have Macbook Pro running Sonoma 14.0 , and I use a Seagate external backup drive. The same message pops up several times a day (from both partitions of the drive, so actually 2 messages) , seemingly with no other related activity. Or maybe when the Time Machine finishes a backup? Yes annoying but fortunately not dangerous.

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.

This thread is mostly dead for months, but I'm chiming in to share that I'm on a Mac Studio M1-Ultra w/ a QNAP NAS and I'm having the same annoying issue. I did also (a few months ago) have a corrupted Time Machine image... perhaps from this improper-disconnecting, I just blew it away and started over.

I was suspecting that it could have been due to my wi-fi, but I've recently switched to a hardwired GbE connection, and I just did a fresh TM backup, and after the first one completed, I got the same annoying message after waking from sleep. I'm running Ventura 13.6.4.

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

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.

13.5 does not seem to have resolved this. On to 13.6?