Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Time Machine "Waiting to Compete First Backup" but looked like it did create the backup in ".inprogress" folder, and is running hourly and creating ".interrupted" folders

Time Machine keeps reporting “Waiting to Complete First Backup”, but keeps appearing to run hourly backups. There are a series of hourly backup folders with “.interrupted” extension on the external backup drive, and also an “.inprogress” folder, which does appear to contain a full backup.


This is on a brand new MacBook Pro 2021 I just got this week.


At first, when I moved the external USB connected Seagate backup drive from my old MacBook to my new one, and “inherited” the backup, everything was working fine.


Then after a while it started reporting that the oldest backup was always the same one from the night before.


I tried erasing the drive (including a double wipe), deleting the com.apple.TimeMachine.plist, rebooting and starting a fresh backup. Looked like it was running fine, first run took a few hours, but after appearing to finish in System Preferences it reports oldest backup is None and “Waiting to Complete First Backup” in the menu bar. But does keep running every hour, and in System Preferences there is a time for the Next backup which keeps advancing after each run.


I’m not sure, but the problem might have started after I did the software update to Monterey 12.0.1 from the factory installed 12.0.


Any suggestions to try much appreciated.

Posted on Oct 31, 2021 10:58 AM

Reply
Question marked as Best reply

Posted on Nov 2, 2021 2:26 PM

Managed to fix it myself. Elsewhere I found how to look at the Time Machine log file using the following in Terminal:


log show --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info > tmlog.txt


Opened tmlog.txt and found the reason for the failure on the last line:


Backup failed (104: BACKUP_DELAYED_UNFINISHED_PROTECTED_FILES)


Looking further up, found several files with the following error:


"Failed to acquire device lock assertion for........Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument""


(all the errors were with com.apple.findmy.FindMyWidget**** files)


Booted into Recovery Mode and ran Disk Utility. Ran First Aid on the startup disk volumes, containers & disk per this:


https://support.apple.com/en-us/HT210898


I didn't notice Disk Utility reporting it fixed any problems. But after rebooting, the next time Time Machine ran it finally completed the first backup!! And has been running smoothly since.

Similar questions

47 replies
Question marked as Best reply

Nov 2, 2021 2:26 PM in response to Kevin Strong

Managed to fix it myself. Elsewhere I found how to look at the Time Machine log file using the following in Terminal:


log show --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info > tmlog.txt


Opened tmlog.txt and found the reason for the failure on the last line:


Backup failed (104: BACKUP_DELAYED_UNFINISHED_PROTECTED_FILES)


Looking further up, found several files with the following error:


"Failed to acquire device lock assertion for........Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument""


(all the errors were with com.apple.findmy.FindMyWidget**** files)


Booted into Recovery Mode and ran Disk Utility. Ran First Aid on the startup disk volumes, containers & disk per this:


https://support.apple.com/en-us/HT210898


I didn't notice Disk Utility reporting it fixed any problems. But after rebooting, the next time Time Machine ran it finally completed the first backup!! And has been running smoothly since.

Nov 8, 2021 10:32 PM in response to patrick.probst

Since in your case and my case the problems appear to be all with com.apple.findmy.FindMyWidget**** files/containers, wondering if the Find My app is working properly, and also if you can add the "Find My" Widget to your Notification Center (https://support.apple.com/en-us/HT211789). Perhaps opening the app and adding the widget may cause the app to correct whatever is wrong with the containers that is causing Time Machine to fail? Easy enough to try. I don't think you can delete the Find My app and reinstall, since it comes with the OS. I guess you could temporarily remove all the offending containers off disk to an external drive or flash drive, then see if Time Machine will run, and also if then running Find My and adding the Find My widget will cause the app to create new versions of the containers.


Obviously in my case I can't try any of this since First Aid fixed it for me.


Maybe start a new discussion that specifically mentions in the title that containers associated with the Find My app are causing Time Machine to fail after updating from 12.0 to 12.0.1?

Nov 9, 2021 3:08 PM in response to frédéric259

I had some chats and a call with Apple support today about this concern, because I need backups. I did several things qithout any success. They advised me to use the safe mode and doing a backup there.

That fixed the problem for me and the backup went through in safe mode. It took time, but time machine ran through.


After a regular reboot my time machine is running again like before. And the 104 error message (above) went away. Up to now I do not have any idea why this works, but some magic must be these days;-)


