From Newsgroup: comp.sys.mac.advocacy

On 2025-02-16 07:01, -hh wrote:

On 2/15/25 19:02, Alan wrote:

On 2025-02-15 06:46, -hh wrote:

Been struggling with this problem for awhile now -- error reads:

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

There's various 'rebuild' suggestions from Apple, but the following
fixed it for me

1.  On your Mac, open System Settings; goto "Lock Screen", see if
"Require password after screen saver begins..." is greyed out. If so,
then continue.

2.  On your Mac, launch the iPhone Mirroring App.

3.  Open "Settings" from its menu.

4.  Change from "Automatically Authenticate" to "Ask every time".

5.  Close the dialog box & Quit the iPhone Mirroring App.

6.  Go back to System Settings & check the Lock Screen settings - the
"Require password after screen saver begins..." should no longer be
greyed out. Try setting it to something other than "Immediate" for now.

Done (maybe do a reboot now to be sure)

Overall, I think that the iPhone Mirroring App's automatic
authentication is the root cause of this TM error.


-hh

I'm not sure you need to do anything, HH.

Well, it is indicating a failure to complete the backup(s).

After clicking on the (red "i"), the full error message is:

[quote]
Time Machine couldn't complete the backup to "[drive name]"

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

What does it say for when the last back was?

Days prior, not the most recent attempt which failed.

Is that not changing from some past date?

No, its not changing.

FYI, an update to the above: the above solution didn't work after I
reduced the time from 8hrs to less (eg, 15 minutes).  Damn.

Other reading on this problem comments on suspecting that USB drives attached through a hub could be associated too.  I have noticed a brief
TM status panel dialog that has a comment along the lines of saying that
a TM backup attempt will resume once the drive is reattached, so maybe there's some sort of (deep?) sleep / logically being no longer attached element too...but this shouldn't apply for an ongoing TM session
*failing* to complete, as in that instance, the drive is already
attached and doing data I/O for the backup.

HH, did this ever get resolved?
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

On 9/4/25 14:27, Alan wrote:

On 2025-02-16 07:01, -hh wrote:

On 2/15/25 19:02, Alan wrote:

On 2025-02-15 06:46, -hh wrote:

Been struggling with this problem for awhile now -- error reads:

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

There's various 'rebuild' suggestions from Apple, but the following
fixed it for me

1.  On your Mac, open System Settings; goto "Lock Screen", see if
"Require password after screen saver begins..." is greyed out. If
so, then continue.

2.  On your Mac, launch the iPhone Mirroring App.

3.  Open "Settings" from its menu.

4.  Change from "Automatically Authenticate" to "Ask every time".

5.  Close the dialog box & Quit the iPhone Mirroring App.

6.  Go back to System Settings & check the Lock Screen settings -
the "Require password after screen saver begins..." should no longer
be greyed out. Try setting it to something other than "Immediate"
for now.

Done (maybe do a reboot now to be sure)

Overall, I think that the iPhone Mirroring App's automatic
authentication is the root cause of this TM error.


-hh

I'm not sure you need to do anything, HH.

Well, it is indicating a failure to complete the backup(s).

After clicking on the (red "i"), the full error message is:

[quote]
Time Machine couldn't complete the backup to "[drive name]"

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

What does it say for when the last back was?

Days prior, not the most recent attempt which failed.

Is that not changing from some past date?

No, its not changing.


FYI, an update to the above: the above solution didn't work after I
reduced the time from 8hrs to less (eg, 15 minutes).  Damn.


Other reading on this problem comments on suspecting that USB drives
attached through a hub could be associated too.  I have noticed a
brief TM status panel dialog that has a comment along the lines of
saying that a TM backup attempt will resume once the drive is
reattached, so maybe there's some sort of (deep?) sleep / logically
being no longer attached element too...but this shouldn't apply for an
ongoing TM session *failing* to complete, as in that instance, the
drive is already attached and doing data I/O for the backup.

HH, did this ever get resolved?

Yes, I believe so.

For those who've experienced it, my suggestion is to do something that's
very simple & stupidly obvious:

1. Open "System Settings"
2. Open "Privacy & Security"
3. Open "Full Disk Access"
4. Enable "Time Machine" (to have full disk access)

If Time Machine isn't listed, hit the "+" at the bottom to add.


-hh


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.mac.advocacy

On 2025-09-04 13:37, -hh wrote:

On 9/4/25 14:27, Alan wrote:

On 2025-02-16 07:01, -hh wrote:

On 2/15/25 19:02, Alan wrote:

On 2025-02-15 06:46, -hh wrote:

Been struggling with this problem for awhile now -- error reads:

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

There's various 'rebuild' suggestions from Apple, but the following >>>>> fixed it for me

1.  On your Mac, open System Settings; goto "Lock Screen", see if
"Require password after screen saver begins..." is greyed out. If
so, then continue.

2.  On your Mac, launch the iPhone Mirroring App.

3.  Open "Settings" from its menu.

4.  Change from "Automatically Authenticate" to "Ask every time".

5.  Close the dialog box & Quit the iPhone Mirroring App.

6.  Go back to System Settings & check the Lock Screen settings -
the "Require password after screen saver begins..." should no
longer be greyed out. Try setting it to something other than
"Immediate" for now.

Done (maybe do a reboot now to be sure)

Overall, I think that the iPhone Mirroring App's automatic
authentication is the root cause of this TM error.


-hh

I'm not sure you need to do anything, HH.

Well, it is indicating a failure to complete the backup(s).

After clicking on the (red "i"), the full error message is:

[quote]
Time Machine couldn't complete the backup to "[drive name]"

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

What does it say for when the last back was?

Days prior, not the most recent attempt which failed.

Is that not changing from some past date?

No, its not changing.


FYI, an update to the above: the above solution didn't work after I
reduced the time from 8hrs to less (eg, 15 minutes).  Damn.


Other reading on this problem comments on suspecting that USB drives
attached through a hub could be associated too.  I have noticed a
brief TM status panel dialog that has a comment along the lines of
saying that a TM backup attempt will resume once the drive is
reattached, so maybe there's some sort of (deep?) sleep / logically
being no longer attached element too...but this shouldn't apply for
an ongoing TM session *failing* to complete, as in that instance, the
drive is already attached and doing data I/O for the backup.

HH, did this ever get resolved?

Yes, I believe so.

For those who've experienced it, my suggestion is to do something that's very simple & stupidly obvious:

1. Open "System Settings"
2. Open "Privacy & Security"
3. Open "Full Disk Access"
4. Enable "Time Machine" (to have full disk access)

If Time Machine isn't listed, hit the "+" at the bottom to add.

Good to know.

Interesting, though.

I've had similar messages, but I got successful backups after seeing
that message, and I just checked that Time Machine was NOT in my list
for Full Disk Access.

Weird.
--- Synchronet 3.21a-Linux NewsLink 1.2