Announcement: Upgrade to macOS Mojave

With features like Dark Mode, Stacks, and four new built-in apps, macOS Mojave helps you get more out of every click. 
Find out how to upgrade to macOS Mojave >

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


Question: Time Machine fails! (10.13.3)

Why does my Time Machine disk no longer work for backing up? Is this because of the changed file system? Why have I not received any message or warning from Apple that my Time Machine disk will no longer be working? I haven't been able to backup since January!

Now, do I have to buy a new HD in order to format my present HD to APFS? Then what about all my old backups, will they still work after being transfered back again?

Posted on


Page content loaded

Mar 17, 2018 3:16 AM in response to Xine In response to Xine

Whatever the problem it's not the file system. Time Machine does not work with an APFS formatted drive so you don't want to format it as one.

Without more information it's hard to say but it's possible the drive just failed. They do that.

Mar 17, 2018 3:16 AM

Reply Helpful

Mar 17, 2018 3:39 AM in response to Xine In response to Xine

My External HDD is a 1 TB WD My Passport. It has two partitions on 499 GB each. My New MacBook Pro 2016's Internal drive is 1 TB but only 395 GB used and backup has been working flawlessly until upgrading to High Sierra.

Mar 17, 2018 3:39 AM

Reply Helpful

Mar 17, 2018 3:44 AM in response to Xine In response to Xine

As a rule a Time Machine backup drive should be at least 2 to 3 times the size of the drive it's backing up. In your case 2 to 3 TBs. The drive could be full, there could be a different problem.

Did you get an error message?

Mar 17, 2018 3:44 AM

Reply Helpful

Mar 17, 2018 4:02 AM in response to dialabrain In response to dialabrain

361 GB of the TM partition used, 138 GB free.
Ok so I guess I have to get a bigger Ext HDD in any case but as I said it has been working flawlessly until upgrading.

Years ago the advice for a TM Drive was just "larger than the backup disk". Seems really weird that so much extra space is needed. Double the space should be more than enough.

User uploaded file

Mar 17, 2018 4:02 AM

Reply Helpful

Mar 17, 2018 4:11 AM in response to Xine In response to Xine

Did you run Disk Utility on the drive as it suggests?

As far as the size of Time Machine drives, it's an incremental back up system, not just a cloner so, a history of backups are kept as far back in time as the size of the drive allows. Hence the name.

It's also not the best idea to use a drive for both Time Machine and data. If and when the drive fails, you lose everything.

Mar 17, 2018 4:11 AM

Reply Helpful

Mar 17, 2018 4:37 AM in response to Xine In response to Xine

Did you run it on both the disk and the partitions? If so, I suppose since it doesn't matter to you, you could remove then re-add the Time Machine partition and try and start a fresh backup.

Also, if you ever installed any of the WD software remove it.

Mar 17, 2018 4:37 AM

Reply Helpful

Mar 17, 2018 6:18 AM in response to Xine In response to Xine

Years ago the advice for a TM Drive was just "larger than the backup disk". Seems really weird that so much extra space is needed. Double the space should be more than enough.

Strictly speaking twice the total amount (of the aggregate amount of source volume data—not capacity—and calculating the former is not trivial) should be adequate, and the only reason it's not a good idea to partition a drive used for TM backups is that a catastrophic failure could render all its partitions simultaneously lost. Even then, if you designate a drive exclusively for TM's purposes, one and only one backup drive isn't enough anyway.

The most common reason for that message is drive failure. Run DFA on both the source volume and its TM backup. Whatever the problem is, it's not related to the capacity of the TM backup partition. Insufficient space would generate a different error message.

Now, do I have to buy a new HD in order to format my present HD to APFS?

No. As far as Time Machine is concerned just forget anything you may have read or heard about APFS. Questions like that make me wish Apple never said anything about APFS at all. From the user perspective Time Machine works the same way it always has.

For additional troubleshooting suggestions read below.

  • Troubleshooting can be time-consuming but here are some steps that might help identify or correct common problems.
  • Extracting Time Machine log activity may or may not yield useful data, but if you are interested those instructions follow below. It might be just the beginning of troubleshooting efforts that are likely to take some time. Otherwise, you can skip this section and go right to the "reconnect" procedure below it.

To extract potentially relevant Time Machine activity from log consider using the following shell script:

clear; printf '\e[3J' && log show --predicate 'subsystem == ""' --info --last 24h | grep -F 'eMac' | grep -Fv 'etat' | awk -F']' '{print substr($0,1,19), $NF}'

Copy (triple-click to select the entire line) and Paste that line in a Terminal window. The Terminal app is in your Mac's Utilities folder.

It extracts Time Machine activity logged during the previous 24 hours. To change that time period change that value. If Time Machine is running there is no need to interrupt TM to use it. Be advised that log is fairly resource-intensive, and if you are using a portable Mac it will consume a lot of battery power as it runs.

