Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

polyphenol

macrumors 68020
Original poster
Sep 9, 2020
2,202
2,717
Wales
Since I got my M4 Mac mini, I have been doing backups to the same external SSDs I had used on my old M1 Mac mini.

I’d originally setup the M4 by restoring from one of the drives. I cannot remember in detail what I did but initially I thought both drives had been imported/connected properly.

However, I found that one drive would often report that the scheduled backup had failed. Can’t remember if it worked for a while or this started from the beginning. Had no idea why if happened. Each time it said that, I went to Time Machine and told it to backup now. And every time it was successful.

The backups to the other drive were always OK.

Basically, unattended backups too one drive always failed.

I had some suspicion that my USB hub was having power issues - and anyway the cables, his and connections needed tidying. That done, and the hub now receiving plenty of power, I crossed my fingers. But no, that didn’t help.

Over the past few days I have run First aid at every level on the problem drive. Fine at top level. Failed at container level. Then fine on the volume. Despite reporting an issue, it did not manage to repair it.

1734889208411.png


Getting thoroughly annoyed, I thought I wouldn’t lose anything by reformatting it. But Disk Utility flat out refused to let me. Rebooted and only connected the drive again once I was logged in - still could not erase it.

Hmm, maybe something in my system was confused. Took it to my MacBook Pro and tried to format it there. Again, though it physically connected - total refusal.

End of tether time. Connected it to my old Windows 10 PC. Deleted the partition!

Then reconnected it to my M4 mini, and set up a new partition, added it to Time Machine. And it is behaving.

Posting in case anyone has has a similar issue.

I read https://forums.macrumors.com/threads/time-machine.2431290/ but decided it looked somewhat different.

I have always used the latest macos releases - leaving at most a few days after an update.
 
Yeah this is a weird bug. For the longest time my wife MBA 15" M2 TM backup with 15.2 worked fine. My iMac M3 with 15.2 keep getting that error. Then recently the M2 started to do it also. It's always when the screen is sleeping and LOCKED. I've left the Macs to never sleep. Someone posted the image that I get and this is it. Also for some reason, someone at Apple decided that this is good. So make sure the Mac is not locked when your away or if its sleeping? I mean seriously Apple?
  • If Time Machine reports that the backup is delayed because some files are unavailable, make sure that your backup disk is available and your Mac is unlocked. Then choose Back Up Now from the Time Machine menu.

Screenshot 2024-12-03 at 9.19.11 AM.png
 
  • Like
Reactions: polyphenol
Yeah this is a weird bug. For the longest time my wife MBA 15" M2 TM backup with 15.2 worked fine. My iMac M3 with 15.2 keep getting that error. Then recently the M2 started to do it also. It's always when the screen is sleeping and LOCKED. I've left the Macs to never sleep. Someone posted the image that I get and this is it. Also for some reason, someone at Apple decided that this is good. So make sure the Mac is not locked when your away or if its sleeping? I mean seriously Apple?
  • If Time Machine reports that the backup is delayed because some files are unavailable, make sure that your backup disk is available and your Mac is unlocked. Then choose Back Up Now from the Time Machine menu.

View attachment 2464921
Thanks for that, I'll explain below why your reply has triggered my brain!

But I still don't understand why I had to go round the houses to do what First Aid should have managed?

Yes, that was how it looked to me. I've never set my mac to lock itself until I've left iot for hours. And backups only take a few minutes.

But if you invoke iPhone Mirroring, the Mac locks much, much faster. I notice if I leave my MBP open and, as far as I am concerned unlocked, then go to make a cup of coffee or whatever, it will be locked by the time I get back. Thankfully, my watch almost always unlocks it almost immediately. Or touch if my watch is charging.

Could this be why Time Machine seems to think it is locked even when we users think of it as not being locked?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.