Time Machine backups stall

Since updating to Mavericks it's very hard for me to get a complete Time Machine backup. Time Machine is backing up to an AEX moubnted harddrive and I never had any problems before the update. Now most backups will stall and I;ll notice a few days later and stop the backup and restart it. Sometimes this works but it usually takes 3 or 4 tries. Tried repairing permissions on my startup drive but that didn't help. Not sure what to try next.

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

Similar Messages

I have a brand new external hard drive (the Lacie Porsche p9230.) Why do all my attempts to do a time machine backup stall? (usually immediately)

I have a brand new 3T external hard drive (the Lacie Porsche p9230.) I manually backed up several big files from my computer ok, but all attempts to do a time machine backup just stall, usually after only a few K are backed up. hours go by, no progress.
The first time, it did 3 gigs in just a couple minutes, it then got to about 9 gigs, then nothing for 2 hours. all subsequent attempts have done merely a few k, or megabytes, then all just stopped, still appearing as if they are proceeding, but with no results over a long time.
It could indeed be the hard drive on my computer itself, but aside from this the computer functions normally, though slow (it's old, 2009.)
As stated. I WAS able to manually back up a folder exceeding 250 gigs in size, and then another of about 14 gigs.
So, why can I nt do a time machine backup, effectively?

All is not lost yet. Lets take it from the begining. By default, the OS is set to mount and drive plugged in. And for the most part it does work. If you haven't already done so, pop open the external case and make sure all of your cables are well seated.
Next
Plug in the drive.
Fire up Disk Utility
In the window pane on the left-hand side, select the drive (selection with the size information of the drive ie - 232.9GB WDC WD2500. . . .)
Click on volume format and make sure Mac OS Extended (Journaled) is selected
Click on the Erase button
After a couple of minutes is should be done and mounted on the desktop
You can also use Apple System Profiler as a troubleshooting tool. Fire it up and select Firewire from the selections. This will bring up a list of all of the devices it can discover and talk to. If your drive is there and working, it should come up with the drive information such as size, manufactor, etc.

Time Machine Backups Stall out

Hello,
I thought I had this resolved when I replaced the backup drive. Time machine backups of my server stall out. They start seemingly fine, but eventually they will reach a point where the progress bar just stops progressing. I can find nothing in any log to indicate why this may be happening. I replaced the backup drive and backups resumed normally until I noticed today it started stalling again. I have tried resetting time machine by stopping the service in sys prefs, deleting the time machine plist in the root library, and restarting time machine and choosing the drive. This did not resolve the issue. Any ideas?
Thanks for your help.
Nick

Had the same problem that I resolved.
Went to bed with time machine stuck at 49.8% complete, thinking by the time I awake, it would finish.
Awoke to find it still stuck at 49.8%
Noticed the backup drive's light was off, so I figured if I could wake up the drive, it may resume loading.
I awoke the drive by going to the menu, then click view log.
After a few seconds, the backup drive light turned on, and the progress bar started moving again.
In about 4 minutes, it completed its restoration.
Seems we have to figure out these things on our own.
Shame on Apple.

New unibody macbook pro time machine backup stalling/stalls

I have been using time machine to back up my Macbook Pro 17 (First Gen), I have 2 external Western Digital Drives connected via USB in a RAID (Striped) Configuration. Everything has worked fine for months and the backups are quite snappy...
I just changed to a NEW Unibody Macbook Pro 17 and formatted the drives, set up the RAID configuration again from fresh in disk utility and reset Time Machine and said OK when it requested to use the drive for backups.
The process gets some way into backing up... sometimes 7GB, 13GB, 17GB even 70GB and then just stops. The hard drives(at least one of them anyway i cant tell exactly) spin down and the file count in Time Machine window just stops. There is no error message and the window just stays there saying its backing up but there is no external HD activity. I have to cancel the backup (which sometimes - but not always - causes everything to stall until i unplug the drives by whipping the USB cable out). Everything then works fine i dont need to restart and it just brings up an error message saying that Time Machine failed to backup...
Any ideas??
I do have antivirus software installed (VirusScan) but i have had that on my previous machine aswell so it cant be that...

I have a MacBook C2Duo (black 2008) customer who has upgraded to 10.5.7 with a new internal and external hard disk and a fresh install of the OS. After doing this, Time Machine constantly stalled at 12.55 GB when backing up to an external disk (USB2). After a lot of reading on the net, I think the problem marks the re-emergence of an old bug where the mdworker task used by Spotlight to index drives is crashing and starting to take up to 99% of the CPUs. At this point, TM simply does not have enough CPU time to work and crawls almost to a halt.
I messed around for a while with Activity Monitor watching the mdworker crash and it is very predictable. Time Machine buddy does not pick it up because of course TM is still working albeit at a snail's pace.
Since mdworker is very associated with Spotlight, I tried setting Spotlight to not index any folderssame problem.
Finally, I set the TM destination drive to be a Private drive in the Spotlight Preferences and it finished without an mdworker crash.
It might be a temporary workaround or it might be coincidence that TM worked this time, so YMMV and Apple should look at this too.

Time Machine backup stalls in 10.5.5

I noticed yesterday that my Time Machine backup was stalled... and that no new backup had been made since Tuesday, shorty before I installed 10.5.5. I've run Disk Utility on my 1TB Hitachi drive and tried copying to and from it, and it appears to be fine.
I've restarted several times, turned Time Machine on and off, and reselected the drive, and the result is the same every time. Time Machine prepares the backup a while, finds 1.5 Gb of files to back up, and then either stalls or works so slowly that it never comes close to finishing.
Anyone have any ideas what is going on? Is there any way I can narrow down the problem?
Also, is there anyway I can roll back to 10.5.4? That would at least tell me for sure that the problem is 10.5.5.

That's OK. If you take a look at the Console logs Time Machine is reporting that your backups need "deep traversal". That's fine. Time Machine knows what is wrong and how to fix it. Let it do it's thing. If you have alot if data, it may take quite awhile.
After your update to 10.5.5 Time Machine realized the system no longer matched what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is 'untrustable'. So it is going to go item-by-item comparing the before and after of your system. It knows what it's doing - let it do it!
Hope that helps.

Time machine backup stalls

Trying to use Time Machine to back up iMac hard drive. Works fine for first few GBs of files and then "freezes" - i.e. progress stops/stalls and time remaining increases from hours to days until completion

BDAqua,
Thanks for reply. Trying the Disk Utility - Verify right now. Depending on what it tells me, I may be posting again for guidance on what to do next. Appreciate the initial direction, hopefully this gets me on the right path.

Macbook Pro -yosemite install stalls at disc select with ''This disc is used for Time Machine Backups' - help !

Having downloaded Yosemite it installed fine on my iMac but on my Macbook Pro installation has frozen at the Disc Selection stage (where you want it to install) with the message 'This disc is used for Time Machine Backups'.
I cant find a way past this to complete the installation.
Any ideas anyone ?
Many thanks.

Time machine needs its own partition to operate. So you are not going install a OSx Lion on that volume.
If there is enough room you may be able to partition the drive on the fly with DiskUtility
Are you saying you clean installed Lion and you are trying to move your user Data over with TM via the migration Assistant? Please explain.

Unable to recover Mavericks via Time Machine on iMac (2011). I have one Time Machine backup from this week On new Time Capsule. I already attempted safe boot and NPRAM reset. Hard drive and permissions verified as ok.

Some more history - I'm not too techie so added everything in I thought might be significant!
- Installed Mavericks on iMac in October 2013
- experienced regular low memory issues - used Memory Clean app as a workaround
- last week decided to upgrade installed memory from 4gb to 16gb. Faster loading but still running out of memory - just takes longer to do so.
- also last week purchased 2gb Time Capsule (to back up 660gb on 1TB drive)
- one successful Time Machine backup completed last weekend.
- I decided to try and clear some space, tidy my folders, old music files, delete duplicates etc (Not system files)
- then tried out 'time machine restore' just to test it out. Deleted files and folders recovered ok using Time Machine menu (the one that looks like outta space)
- yesterday, Avast Anti-Virus flagged virus detected (sorry, I didn't manage to capture details) and quarantined file, but I couldn't get any windows to respond so forced Mac to shutdown.
- attempted regular reboot , system hanging on white/ apple symbol screen.
- attempted Safe reboot - reboot stalls at mess 'BootCacheControl: unable to open /var/db/BootCache.playlist no such file or directory.
(I don't know if this is significant)
- attempt NPRAM reset, reboot hanging at Apple symbol still
- attempted reboot into Disk Utility. HD drive verified ok. Permissions checked and Safari permissions fixed (only)
- finally attempting restore from Time Machine Backup via Disk Utility. Stalls at 'select a backup source'. Menu is 'searching for Time Machine Backup....'
Nothing is listed, after a few mins machine just goes to sleep.
My Time Capsule and networks are all switched on. No idea what to try next!

Most of the problems like this that people report on this forum are due to bad "utilities" like Memory Clean and Avast.
Your Mac probably didn't have a virus. There has never been an OSX virus "in the wild". Third party antivirus software is of very dubious utility on Macs. Macs are not PCs. OSX has anti-malware protection built into it already.
Do you have any other third party "utilities" on your Mac, such as CleanMyMac or MacKeeper?
Is the RAM you installed the recommended type of RAM for your Mac?
Take a look at this page: Mac OS X: Gray screen appears during startup
But your OS may be damaged beyond repair, or beyond what disk utility is able to repair.
In that case you have a few options:
There is a small chance that a (reputable) third part utility like Techtool Pro 7 may be able to fix your OS.
Try to boot into single user mode (restart, hold down ⌘S until you see a black screen with white text) and repair your hard drive. Here's a reference with directions: Repair Your Hard Disk in Single User Mode | Everything Macintosh
bite the bullet, boot into the recovery partition or internet recovery, and erase your HD, reinstall Mavericks from scratch, and start over. Your documents are probably still on your Time Machine Backup. I wouldn't reinstall the documents via a migration- you don't want to reinstall bad system files along with your documents- but you could copy them one by one back to your internal HD. And most importantly- don't reinstall any third party "utilites" like Memory Clean or Avast (or any other third-party antivirus software, for that matter).

Hard drive issues due to Time Machine backup? Can't source the problem.

Last night my computer began to run extremely slow. All apps simultaneously lagged (spinning wheel of death), but then began working again after about 0.5-1 minute. This whole-system crash repeated about every 10 minutes a total of probably 5-6 times. The last time all apps stopped functioning and (CPU usage of iTunes was 85-95% for some reason (viewed using activity monitor), I am guessing due to its use of multiple hard drives as my music is stored on an external drive) and my computer just shut off after about 3 minutes of completely stalling. Rebooted computer and was left with an EXTREMELY slow system; opening up the quick menu (forgot the name, button on the top row of keyboard) for booting applications took 2-3 minutes. I eventually started disk utility, verified disk. It said I needed to repair disk by restarting my computer while holding down [Command] R message. Made sure i had a backup (at the time of that backup my computer was experiencing the problems above, 11:21pm), so I restarted whilst holding command R. Booted into the OSX utilities, retried the disk repair, received the "Disk Utility cannot repair this drive: back up as many files as you can..." message. Erased/reformatted my internal hard drive, and ran "repair disk" again; disk utility found no problems with the disk. Restored my files to my internal hard drive using OSX utilities (using the full system restore of the 11:21pm backup), and left it running while ran some errands. When I came back to look at my computer, it had attempted startup and crashed with the "kernel error" or whatever where all the text is on the left of the screen. It said something about not being able to find "disk2", which I believe was the disk containing OSX utilities (as veiwed in disk utility while running OSX utilities). Force shutdown, reboot with command R, wiped my internal drive again. Decided to only install a fresh version of OSX in an attempt to scan for viruses (using Sophos Antivirus, running scan as I am typing this), as the slow behavior of my computer had been very strange and began almost instantaneously (seemed like a virus/malware). No threats found so far with Sophos (scanning all my external drives too to source the problem in time machine backups), but I have deduced that there is something wrong with the most current Time machine backup, as it re-established the "problem" (easily fixed once drive is erased using OSX utilities) with my hard drive once I restored it to my internal hard drive. I am wondering (if it is not a virus) if I will need to repeat this whole process with every time machine backup to find where it went wrong, or if i can somehow pinpoint the problem easier. Will all of my Time Machine backups be corrupted now? Why would the Time Machine backup affect the state of the hard drive (does in need to be repaired or not)? Very confused at these random problems. If it is a virus (I will post the results of the Sophos antivirus scan as soon as it is finished), can I remove it from the backup and then restore it with no problems? What do you suggest I do? Will it make a difference to restore the most recent backup (11:21pm) using Migration assistant now that I am running a fresh install of OSX mountain lion? How can I source and eliminate the problem?

Activity Monitor – Monitor Performance Problems
Performance Guide
Why is my computer slow
Why your Mac runs slower than it should
Slow Mac After Mavericks
Things you can do to resolve slowdowns see post by Kappy
Try running this program and then copy and paste the output in a reply. The program was created by Etresoft, a frequent contributor. Please use copy and paste as screen shots can be hard to read.
Etrecheck – System Information

Time Machine backups corrupt or external hard drive failure?

My goal today was to upgrade my MacBook Pro's HD, and to restore my system from my latest Time Machine backup which resides on an external hard drive. I installed the new hard drive, formatted it as Mac OS Extended (Journaled), and selected Restore System From Backup from Utilities. The system restore was five minutes form finishing when I received an error that the system restore could not be completed, and that I should restart my machine and try again. I did as instructed, but once the system restore process began, the screen went gray, and I was told that the Snow Leopard install could not be completed.
Before beginning the process a third time, I ran Disk Utility from the Snow Leopard install disc and attempted to verify and repair the external (Time Machine) hard drive. The Time Machine hard drive could not be verified, nor could it be repaired. I popped in the old hard drive into my MacBook Pro, booted Snow Leopard, and ran Disk Utility, and tried again repairing the Time Machine hard drive. Here is the log of the error I received:
2010-12-29 21:14:30 -0800: Verify and Repair volume “Time Machine”
2010-12-29 21:14:30 -0800: Starting repair tool:
2010-12-29 21:14:31 -0800: Checking Journaled HFS Plus volume.
2010-12-29 21:14:31 -0800: Checking extents overflow file.
2010-12-29 21:14:31 -0800: Checking catalog file.
2010-12-29 21:20:22 -0800: Invalid node structure
2010-12-29 21:20:22 -0800: The volume Time Machine could not be verified completely.
2010-12-29 21:20:22 -0800: Volume repair complete.
2010-12-29 21:20:22 -0800: Updating boot support partitions for the volume as required.
2010-12-29 21:20:22 -0800: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
2010-12-29 21:20:22 -0800:
2010-12-29 21:20:22 -0800: Disk Utility stopped repairing “Time Machine”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
Do these errors indicate that my Time Machine backups located in the Backups.backupdb are corrupt, or is the external hard drive corrupt and failing?
The Time Machine backups are on a Maxtor OneTouch, and from what I've read, they're prone to an early demise. I've also recently noticed that my Time Machine backups started slowing. For example, I would plug in my external hard drive and if 1.3GB needed to be backed up, it would stall at 300 MB before jumping to 700 MB, stall again, then jump to 900 MB. That could be a sign of a failing hard drive, correct? If the external hard drive is failing, I can purchase a new eternal hard drive then copy the Backups.backupdb to the new hard drive, correct?
However, if Backups.backupdb is corrupt, then from what I understand, I would have to start fresh. I would prefer to not start fresh unless there's no other option, as I would be losing almost three years worth of Time Machine backups.
Any guidance is appreciated. Thanks!

ali_baba7 wrote:
2010-12-29 21:20:22 -0800: Invalid node structure
2010-12-29 21:20:22 -0800: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
It's possible a heavy-duty 3rd-party utility such as +Disk Warrior+ can fix that. It's about $100, and there's no guarantee, but it's probably a good investment for the future.
Do these errors indicate that my Time Machine backups located in the Backups.backupdb are corrupt, or is the external hard drive corrupt and failing?
The structure of the file system is damaged.
That may have been caused by the disk beginning to fail, but there's no way to tell for sure until you erase and reformat the disk and try to use it.
I've also recently noticed that my Time Machine backups started slowing. For example, I would plug in my external hard drive and if 1.3GB needed to be backed up, it would stall at 300 MB before jumping to 700 MB, stall again, then jump to 900 MB. That could be a sign of a failing hard drive, correct?
It could, but it could also be whatever's wrong with the file structure.
If the external hard drive is failing, I can purchase a new eternal hard drive then copy the Backups.backupdb to the new hard drive, correct?
No. You can't copy corrupted backups. They're all linked together, like a database, so if anything's damaged, the whole set is suspect, and can't be copied.
There are a couple of options:
If the disk is physically ok, and the directory damage was recent, you might be able to restore from an earlier backup. But since you noticed problems some time ago, the damage may not be recent.
Or, you might be able to get up and running by just installing OSX from your SL Install disk (and the 10.6.5 "combo" update). You'll be missing whatever wasn't restored in that last 5 minutes or so. Things are restored in the same order they're listed by the Finder, so it will be the last things in the last user account. You should be able to figure out where it stopped, check or delete the very last file (likely incomplete) and selectively restore as many of the remaining things as you can, via the "Star Wars" display.
Just to make things more difficult, if the disk is failing, the more you use it, the more likely it is to get worse or fail completely.
So your safest bet may be to install OSX, then download and install the 10.6.5 "combo" update. Info and download available at: http://support.apple.com/kb/DL1324 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards. Then recover what you can.

Restoring time machine backup stuck at end

Hello!
I recently suffered a random filesystem failure and had to reinstall the OS. I was running 10.7, in fact, I turned on my MBP to install 10.7.1.
After a lengthy download, the installer prompted me to restore from a Time Machine backup, which I'm keeping since my last hardware HD failure. I chose to restore, and the installer detected my Time Capsule, loaded the backup, and started restoring.
I left it overnight and, come the following morning, the restore hadn't finished yet. Again, I left it while I was at work, and came back 8 hours later to find the screen in the exact same way I left it in the morning.
After some tests trying to restore the backup (including a failed back-to-Snow Leopard attempted recovery, couldn't connect to my TC), I figured I would reinstall Lion from scratch and use Console.app to check the progress using the system log when restoring using Migration Assistant.
My first surprise was when I tried to run Migration Assistant using the root user, which made Migration Assistant crash, so I had to create a second administrator user in order to restore my original administrator account.
After leaving it run its course, I started noticing that the Migration Assistant was trying to restart opendirectoryd, and that it was failing to start, citing error 71 "profile could not be found" (or opened, instead of found, I really don't remember and don't have the log here with me).
I then went into the terminal to check if the restored data was on disk, which it was, so, after a couple of attempts of launchd to restart opendirectoryd, I pulled the plug and shut the machine down cold (no shutdown process, just held the power button).
When the computer started up again (I have verbose boot mode on), it stalled at macx_swapon (again, or something like that, I don't remember), and didn't move in the whole hour and a half I let it sit there.
I tried booting single user mode, but the only thing I got to do was check if the restored data was there (which it was), and try to create my user (which I couldn't).
I've had success restoring backups from that Time Capsule but for another Mac.
Is there any way I can restore my computer back to the exact state of the Time Machine backup? FWIW, the TM backup is a data-only backup (i.e. doesn't have the OS with it), so a disk clone is not an option.
I really would like to avoid going the "fake manual restore" option of creating the same user, moving the files manually and so on, it's a PITA
Thanks in advance,
Nico

Sorry, can'thelp. But:
I trust TM only for rescuing individual files. I tried a full restoration of my Lion system, as a test, and everything was restored and seemed OK except half my Mail messages were missing. A few months ago, on OS 10.5.8, TM suddenly told me that it had deleted some files. The files deleted were all from Jan. 2010 to four weeks before! I know that it does this if the TM disc is getting full, but I had not created any large files in the preceding few hours. Also, the TM disc had loads of space left, yet when the message came, TM's GetInfo showed the disc nearly full!. I had to erase the disc and start again.
I don't find TM reliable. I make my backups in the form of bootable clones, scheduled every day in Carbon Copy Cloner.

System "hiccup" during Time Machine Backups

Over the course of the past week or so, I've noiticed that my system will freeze/stall/hiccup (whatever you call it) during Time Machine backups. This will apply to YouTube/Vimeo videos, iTunes (where I noticed it... it's like the song pauses and resumes 2 or 3 times over 10 seconds), task switching, text entry, etc. Again, this is only a recent thing.
Here's a log of what I was doing during this last backup. Didn't check the time when iTunes froze, but it happened at least twice, maybe 3 times.
3/5/13 4:50:35.477 PM com.apple.backupd[48152]: Starting automatic backup
3/5/13 4:50:36.010 PM com.apple.backupd[48152]: Backing up to: /Volumes/Hydra 1/Backups.backupdb
3/5/13 4:50:55.980 PM com.apple.backupd[48152]: Using file event preflight for Mac HD
3/5/13 4:51:18.189 PM com.apple.backupd[48152]: Will copy (2.07 GB) from Mac HD
3/5/13 4:51:19.601 PM com.apple.backupd[48152]: Found 105304 files (2.55 GB) needing backup
3/5/13 4:51:19.638 PM com.apple.backupd[48152]: 4.58 GB required (including padding), 153.96 GB available
3/5/13 4:51:53.825 PM locationd[48163]: NOTICE,Location icon should now be in state 0
3/5/13 4:52:01.241 PM lsboxd[245]: @AE relay 4755524c:4755524c
3/5/13 4:53:40.070 PM mdworker[48192]: Unable to talk to lsboxd
3/5/13 4:53:40.075 PM mdworker[48191]: Unable to talk to lsboxd
3/5/13 4:53:40.219 PM sandboxd[48194]: ([48192]) mdworker(48192) deny mach-lookup com.apple.ls.boxd
3/5/13 4:53:40.226 PM sandboxd[48194]: ([48191]) mdworker(48191) deny mach-lookup com.apple.ls.boxd
3/5/13 4:53:40.000 PM kernel[0]: Sandbox: sandboxd(48194) deny mach-lookup com.apple.coresymbolicationd
3/5/13 4:53:58.561 PM Messages[26674]: [Warning] Updating typing guid on IMMessage from 3FEF0FB8-9FEC-4C4F-93B9-ABA280016F8A to AB036A47-4BE4-4DD7-879D-1ED11CF1F0E0
3/5/13 4:54:08.903 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:54:08.905 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:54:11.000 PM kernel[0]: disk0s2: I/O error.
3/5/13 4:54:27.000 PM kernel[0]: disk0s2: I/O error.
3/5/13 4:54:27.526 PM com.apple.backupd[48152]: Error: (-36) SrcErr:YES Copying /Users/niclake/.dropbox/sigstore.dbx to (null)
3/5/13 4:54:52.106 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:54:52.108 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:55:24.726 PM coreservicesd[65]: Application App:"Sublime Text 2" [ 0x0/0x13ea3e9] @ 0x0x7ffb51e75860 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x14d24d1:) ), so denying.
3/5/13 4:55:24.726 PM WindowServer[93]: [cps/setfront] Failed setting the front application to Sublime Text 2, psn 0x0-0x13ea3e9, securitySessionID=0x186a3, err=-13066
3/5/13 4:55:24.765 PM authexec[48213]: executing /bin/cp
3/5/13 4:55:35.752 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_NOTRESP (1)
3/5/13 4:55:35.752 PM KernelEventAgent[45]: tid 00000000 type 'afpfs', mounted on '/Volumes/Chimera', from '//Nic%20Lake@Nic%60s%20AirPort%20Extreme._afpovertcp._tcp.local/Chimera', not responding
3/5/13 4:55:35.000 PM kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 575 on so 0xffffff8026cb6260
3/5/13 4:55:35.000 PM kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Chimera prevTrigger 575 currTrigger 576
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Chimera
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/Chimera
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Chimera
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Chimera
3/5/13 4:55:35.752 PM KernelEventAgent[45]: tid 00000000 found 1 filesystem(s) with problem(s)
3/5/13 4:55:35.869 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_NOTRESP (1)
3/5/13 4:55:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 13 /Volumes/Chimera
3/5/13 4:55:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Chimera
3/5/13 4:55:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: get the reconnect token
3/5/13 4:55:45.111 PM mdworker[48217]: Unable to talk to lsboxd
3/5/13 4:55:45.119 PM mdworker[48218]: Unable to talk to lsboxd
3/5/13 4:55:45.339 PM sandboxd[48215]: ([48217]) mdworker(48217) deny mach-lookup com.apple.ls.boxd
3/5/13 4:55:45.348 PM sandboxd[48215]: ([48218]) mdworker(48218) deny mach-lookup com.apple.ls.boxd
3/5/13 4:55:45.000 PM kernel[0]: Sandbox: sandboxd(48215) deny mach-lookup com.apple.coresymbolicationd
3/5/13 4:56:15.453 PM Messages[26674]: [Warning] Updating typing guid on IMMessage from 87A43B63-A4B2-4E41-B472-34083741613A to BA8D492D-6BDB-4B9B-9A44-50D21FCFAC7E
3/5/13 4:56:24.430 PM Messages[26674]: [Warning] Updating typing guid on IMMessage from 86F1F958-B235-4C5B-BCEE-537E0826534D to 2A54A84E-C80B-43F6-A31B-0148CB5367B0
3/5/13 4:56:31.437 PM lsboxd[245]: @AE relay 4755524c:4755524c
3/5/13 4:56:35.096 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:56:35.098 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:56:37.574 PM Messages[26674]: [Warning] Updating typing guid on IMMessage from A0CF4108-C32F-4E4C-B1FB-5745F2EFA376 to B890B725-4D5B-4338-9574-42E1BC800D26
3/5/13 4:56:53.912 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:56:53.914 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:57:09.327 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:57:09.331 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:57:48.285 PM mdworker[48246]: Unable to talk to lsboxd
3/5/13 4:57:48.291 PM mdworker[48247]: Unable to talk to lsboxd
3/5/13 4:57:48.388 PM sandboxd[48243]: ([48246]) mdworker(48246) deny mach-lookup com.apple.ls.boxd
3/5/13 4:57:48.423 PM sandboxd[48243]: ([48247]) mdworker(48247) deny mach-lookup com.apple.ls.boxd
3/5/13 4:57:48.000 PM kernel[0]: Sandbox: sandboxd(48243) deny mach-lookup com.apple.coresymbolicationd
3/5/13 4:58:13.430 PM Tweetbot[22562]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
3/5/13 4:58:25.538 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:58:25.540 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:58:30.819 PM iTunes[1027]: ImageIO: JPEG Corrupt JPEG data: premature end of data segment
3/5/13 4:58:30.829 PM Bowtie Butler[1030]: ImageIO: JPEG Corrupt JPEG data: premature end of data segment
3/5/13 4:59:52.515 PM com.apple.backupd[48152]: Copied 118801 files (2.47 GB) from volume Mac HD.
3/5/13 4:59:52.707 PM com.apple.backupd[48152]: Using file event preflight for Mac HD
3/5/13 4:59:53.910 PM com.apple.backupd[48152]: Will copy (3.4 MB) from Mac HD
3/5/13 4:59:53.913 PM com.apple.backupd[48152]: Found 120 files (3.4 MB) needing backup
3/5/13 4:59:53.914 PM com.apple.backupd[48152]: 1.84 GB required (including padding), 150.66 GB available
3/5/13 5:00:16.000 PM kernel[0]: disk0s2: I/O error.
3/5/13 5:00:16.222 PM com.apple.backupd[48152]: Error: (-36) SrcErr:YES Copying /Users/niclake/.dropbox/sigstore.dbx to (null)
3/5/13 5:00:35.593 PM com.apple.backupd[48152]: Copied 1349 files (53 MB) from volume Mac HD.
3/5/13 5:00:36.426 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_NOTRESP (1)
3/5/13 5:00:36.426 PM KernelEventAgent[45]: tid 00000000 type 'afpfs', mounted on '/Volumes/Chimera', from '//Nic%20Lake@Nic%60s%20AirPort%20Extreme._afpovertcp._tcp.local/Chimera', not responding
3/5/13 5:00:36.000 PM kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 576 on so 0xffffff8026cb6260
3/5/13 5:00:36.000 PM kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Chimera prevTrigger 576 currTrigger 577
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Chimera
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/Chimera
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Chimera
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Chimera
3/5/13 5:00:36.427 PM KernelEventAgent[45]: tid 00000000 found 1 filesystem(s) with problem(s)
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 13 /Volumes/Chimera
3/5/13 5:00:36.543 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_NOTRESP (1)
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Chimera
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: get the reconnect token
3/5/13 5:00:37.029 PM com.apple.backupd[48152]: Created new backup: 2013-03-05-170036
3/5/13 5:00:41.100 PM com.apple.backupd[48152]: Starting post-backup thinning
3/5/13 5:00:41.100 PM com.apple.backupd[48152]: No post-back up thinning needed: no expired backups exist
3/5/13 5:00:41.218 PM com.apple.backupd[48152]: Backup completed successfully.

The boot drive is failing, or you have some other hardware fault.
Back up all data immediately, then make a "Genius" appointment at an Apple Store to have the machine tested.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to bare metal from any of them.) Don’t erase the recovery partition, if present.
*An SSD doesn't need to be zeroed.

Isight causes Time Machine to stall

Hi everyone,
I've been struggling since getting Leopard to get Time Machine running. It has run intermittently for me, but usually just starts backing up and stalling after a period of time. I seem to have found a fix I thought I would post for other people struggling with this problem--if you have an old, external isight camera, disconnect it! It doesn't matter if it's actually "on" or not.
I realized that I used to have a similar problem with Carbon Copy Cloner, and taking the isight off fixed it in that instance, as well. I should point out that this problem has occurred across two different iMacs, so it's not likely a weird fluke. Something about the camera interferes with the backup process.
Cheers!
Tony

Good info, Tony!
If you are using a Firewire hard drive as your Time Machine backup device, my guess is that you are experiencing a Firewire conflict with your external iSight.
I am using one of my internal drives on my tower Mac for my Time Machine backups, and I do NOT share your problem while my external iSight is connected. Time Machine backups do pause while my iSight is active, but backups proceed normally with my iSight connected and on, even when iChat is open and connected to my iSight.
External (Firewire) iSight users who must use external drives for Time Machine backup might want to choose a USB drive as their backup device if they do not want to turn Time Machine backups off while their iSights are connected. Doing so would likely eliminate problem you experience.
Cheers,
EZ Jim
PowerBook 1.67 GHz w/Mac OS X (10.4.11) G5 DP 1.8 w/Mac OS X (10.5.1) External iSight

Time Machine backup hangs in Lion 10.7.4

My mother just purchased a new 2012 mbp after her 2008 mpb motherboard crapped out. I restored her data from a time machine backup she had on a 500 GB WD external HD (My Passport). I then attempted to setup Time Machine backups for her new computer using the same external HD. During the large initial backup (around 120 GB), Time Machine seems to freeze up. I tried repairing and reformatting the external HD (Mac OS Journaled) but the problem remains. For the past hour Time Machine has been stuck at 3.05 GB of 120.26 GB with 645,018 items to go. It was cranking along at 1 GB/min but seemed to stall after around 3 minutes. It is either stuck or the transfer speed took a huge a nose dive.
Any suggestions?

Sounds like your external may have issues. I'd try a different external drive. -Alan

Restore from Time Machine Backup fails half-way through...

I'm trying to fix my mom's 2.4GHz Core 2 Duo 24" Aluminum iMac (w/ 2GB of RAM). It was stuck on the white screen with the Apple logo and a spinning wheel. I tried a few things to get it to boot up but nothing worked, so I booted up using my OX 10.5 Leopard disk (the retail box version) and tried to repair the disk using Disk Utility. Disk Utility couldn't un-mount the disk so I decided to erase the disk and start from scratch.
So I erased the disk and formatted in OS Extended (Journaled). Then I ran the repair disk function and the disk checks out OK. So, here is my problem:
When I tried to restore from a Time Machine backup, everything worked normally until it got about 20% through the restore process. At that point it froze for a while and then gave me an error message that the restore failed and asked if I would like to restart?
I've tried this a few times, all with approximately the same result (it either freezes or gives me the error/restart message).
What's wrong with my mom's computer?

c.d.stone wrote:
The restore process is just spinning it's wheels and the log says "erasing" drive name.
Is the drive name your internal?
UPDATE: When I stopped the restore function I checked the error log again and it said "could not un-mount disk for erasure" Not sure what that means. Anyone know how to fix that?
I'm pretty sure something is wrong with the hard drive installed on the iMac at this point. I tried to do a clean install of 10.5.0 from the Leopard retail DVD and that stalled early in the process as well.
Yes, it sure sounds like it. It now sounds like both the TM restore and Erase and Install are unable to erase your internal HD. It's not even getting to your TM backups, or installing OSX.
Let's double-check and try again. Boot from the Install disc again, and completely reformat the internal HD. Be sure to use the GUID Partition Map scheme if it's an Intel Mac, or the +Apple Partition Map+ scheme if it's a PPC. And use the +Mac OS Extended (Journaled)+ format.
It might be worth taking the time to then do a +Zero Out.+ Select Erase, then +Security Options,+ then +Zero Out Disk+ (the one-pass option is sufficient). That will, obviously, write zeros to the entire disk. If this fails, the disk is dying and likely the cause of the whole mess. If it passes, it isn't necessarily ok, but it's a pretty good sign, and you may be able to proceed with the restore.

Time Machine backups stall

Similar Messages

Maybe you are looking for