Safe mode:

https://support.apple.com/en-us/HT201262

Nov 6, 2021 12:57 PM in response to Kevin Strong

I had exactly the same problem on my Apple Silicon 16" MBP, which was updated from factory macOS 12.0.0 to macOS 12.0.1.


I was able to resolve the issue the same way as the OP, by running First Aid in Recovery Mode: No problems were found but the time machine backup magically worked the next time.


Looks like there might be a fairly reproducible bug here.

Nov 7, 2021 2:58 AM in response to Kevin Strong

I had also exactly the same issue with Mac OS 12.0.1 on my Mac Mini M1.... in the log I have the same info:


"Failed to acquire device lock assertion for........Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument""

Backup failed (104: BACKUP_DELAYED_UNFINISHED_PROTECTED_FILES)


These findmy-Folders are a problem for all UserLibrary folders of all users. But unfortunately, running First Aid in Recovery Mode did not fix my problem :-(


Any other ideas?


Nov 8, 2021 3:55 AM in response to patrick.probst

No, I tried several First aids run in sequences on all layers as described above. Backup not finishing on USB nor on NAS shows same behaviour.


I have same BACKUP_DELAYED_UNFINISHED_PROTECTED_FILES error message.

Any other ideas?


@Apple: For me, not having a working backup is a serious problem, this has to be investigated and fixed immediately.

What I do not really like in that case is that I have to find a solution myself to keep working such an relevant feature.

If a mouse or something special does not work ok, but not the backup.



Nov 9, 2021 12:17 AM in response to patrick.probst

I have a second Monterey installation on an external SSD. I moved the offending files to another location mounting the internal drive after having booted on the SSD. Rebooted on the internal drive, did the backup, and booted again on the external SSD to restore the files that were moved.


What's is that my Monterey on the external SSD backups itself without any issue. Maybe could I try the replace the internal com.apple.find* files with the ones from the external drive ?

Nov 9, 2021 10:05 PM in response to Kevin Strong

I have the same issue with my new 16" MBP (M1 Pro) running 12.0.1 and an external 4TB USB drive (I've actually tried two brand-new drives, one from WD and one from Seagate). Backing up from Safe Mode and/or using First Aid on the startup disk in Recovery mode did not help. I'm still seeing the errors for the com.apple.findmy.FindMyWidget* nodes in the log, and the initial backup never finishes. I'm trying this again after excluding the offending paths by running "sudo tmutil addexclusion -p ..." for each of them, and hopefully this works. If it does, I'll remove the exclusions to see if the second incremental backup finishes...

Nov 10, 2021 5:11 PM in response to Kevin Strong

Here is an update on my situation (in case someone is interested): after excluding the "com.apple.findmy.FindMyWidget*" directories from Time Machine, the first backup completed successfully. However, after removing the exclusions, these directories were not added to the subsequent backups (which were also successful). I wonder if they are included in the backups for others who were able to finish the first backup by booting into safe mode, or if anyone has ever tried a full system recovery from such a backup... also, I'm not sure if the absence of those directories would have any impact on the system operation (perhaps they will be re-created automatically?)

Nov 10, 2021 6:54 PM in response to dpugachev

They are all there in my Time Machine backups. I did notice that in Finder they are no longer displayed as "com.apple.findymy.FindMy*" folders but as "FindMy*" folders, though Get Info does show that the names are "com.apple.findymy.FindMy*". Since they are all specifically for the Find My app, I don't think they should have any impact on general system operation, but I assume they are needed for running Find My Mac.

Time Machine "Waiting to Compete First Backup" but looked like it did create the backup in ".inprogress" folder, and is running hourly and creating ".interrupted" folders

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.