You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Time Machine did not finish backing up because some files were unavailable. Backups will resume when your Mac is unlocked.

I've had no trouble with Time Machine until updating my Mac Mini M2 to OS 15.0.1. After the update, I constantly get the message "Time Machine did not finish backing up because some files were unavailable. Backups will resume when your Mac is unlocked." The backups seem to run fine until reaching about 80% then stall before the message appears. I've tried different ports, different USB C hubs, different cables etc. with the same result. I've scann the resources here and found nothing current or helpful on this issue.

Mac mini (M2, 2023)

Posted on Oct 25, 2024 5:25 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 25, 2024 2:50 PM

After my initial post, I tried erasing my backup drive and starting over with a new time machine backup, but I still got the same message.


After exhausting everything I could think of, I called Apple Care. I spoke with a representative who let me explain everything I had already tried and he indicated that I had covered most of his solutions matrix, so we didn't waste time going over that again (GREATLY APPRECIATED!). I was put on hold for a short time by the rep then asked to do the following:


  1. Eject my backup drive and disconnect it from my Mac;
  2. Open time machine and tell it to forget my backup drive;
  3. Restart my Mac in Safe mode;
  4. Reconnect my backup drive;
  5. Open time machine and tell it to use my backup drive for a new backup;
  6. Let time machine format the backup drive and complete an initial backup to my backup drive;
  7. Confirm the initial backup finished without errors;
  8. Restart my Mac in normal (not safe) mode.


I completed the above steps in pretty short order and have since had 5 hourly backups with no errors. This seems to have solved the problem.

57 replies
Question marked as Top-ranking reply

Oct 25, 2024 2:50 PM in response to Kerry Kinkade

After my initial post, I tried erasing my backup drive and starting over with a new time machine backup, but I still got the same message.


After exhausting everything I could think of, I called Apple Care. I spoke with a representative who let me explain everything I had already tried and he indicated that I had covered most of his solutions matrix, so we didn't waste time going over that again (GREATLY APPRECIATED!). I was put on hold for a short time by the rep then asked to do the following:


  1. Eject my backup drive and disconnect it from my Mac;
  2. Open time machine and tell it to forget my backup drive;
  3. Restart my Mac in Safe mode;
  4. Reconnect my backup drive;
  5. Open time machine and tell it to use my backup drive for a new backup;
  6. Let time machine format the backup drive and complete an initial backup to my backup drive;
  7. Confirm the initial backup finished without errors;
  8. Restart my Mac in normal (not safe) mode.


I completed the above steps in pretty short order and have since had 5 hourly backups with no errors. This seems to have solved the problem.

Nov 3, 2024 6:57 AM in response to Kerry Kinkade

..... And I can confirm the issue was fixed after the restore, but that was on macOS Sonoma, as soon as I uplifted to Sequoia the issue returned, as I expected.


I've just spoken to Apple Support again and she is going to investigate and cal me back tomorrow.


If it is any use to anyone my case is 10*******93.


If you have reported the case and have a case number please feed it back, as she did indicate she was not aware of any other reports. If you have not reported it please do so and feel free to reference my case number.


The more of us that report it the quicker it will get resolved.


[Edited by Moderator]

Nov 15, 2024 5:47 PM in response to Kerry Kinkade

It's just lazy customer support to ask users to wipe their TM drive and/or Mac hard drives (and restore or reinstall macOS). There is obviously a NEW bug in macOS 15 that is causing this when TM kicks off and the screen is locked. Obviously. Wiping everything only papers over the problem and DOES NOTHING to find the real issue.


