Recurrently stuck time machine backup

[ragnu]

Hello. With Yosemite, my time machine backups onto a WD usb external HD get stuck. Each time, I resolve the problem either by trashing the inprogress file on my external drive or, more easily, by trashing the .plist file, then restarting. Everything goes smoothly for a day or two, then the problem reoccurs. I'm running 10.10.3 beta, but had the problem in past versions of Yosemite as well. Any ideas? thanks

 

[Julien]

This could be your HD staring to fail.

 

[ragnu]

Except that it's pretty new, and the problem never occurred before Yosemite.

 

[Partron22]

You have other backup software? SuperDuper! or Carbon Copy Cloner?
If not, consider getting some, using it, and verifying integrity of BU.
Even when it works, Time Machine is not a complete backup solution.

 

[ragnu]

Yes, I have been using SuperDuper for years, along with Time Machine. They do very different things, and I'd like to continue using both of them. The thing is that I didn't have this problem with TM before Yosemite, so I'm wondering if there isn't a bug, or, at any rate, if anyone has a solution to suggest.

Thanks

 

[Partron22]

I'm in exactly same boat as you; SuperDuper + TimeMachine that went bad w the update to Yosemite. After much fighting w it, I'm waiting for ~10.10.4 or so before I give it another shot.

 

[ragnu]

Well, SuperDuper is working fine; it's just Time Machine that gets stuck very often.

 

[Partron22]

Well, SuperDuper is working fine; it's just Time Machine that gets stuck very often.

Exactly.

 

[Taz Mangus]

Well, SuperDuper is working fine; it's just Time Machine that gets stuck very often.

Hold down the OPTION key and select the Time Machine backup icon in the menu bar and then select "Verify Backups" if it is not greyyed out. See if this helps.

 

[ragnu]

It's greyed out. My backup volume is usb; "verify backups" only works with NAS. I did run a "verify disk" from disk utility on it, and it said everything was OK.

 

[Taz Mangus]

It's greyed out. My backup volume is usb; "verify backups" only works with NAS. I did run a "verify disk" from disk utility on it, and it said everything was OK.

While Time Machine is running and gets stuck, open the console app and enter "backupd" in the search. Report back with what is displayed.

 

[ragnu]

Will do, next time it happens. Thanks.

 

[ragnu]

It happened again. Here is what Console says:

17/03/2015 11:16:20,447 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 11:16:50,576 com.apple.backupd-helper[593]: Not starting scheduled Time Machine backup: No destinations resolvable
17/03/2015 11:43:21,101 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 12:06:56,164 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 12:17:07,425 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 12:17:37,514 com.apple.backupd-helper[593]: Not starting scheduled Time Machine backup: No destinations resolvable
17/03/2015 12:38:20,112 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 13:57:34,483 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 14:29:07,226 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 14:52:05,287 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 15:30:51,524 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 15:59:53,117 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 16:09:31,259 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 16:24:57,085 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 16:30:58,065 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 16:31:28,161 com.apple.backupd-helper[593]: Not starting scheduled Time Machine backup: No destinations resolvable
17/03/2015 16:59:24,609 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 17:52:56,203 com.apple.backupd-helper[593]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
17/03/2015 17:52:59,469 com.apple.backupd[1584]: Starting automatic backup
17/03/2015 17:53:10,006 com.apple.backupd[1584]: Backing up to /dev/disk1s2: /Volumes/TM/Backups.backupdb
17/03/2015 17:53:10,000 kernel[0]: memorystatus_thread: idle exiting pid 593 [backupd-helper]
17/03/2015 17:53:39,000 kernel[0]: memorystatus_thread: idle exiting pid 1592 [backupd-helper]
17/03/2015 17:53:55,000 kernel[0]: memorystatus_thread: idle exiting pid 1602 [backupd-helper]
17/03/2015 18:02:55,350 com.apple.backupd[1584]: Will copy (4.3 Go) from Macintosh HD
17/03/2015 18:02:55,648 com.apple.backupd[1584]: Found 74260 files (4.62 Go) needing backup
17/03/2015 18:02:56,220 com.apple.backupd[1584]: 7.61 Go required (including padding), 218.59 Go available
17/03/2015 18:52:39,415 com.apple.backupd-helper[1609]: Not starting scheduled Time Machine backup: Backup already running
17/03/2015 19:52:48,974 com.apple.backupd-helper[1609]: Not starting scheduled Time Machine backup: Backup already running
17/03/2015 20:53:08,589 com.apple.backupd-helper[1609]: Not starting scheduled Time Machine backup: Backup already running
17/03/2015 21:53:11,999 com.apple.backupd-helper[1609]: Not starting scheduled Time Machine backup: Backup already running
17/03/2015 22:53:30,266 com.apple.backupd-helper[1609]: Not starting scheduled Time Machine backup: Backup already running
17/03/2015 23:53:31,468 com.apple.backupd-helper[1609]: Not starting scheduled Time Machine backup: Backup already running

 

