My Time Machine backup is stuck

I have the same problem, my last backup completed on 5th of September, since then, not a single one on this particular disk completed successfully.

I will not erase previous backups until the release of the next macOS update to see if that resolves something. I have a separate time machine backup disk that works flawlessly.

You could run First Aid on the TM drive but it will take a long time. Mine took about 6 hours.

How much free space do you have on your MBP's boot drive. If there isn't enough for a local snapshot there will be problems.

Have you installed and run any "cleaning", "optimizing", "speed-up", anti-virus or VPN apps on your Mac?

marc_ch wrote:

Hello all

I am currently trying to create a Time Machine backup of my MacBook Pro 14-inch, 2023 Apple M2 Pro running macOS 13.5.1 (22G90). 

Up to now, I have been able to create backups on my external hard drive without any problems. But now I'm facing the problem that the Time Machine backup keeps stopping at the same place. Even after hours of waiting, there is no progress. For example, the backup gets stuck at 5.7% / 2.5 GB. I have already erased and partitioned the hard drive several times (GUID, APFS).

I have searched via Terminal or Console for an error message. I get the following error message:

Console: Failed to create volume info from disk '<TMDisk: 0x1628e2a00> '/System/Volumes/Data/home'', error: missingURLForRemounting

Terminal: 2023-09-02 17:09:01  Failed to create volume info from disk '<TMDisk: 0x16281d800> '/System/Volumes/Data/home'', error: missingURLForRemounting

Unfortunately I cannot find this path on my MacBook. So I am at the end with my knowledge and ask you for help. What do I have to do to get the backups working again?

Time Machine issues—

"Time Machine has completed a new backup for you"

or get a message saying, "it can't create the backup,"

or “failed to complete the backup, ” 

or “Preparing backup”

If any of these message appear repeatedly —the Time Machine drive is operating in a state of failure.

The resolve would be to replace the drive.

try another drive and compare your results..

I'm having this exact same issue, same conditions, and even bought a brand new drive to see if that fixed it. It did not. I am pretty sure @marc_ch is not seeing disk failure here, but something else.

There's even a crash report:

marc_ch wrote:

Thanks for your answer!

1: Hm, First Aid unfortunately does not help. I had to erase the hard disk several times because nothing else worked.

That was my next recommendation.