I say "lazy" without any guilt. I do customer support for a software company and I always want to find the real cause rather than paper over it. Look how many people are impacted by this!!! The real number is 1 or 2 orders of magnitude more! (because people don't spend the time finding a place to post their problem)

Nov 22, 2024 11:03 AM in response to Kerry Kinkade

The latest things I'm trying:


  • Emptied the Trash Can
  • Rebooted the Mac
  • Wiped and formatted my TM backup drives (emptied the NAS TM share)
  • Set TM up to backup to external drives only (for now I've ignored the NAS share as it's slower)
  • [Still got the TM errors up to here]
  • Forced a Spotlight reindex (again)
  • Went into TM settings and excluded all external drives from the Backup
  • Went into Spotlight Privacy and excluded all external drives as well as network shares from being searched.


So far four TM backups with the Mac locked with no issues.

Nov 1, 2024 3:47 AM in response to Kerry Kinkade

I'm very sorry to say but the 'fix' didn't work for me at all. I went through all the steps in full, and this morning after being out for a walk, with the Mac locked I returned to find the errors were back!

Exactly the same situation, 'some files unavailable' so the backup could not complete.

Now I'm working on the Mac (that is it is unlocked) the backups are now taking place and completing without any errors.

Apple need to fix this issue.


Nov 6, 2024 2:02 AM in response to Kerry Kinkade

Guys yesterday I realised that Spotlight was not indexing things properly on my Mac. I then followed this support article, and added / removed the hard drive on the Mac as well as excepting a few drives.


This morning I accessed the Mac and I had no TM backup errors at all. W00t!


So is it worth you guys reinitialising Spotlight and seeing if it fixes your errors? Worth a try!



Oct 28, 2024 1:07 PM in response to Kerry Kinkade

I'm curious about the solution. I've the same issue which has occurred from Sequoia 15.0.1 onwards (now running 15.1). This is on a Mac Mini 2 Pro.


I have three TM backups:


  • external drive (via USB-A hub)
  • external drive USB-C
  • To a share on my Synology NAS


It looks like the solution involves getting the Mac into save mode and then reconnecting TM. I wasn't sure that was possible for the network share to the NAS, but if it is…


Then the big question is… when re-adding the drive into TM, what do you do with the existent TM backup, re-use it, or start again with a fresh backup?


I'm assuming here that for the NAS, the existing bundle in the share needs to be deleted from the NAS side of things?


Any further thoughts or info would be appreciated.

Nov 2, 2024 6:02 PM in response to dbrewood

This probably means that the workaround of sorts (deleting the backup sparse bundle is hardly a workaround) that works for Sequoia 15.0.1 does not work for 15.1. So, between 15.0.1 and 15.1 they made the bug worse. This must be all related to the security changes they make. Too much security?


Apple needs to fix this serious bug fast now that you have found the hard way that it is worse with Sequoia 15.1.


Nov 3, 2024 7:12 AM in response to mjmarch

Yep I saw that they had made the edit alas. I just checked and it seems we can't contact each other via PM on here either. You can try contacting me on Mastodon search for tekguru on the Vivaldi instance. Unless of course they edit this out too :)


I'll bite the bullet and stick with Sequoia and if needful backup manually until it is resolved. I'd class it as a critical issue they need to resolve.

Nov 13, 2024 2:37 PM in response to Kerry Kinkade

I'm having this issue, or one quite similar. I get the same error message "Time Machine did not finish backing up because some files were unavailable. Backups will resume when your Mac is unlocked."


I last Friday I migrated to a new M4 Mac mini, now running OS 15.1. That went without hitch. I took over (captured? whatever the term is) the old TM backup, and that seemed fine too. Backups happen on the regular TM schedule, but sometimes I do get this error message. When I do, if I manually trigger a TM backup, that takes place without incident. I just returned home after being out for a couple of hours. Screen was locked and mini was locked; my AppleWatch unlocked the mini. I see that 20 minutes ago a TM backup too place. So this problem, whatever it is, is not even consistent for me.

Nov 15, 2024 5:53 PM in response to envoy510

I found this on reddit:


log show --info --style compact --predicate '(subsystem == "com.apple.TimeMachine") && (eventMessage like[cd] "Failed * acquire device lock assertion*")' --last 8h


to find the file. For me (and others on reddit since macOS 15.0):


Timestamp               Ty Process[PID:TID]
2024-11-15 17:02:28.528 E  backupd[322:533fa9] [com.apple.TimeMachine:FileProtection] Failed to acquire device lock assertion for '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/max/2024-11-15-170051/Data/Users/xxxxx/Library/Containers/com.apple.findmy.FindMyWidgetItems/Data/SystemData/com.apple.chrono/snapshots/com.apple.findmy.FindMyWidgetItems/systemSmall---4259486853547037044----164.00w--164.00h--20.00r--0f--0.00t-0.00l-0.00b0.00t.chrono-timeline' (assertion state: <dropped>), error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"


Really seems like a new bug, Apple. Stop telling people to wipe their machines!!! Ask them for this info!!!

Time Machine did not finish backing up because some files were unavailable. Backups will resume when your Mac is unlocked.

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