[Taz Mangus]

It happened again. Here is what Console says:

17/03/2015 17:52:59,469 com.apple.backupd[1584]: Starting automatic backup
17/03/2015 17:53:10,006 com.apple.backupd[1584]: Backing up to /dev/disk1s2: /Volumes/TM/Backups.backupdb
17/03/2015 17:53:10,000 kernel[0]: memorystatus_thread: idle exiting pid 593 [backupd-helper]
17/03/2015 17:53:39,000 kernel[0]: memorystatus_thread: idle exiting pid 1592 [backupd-helper]
17/03/2015 17:53:55,000 kernel[0]: memorystatus_thread: idle exiting pid 1602 [backupd-helper]
17/03/2015 18:02:55,350 com.apple.backupd[1584]: Will copy (4.3 Go) from Macintosh HD
17/03/2015 18:02:55,648 com.apple.backupd[1584]: Found 74260 files (4.62 Go) needing backup
17/03/2015 18:02:56,220 com.apple.backupd[1584]: 7.61 Go required (including padding), 218.59 Go available

Open the terminal application and enter "tmutil status". Do that several times. You should see "NumberOfChangedItems" with a number that changes. If you see a number that changes then it could be that the backup is fine. Let it go and see how long it takes to finish backing up. The log you posted does show it needing to backup 74260 files.

Have you ever let the Time Machine backup finish when it starts taking what seems forever to finish? If so, how long did it take?

EDIT: I just noticed something that looks odd. In the log you posted it shows 7.61 Go required (including padding), 218.59 Go available. It is showing Go instead of GB. I just looked at my console log and when I look at the backupd entries I see GB not Go.

