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

Still getting this error message soon after I upgraded to Sonoma 14.0. Clearly the bug is not being taken seriously at Apple

-Carl

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.

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.

If Apple still had Time Machine hardware, they might care. They don't. So they don't, apparently.

I still have this with my M2 Pro Mac Mini when backing up to a QNAP NAS using Time Machine, OS & all apps/firmware up to date. Backup will complete if I sit and kerep pressing 'Backup Now', TM still backs up wihout issue to my 2 locally connected USB Drives, 1 via USB-C, 1x USB-3.

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.

Regretfully unhelpful: this set of "resources" do not appear to have been updated for Ventura. Additionally, these resources do not address the problem reported, which appears as a spontaneous early disconnect of the backup disk and not a failure or inability to connect to the disk.

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 ...

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 already have that feature turned off. This is starting to happen during the day while I am working on the computer. D is my backup drive, a 2 TB SSD drive. E is a 2 TB drive also but is not included in the backup.

Hooray!! Finally, with Sonoma 14.5 I no longer get the message when I wake my M2 Mini from sleep. Thanks Apple! The Micron 2TB SSDs and two hard drives show up without any message.

For what it's worth, my M1 MBP still has the problem even on Sonoma 14.5. It's less frequent, but it still happens.

Yep, If I constantly restart the network backup it will complete after 15-20 attempts, it then needs to verify this backup, so a previously automated & reliable backup now needs me to pay it 100% attention for a week. So a total showstopper. QNAP are adamant it’s not their NAS, so it’s down to Apple.