Time Machine stuck "Preparing backup," out of obvious fixes

My Time Machine is permanently stuck in "Preparing backup." It's on a headless Mini running background stuff, so I didn't notice until recently that it hadn't run a successful backup since April.


There's plenty of room on the (large) backup drive, and backups from our home laptops continue to be processed successfully to that same drive.


After a couple TM restarts with no progress, I decided to jettison the entire Backups.backupdb folder, empty the Trash, and try again. I ran DU on the backup drive just to ensure there was no corruption. Then I rebooted just in case there was a session corruption. The Mini came up, asked me if I wanted to establish backups to one of my two large drives (promising), I chose the correct one, and it started the backup again. (It complained that it was backing up an encrypted disk to an unencrypted disk, but I told it I didn't care.) 12 hours later, it's still "Preparing backup."


I'm running the latest Mojave (10.14.6), i7, 32GB, 500G SSD (with only 132GB used), and there are 2TB spare on the backup drive, so it's not a system capacity problem. This is a new "initial" backup, so it's not a "too long since last backup" problem. Meters show kernel_task running at about 100% (one core), and pretty much nothing else other than a small WindowServer time. Together, backupd and backupd-helper claim under a second of total CPU time used.


I've run the "D" diagnostic on the Mini, booted to the Recovery partition and run DU on the internal as well as the backup drive. Everything is sparkling clean. And TM was running fine since I got this Mini in 2018, on this same volume, until it decided just to stop in April.


I'm tempted to start blowing away TM preference files, but I'm hesitant to shoot the wrong ones. I'm also hesitant to use Pondini's website, since I don't believe he survived to see Mojave released.


Suggestions?

Mac mini 2018 or later

Posted on Sep 13, 2020 2:55 PM

Reply

Similar questions

26 replies

Sep 14, 2020 11:35 AM in response to macswe

I'd still also like to know why kernel_task is eating up 100% of a core on an otherwise idle machine.


That may be a clue.


Refer to If kernel_task is using a large percentage of your Mac CPU - Apple Support. The content of that Apple Support document isn't very useful on its own, but if you delve into all possible causes it eventually suggests resetting that Mac's SMC: How to reset the SMC of your Mac.


If it's not already obvious all these troubleshooting efforts are delaying the creation of a recent TM backup... but you have to start somewhere. Decide if that need outweighs trying to figure out what's wrong, and consider buying a new TM backup drive—which you may need anyway pending the outcome of those efforts.

Sep 14, 2020 1:41 PM in response to John Galt

Yeah, I'm aware of the heat issue with kernel_task -- it hits my MBP every time ambient goes over 80°, and I used to use it on outside jobsites in AZ a lot. But that hits all the cores, plus I've never seen it on the Mini.


After restarting after removing the nonexistent folder, kernel_task seems to have stopped spinning. Yay!


Again, it's stuck at "Preparing backup." Now I am seeing the following errors in the log (I've seen them before, too). This whole "file:///" issue may be the key to the problem. I have no idea what it's trying to do here. There is a file .com.apple.timemachine.supported at the root of Tardis, but it's zero-length, and other discussions indicate it should be, so I don't think it's involved. There's nothing else in the hierarchy that looks like it would be involved in whatever TM is trying and failing to fetch.




Sep 14, 2020 6:32 PM in response to Old Toad

I ran DU First Aid on the TM drive back in the OP. Since I had completely removed the Backups.backupdb folder in order to start fresh, there was no multilinked anything remaining on the drive and the operation was quite prompt. On that drive there are only three sparsebundles of backups from three other household machines, plus a bunch of invisible cruft belonging to the system. The backup drive is in Spotlight privacy.


My boot drive is 130/500GB full, a pittance in today's terms. Of that, /Users takes under 13GB, and /Developer runs 2.5GB, the rest is all vanilla macOS. However, your question reminded me that there is also an external drive for large files, some of which does get backed up as well, and I had never yet checked that. DU loved it long time, but DiskWarrior said it was replacing the directory because the old one was too damaged to compare (no data was lost). For kicks, I also ran DW over the backup drive (since there is no multilinking on it yet) -- DW reported trivial corrections similar to those reported almost any time you run it.


I restarted TM, got the same spate of "file:///" errors, and it's been "Preparing backup" for about five minutes now. I'll let it run and see if that fixes it, I'm thinking my odds are only maybe 20%.


Sep 14, 2020 6:39 PM in response to macswe

Somewhere in Apple's TM troubleshooting guide it recommends DU First Aid for the backup and source volumes, the latter of which is frequently overlooked. That implies all source volumes.


DU loved it long time, but DiskWarrior said it was replacing the directory because the old one was too damaged to compare (no data was lost).


If the external drive is also being backed up, and it has problems, they are certain to return.

Sep 14, 2020 6:52 PM in response to John Galt

I've run DU First Aid on every volume on that system at least once in the past 24 hours, and DW on the two externals (the internal is APFS). They are now all as clean as they can be.


Both externals are RAID-1 (mirror) volumes that well predate this Mini; I expect the archival volume structures collected some damage during power outages or whatever, or maybe even due to some bug in a version of the RAID driver (SoftRAID). I'm still a bit fuzzled about how DU could say it was perfect, while DW said it was beyond use -- what kind of damage does that? In any event, I'm pretty confident the hardware is solid.

Oct 3, 2020 12:13 PM in response to macswe

I believe your suspicion is correct; it's not a Time Machine problem. The root cause of your difficulties seems to be the Mini's startup disk, which is the reason Apple recommend running DU on it as well as its backups. Since that did not result in success it may be unrepairable. Have Apple fix it: Contact Support. Software cannot fix broken hardware.


You appear to be fixated on APFS, which iOS devices have been using for years despite the aid of any so-called "warriors" rushing to their defense.

Oct 3, 2020 2:43 PM in response to John Galt

I have no reason to even suspect anything is wrong with any of my hardware. Startup-D gives a clean bill of health, and there's really no reason for the SSD to be going sour. (And if it happens again, I can just replace it, once I have a recent TM backup).


I am currently using another (working) A2 device to clone my drive from the Mini to an external so I will have something to run File Migration from, then I am going to nuke the internal and reinstall a fresh Mojave.


Yes, you bet I am fixated on APFS. When I get loads of error screens from (useless) DU saying stuff like:


error: Cross Check: External physical extend (xxx + 1) has kind APFS_KIND_UPDATE 
      but was not referenced previously {several of these}
Snapshot is invalid
APFS inverter failed to invert the volume -- invalid argument


...I don't have to run DNA to ID the probable culprit. I repaired and maintained Macs for 35 years without ever having to "invert a volume," whatever the heck that is, and it looks like something I could easily have gone without.


If DU were up to its job, Alsoft wouldn't be in business. But there's a reason they've been profitable for decades.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Time Machine stuck "Preparing backup," out of obvious fixes

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