Try this and see if it fixes the problem. Stop the Time Machine backup, repair permissions and reboot. Also, while rebooting hold down CMD-OPTION-P-R until you hear 2 bong sounds (the computer should reboot twice; don't release CMD-OPTION-P-R until the computer reboots a second and you hear the second bong which will be a full volume bong sound). Log back in and start a manual Time Machine backup with "Backup Now". Is it working better?

 

[ragnu]

Thanks Taz for that rundown.
My system language is set to French, and Go is French for GB, though everything else in the Console's output is in English. Kind of odd.
Whenever it gets stuck, it stays stuck an awful long time. This last time, it was stuck all night, and I stopped the backup in the morning. Other times, there was a lot less to back up, and it still stayed stuck for hours and hours. Anyway, next time I'll try your Terminal trick to see what, if anything, is going on.
I've also repaired permissions and reset PRAM (because of wifi issues) a couple of times since the problem began occurring.
It doesn't get stuck every time, but when it does, I have to delete the .plist and restart to get it going again.

 

[Taz Mangus]

Thanks Taz for that rundown.
My system language is set to French, and Go is French for GB, though everything else in the Console's output is in English. Kind of odd.
Whenever it gets stuck, it stays stuck an awful long time. This last time, it was stuck all night, and I stopped the backup in the morning. Other times, there was a lot less to back up, and it still stayed stuck for hours and hours. Anyway, next time I'll try your Terminal trick to see what, if anything, is going on.
I've also repaired permissions and reset PRAM (because of wifi issues) a couple of times since the problem began occurring.
It doesn't get stuck every time, but when it does, I have to delete the .plist and restart to get it going again.

I was thinking more about this and I have a few more suggestions to try:

• In Disk Utility, try "Repair Disk" on your Time Machine backup hard drive.
• In Disk Utility, try "Repair Disk" on your internal hard drive.

The above steps are to make sure that there is not some issue with the hard drives. If "Repair Disk" did find something then see if Time Machine backup gets stuck.

Another thing to try:

• Split the backup hard drive into 2 partitions in Disk Utility.
• The new partition will mount as what looks like a another hard drive.
• Open Time Machine preferences and add the new mounted partition as a backup hard drive, select use both hard drives. Time Machine will now show both partitions as backup volumes.
• Unmount the your original backup partition.
• Turn off automatic Time Machine Backups.
• Start a manual backup.

I am curious if Time Machine will still get stuck. When you are done with this test, delete the new partition backup in Time Machine preferences, and delete the partition in Disk Utility. Me sure to resize the partition back to the full size of the hard disk. Turn back on automatic Time Machine backups.

 

[ragnu]

Thanks again Taz!
I've already run Verify Disk on both volumes, and no problems were detected. Anyway, it just got stuck again, so I'm creating a new partition and will try your idea. The thing is, it doesn't get stuck every time, so I may well end up with a new complete backup on the new partition. I can just keep backing up to it for a few days and see if it eventually gets stuck and, if not, erase the first partition. (I'm not too concerned over losing old backups.) I'll let you know.

 

[Taz Mangus]

Thanks again Taz!
I've already run Verify Disk on both volumes, and no problems were detected. Anyway, it just got stuck again, so I'm creating a new partition and will try your idea. The thing is, it doesn't get stuck every time, so I may well end up with a new complete backup on the new partition. I can just keep backing up to it for a few days and see if it eventually gets stuck and, if not, erase the first partition. (I'm not too concerned over losing old backups.) I'll let you know.

I would not suggest you erase the first partition and keep the second as you won't be able to resize the second partition to the size of the whole hard drive. In order for a partition to use all of the hard disk the partition must begin at the first sector on the hard disk. A second partition will begin somewhere lower and can't be moved to the first sector of the hard drive. My suggestion was just a test but if you are not concerned about loosing your old backups then I suggest you start over with your backup.

By the way, it is a good idea to have more then one backup where each is on its own device stored in different locations. I run 2 backups, one is the normal Time Machine backup that runs every hour and attached to my Mac. The second is on a different hard drive that I plug into the computer, via USB, every 3 days or so and run manually. I learned the hard way to do this when my backup hard drive had a hardware failure and needed to be replaced. I lost all the backups that were stored in that hard drive that failed.

If you do decide to use more then 1 backup hard drive, when you set it up, make it the first one listed in the Time Machine preferences. What I found is that Time Machine backups in the order that the devices are listed in the preferences. When I plug the second hard drive in because it is listed first the backup will go to it first. If you make the secondary backup hard drive last in the list, when you do a manual backup Time Machine will use the first device listed. Since I don't leave the second hard drive plugged in all the time, I want to make sure that the backup starts on that hard drive when I plugged it in.

The way you would change the order of the Time Machine hard drives is first delete the current hard drive from the Time Machine preferences and then start adding back in the secondary backup hard drive first, followed by the primary backup hard drive. Nothing will be lost on the backup hard drive that you deleted it from the preferences. The information about the backup history will get refreshed in the Time Machine preferences window when it starts backing up again.

Hope this helps. Sorry you are having so much trouble running Time Machine. I know I would certainly be frustrated if Time Machine were getting stuck.

 

[ragnu]

Thanks. By the way, running TM on the backup volume I created this morning, it got stuck almost immediately at 948,8 MB out of 93,04 GB, and has been there for about 3 1/2 hours. So I'm giving up, erasing that second partition, and going back to the first one. When it gets stuck, I'll just delete the .plist as before. Maybe a future OS update will solve the problem; as I said, it only began recently.