log will need a few moments to extract the Time Machine log data. Wait for it to finish. It is normal for its results to include various "errors" and "failures" and none of them are necessarily an indication of anything wrong.

Copy (Edit > Select All and then Copy) and Paste that Terminal window's contents in a reply to this Discussion. Please omit or obscure any information that you may consider personal.

Quit the Terminal app when you're finished with it.

The following technique can be used to "reconnect" to the backup disk. It will not affect the existing backup history in any way.

Open Time Machine's Preferences and de-select the Back Up Automatically checkbox. Make sure no backups are in progress, otherwise you should wait for it to finish or terminate.

If the backup disk is directly connected to the Mac, disconnect it: drag its icon to the Trash, wait for it to disappear from the Desktop, and then physically disconnect it from the Mac.

If its icon does not appear on the Desktop, select External Disks in the Finder menu > Preferences... > General. You can de-select it later.

Then, click the "Select Disk..." button, select the backup disk, then Remove Disk, then Stop Using This Disk.

If you designated more than one backup destination, the "Select Disk..." button is replaced by an "Add or Remove Backup Disk..." option. You have to scroll through the list of backup disks for that option to become visible.

This will not affect any existing backups.

Reconnect the backup disk to the Mac, power it on if required, and wait for its icon to appear on the Desktop.

Then, Select Disk... again in Time Machine's Preferences. Re-select the same one under Available Disks, then Use Disk. If the backup is on a network (TC or AEBS), you will be prompted for the password you provided for that disk in AirPort Utility.

"Waiting to complete first backup" will appear, which means it won't do anything until the next scheduled backup. Despite the implication of that message, it does not mean it needs to create a completely new backup, as if it's creating a brand new one. Your existing backups will still be available.

If you don't want to wait that long, select Back Up Now.

A Notification may appear if your source volume is encrypted and the backup volume is not. That's normal.

Re-select Back Up Automatically. The "Preparing Backup..." status message will remain for a long time. Eventually, "Backing up xxx of yyy" will appear, but those values will not be accurate, nor will the "Estimated time remaining" in Time Machine's Preferences. Just ignore it. It may take a few hours even if your Mac is not allowed to sleep. Time Machine will also pause or become slow if you use your Mac for tasks it considers a higher priority.

For fundamental troubleshooting references please read If you can't back up or restore your Mac using Time Machine - Apple Support and Time Machine troubleshooting - Apple Support.

Mar 17, 2018 6:18 AM

Reply Helpful

Mar 17, 2018 6:22 AM in response to Xine In response to Xine

So for the proper functioning of a TM Disk but not caring so much about the number of historical backups will it then be ok with a drive that is the same size of the data disk being backed up?

Edit: Ok so John Galt answered this particular question.

Mar 17, 2018 6:22 AM

Reply Helpful

Mar 17, 2018 6:22 AM in response to Xine In response to Xine

Oh and one more thing—if you installed some non-Apple "disk manager" or "utility" such as the junk Western Digital and Seagate are fond of bundling with the drives they sell, uninstall it. Those things convey no benefit and often cause trouble.

Needless to say, if you are using any non-Apple "anti-virus", "cleaning", or "Internet security" junk, anything at all in that broad category of useless garbage, don't do that either. A lot of things won't work if you do..

Mar 17, 2018 6:22 AM

Reply Helpful

Mar 25, 2018 10:51 PM in response to Xine In response to Xine

Having just spent a very long week dealing with severe problems with my computer, I realized that it has likely been related to Time Machine. After much struggle and research on the topic, I'm betting my money on the possibility of a TM bug being introduced recently, maybe as recently as 10.13.3. My TM backups stopped about 10 days after I installed 10.13.3. From reading various support topics, here are my theories in case it helps someone:

  1. It may have to do with using an encrypted backup disk. That is what I was successfully using until a week ago, but many people who report recent problems also note they are backing up to an encrypted TM disk.
  2. It may also have to do with one of your drives getting full or having bad blocks. My primary drive got to 97% full without my realizing it, and (whether related to that or not) I started seeing read errors on that disk. Others have commented on having full drives when they've seen TM problems begin.
  3. Many commented that TM would run for a while, but would fail within the first GB or two. Exactly my situation as well.
  4. While TM runs OK for a few hours, I eventually would start seeing the spinning wheel of death and more and more things became unresponsive, until I had to reboot.
  5. I've purchased two new hard drives in the past week, including the TM drive, but even a brand new TM drive didn't fix the problem. The only way that I can run without crashing is to leave TM turned off.
  6. My plan is to fully reset TM by deleting the TM .plist, but I haven't yet done that to see if that fixes the problem. I haven't seen a posting where someone tried that, but it's the only thing left that I can think of.

My theory at this point is that some combination of an encrypted TM disk, a full drive, and/or a drive that is failing causes TM to be totally hosed under 10.13.3. Just a theory at this point.

Mar 25, 2018 10:51 PM

Reply Helpful
User profile for user: Xine

Question: Time Machine fails! (10.13.3)