Macbook Air Freezes when Time Machine backup starts

My Macbook Air (OS 10.5.5) has started freezing up whenever a Time Machine backup begins. I get the dark shade screen telling me that it has crashed and to hard power off. Everything was working well before, including the Time Machine backups, and the only changes I have made are the Apple updates. At first I thought it was random crashes, but I soon discovered that turning off Time Machine stops the problem (though obviously does not fix it). I've tried restarting and turning Time Machine back on, but it still makes the computer crash within a minute of the start of the backup process. The backup goes to a Time Capsule. I have not seen this problem on any of my other macs on the same network including a Macbook Pro that backs up to the same Time Capsule. Does anyone have any idea what the problem could be and how to fix it?

To be honest,no I don't know why you are having this problem.
It looks like a specific problem with your MBA which could be a hardware problem (RAM most likely here) or a bad sector problem on the hard disk. If you own a copy of TechTool or something similar, run a full hardware systems check. If you don't own TechTool, run the Apple Hardware check from the MBA System install disk.
And, it could be a software problem. I don't know if this sequence will help, but do it anyway because it seems to solve problems on other Leopard systems.
1.) Disable Time Machine back ups
2.) Open Disk Utility and Run Repair Permissions
3.) Run Verify Disk. If it passes go to step 4.
4.) Download the 10.5.5. Combo Updater from http://support.apple.com/downloads/MacOS_X_10_5_5_ComboUpdate
5.) Run the Combo Updater and restart
6.) Run Disk Utility Repair Permissions again
Then enable Time Machine and keep your fingers crossed.
Let me know if any of that helps.

Similar Messages

New Macbook Air transferred by Time Machine Backup USB--fan/temps

Hello,
I just got the last version of the macbook air, with 120HDD and 1.86 cpu. I thought that I would have to try to transfer everything from my Imac 27" through wifi transfer but when I started up the macbook air it asked if I had a time machine backup I would like to use through USB (which I have used many times before to basically transfer all my data, applications, and settings.) It took a while and the macbook air's fans kicked in during the transfer, which is from the Imac with snow leopard. total transfer was around 45gb. I thought this type of transfer wasn't possible. I also did a long software update after the transfer.
MY QUESTION: could any of this account for the macbook air running hot now, fan at about 6200rpm. I am in Paris and it is very hot here now, so maybe this accounts for it. I'll see in the morning. I am just wondering if the machine will run hot now because perhaps because of the type of transfer I executed, which might have included programs or apps not directly related to the macbook air itself. Again, we are in a heat wave here so perhaps this contributes to it. Don't these machines run rather quietly?
any advice would be appreciated. I could always start again, do a reinstall, etc. but except for the fans running, I have everything I need on the machine and would really prefer not buying the external dvd ir starting over again.
Thanks

I learned that the macbook air shipped with Leopard, but after migrating everything over from my Imac 27" with Snow Leopard, my system now on the Macbook Air is exactly what I have on the Imac. After the initial backup from Time Machine I did a software update, which brought the system up to 10.6.4. I suppose on some level part of one system did transfer over to the Macbook Air, or at least it updated the system that was shipped on the Air. I did call Apple and was told that if there were issues during the Time Machine backup the system would have alerted or panics would have occurred. The guy wasn't 100% sure, but felt that the backup went normally.
The Air seems to work fine, but the fans kick up from the base of 2500rpm when I watch a video or download video files for a few minutes as an experiment. I don't want to do a complete re-install with the original DVD discs, with all of the trouble that implies, if the machine is going to run rather hot with fans increasing in any case. I suppose that's why I am looking for confirmation one way or another.
It was suggested that I log out and open another account empty of data and see if that makes a difference.
If the machine will run cooler with a re-install, no problem. But it sounds as if all of that could be for naught.
Any other comments would be appreciated.

System crashing when Time Machine backup starts

My MacBook Pro has crashed 4 times today. The first 2 times I wasn't around to see the crash, I just saw the message that the system had crashed and that I needed to hold down the power button and restart.
The 3rd time it happened I noticed that the Time Machine backup process had just started before the crash. I restarted the computer, manually started a Time Machine backup, and it crashed again.
It seems that the crashes are happening when Time Machine tries to backup to my Time Capsule.
Anyone have any ideas for me to try to get it working correctly, or any ideas on what exactly might be causing it? Maybe a problem with my Time Capsule? I noticed on my wife's MacBook that her Time Machine backup had failed today too. Her MacBook has not had any system crashes though.

Hi Garner,
Yes, you'll erase it with Disk Utility (make sure that you don't have any other information on the drive that you don't want to lose!).
So when you try backing up the other machine manually, does it work? If your other backup is actually working, you might want to try just erasing the old backups for the one machine that won't work and see if that helps (to avoid backing up both all over again). Just because my experience was that we had to format the drive doesn't mean that you'll necessarily have to.
And yes, if you don't ever mount the drive outside of Time Machine, that should be OK.
Hope that helps! Enjoy the long, boring backup process (sorry about that...).
—Hazy

I restored a Macbook Pro from a Time Machine backup and now none of my passwords are working (and I know they are the correct passwords). What can I do?

I restored a Macbook Pro from a Time Machine backup and now none of my passwords are working (and I know they are the correct passwords). What can I do?

First, make sure caps lock is not on.
Another reason why the password might not be recognized is that the keyboard layout (input source) has been switched without your realizing it. You can select one of the available layouts by choosing from the flag menu in the upper right corner, if it's showing, or cycle through them by pressing the key combination command-space or command-option-space. See also this support article.
If the user account is associated with an Apple ID, and you know the Apple ID password, then maybe the Apple ID can be used to reset your user account password. In OS X 10.10 and later, this option also works with FileVault, but only if you enabled it when you activated FileVault. It's not retroactive. Otherwise, see below.
Note: If you've activated FileVault, this procedure doesn't apply. Follow instead these instructions.
Start up in Recovery mode. When the OS X Utilities window appears, select
Utilities ▹ Terminal
from the menu bar at the top of the screen—not from any of the items in the OS X Utilities window.
In the window that opens, type this:
resetp
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window opens. Close the Terminal window to get it out of the way.
Select the startup volume ("Macintosh HD," unless you gave it a different name) if not already selected. You won't be able to do this if FileVault is active.
Select your username from the menu labeled Select the user account if not already selected.
Follow the prompts to reset the password. It's safest to choose a password that includes only the characters a-z, A-Z, and 0-9.
Select
 ▹ Restart
from the menu bar.
You should now be able to log in with the new password, but the Keychain will be reset (empty.) If you've forgotten the Keychain password (which is ordinarily the same as the login password), there's no way to recover it.

Mac Pro freezes when Time Machine starts backup

MacPro1,1, Lion 10.7.5 (this machine won't run Mountain Lion).
Processor Name: Dual-Core Intel Xeon
Processor Speed: 3 GHz
Number of Processors: 2
Total Number of Cores: 4
L2 Cache (per Processor): 4 MB
Memory: 12 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005D.B00
SMC Version (system): 1.7f10
I'm backing up to a newer 3Tb Time Capsule. When TM backup starts other applications freeze, Force Quit is unaccessible, I have to hold down the power button to shut down. This started about a month after starting to use the Time Capsule, now 2 months old. Here's some log data from when TM starts to the shut down:
9/7/13 9:54:44.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:44.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:44.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:44.560 AM com.apple.backupd: Waiting for Spotlight to finish indexing /Volumes/Time Machine Backups/Backups.backupdb
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:45.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:46.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:47.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:48.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:49.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:50.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:50.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.734 AM configd: network configuration changed.
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:51.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 65.
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
9/7/13 9:54:52.031 AM configd: network configuration changed.
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:54.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: Logging in with uam 13 /Volumes/Data
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
9/7/13 9:54:54.000 AM kernel: ASP_TCP ReplayPendingReqs: replaying slot 0 with reqID 2981 afpCmd 0xB on so 0x1e43ce68
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: get the reconnect token
9/7/13 9:54:54.443 AM SLRuntimeLoader: clip: empty path.
9/7/13 9:54:54.444 AM [0x0-0x17d17d].com.canon.SLRuntimeLoader: Sep 7 09:54:54 My-Mac-Pro-6.local SLRuntimeLoader[3031] <Error>: clip: empty path.
9/7/13 9:54:58.738 AM Address Book: Subscription request completed
9/7/13 9:55:10.581 AM [0x0-0x181181].com.apple.iTunes: 2013-09-07 09:55:10.581 The plugin 'Quartz Composer Visualizer' failed to load because it has the wrong CPU architecture for this version of iTunes. (3585)
9/7/13 9:55:22.038 AM com.apple.backupd: Starting standard backup
9/7/13 9:55:22.066 AM com.apple.backupd: Network destination already mounted at: /Volumes/Data
9/7/13 9:55:33.811 AM com.apple.backupd: Disk image already attached: /Volumes/Data/My Mac Pro (6).sparsebundle, DIHLDiskImageAttach returned: 35
9/7/13 9:55:35.601 AM com.apple.backupd: Disk image already attached: /Volumes/Data/My Mac Pro (6).sparsebundle, DIHLDiskImageAttach returned: 35
9/7/13 9:55:36.791 AM com.apple.backupd: Disk image /Volumes/Data/My Mac Pro (6).sparsebundle mounted at: /Volumes/Time Machine Backups
9/7/13 9:55:36.988 AM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
9/7/13 9:55:55.532 AM com.apple.backupd: 1.77 GB required (including padding), 1.09 TB available
9/7/13 9:57:24.944 AM com.apple.backupd: Copied 3262 files (21.5 MB) from volume Internal 1 3TB.
9/7/13 9:57:31.941 AM com.apple.backupd: 1.92 GB required (including padding), 1.09 TB available
9/7/13 9:58:02.477 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.480 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.482 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.483 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.484 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.485 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:26.993 AM com.apple.backupd: Copied 1720 files (304.1 MB) from volume Internal 1 3TB.
9/7/13 10:01:45.000 AM bootlog: BOOT_TIME 1378566105 0
9/7/13 10:01:58.767 AM fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (307606 12 307803)
9/7/13 10:01:59.000 AM kernel: npvhash=4095
9/7/13 10:01:59.000 AM kernel: PAE enabled

Thanks, Linc. Based on earlier posts around the same problem I assumed it was something to do with the computer. TC is up to date and restarting it seems to have corrected the problem, at least during the one TM backup that's gone since.
BTW, I have two internal 3 TB HDs, one with all content, the second which mirrors the first and is updated every night. I'm using the TC/TM as the backup to my backup. I also take a new full copy offsite weekly. Curious though, what do you think of backing up to cloud storage?

New MacBook Pro - continue with Time Machine backups or start over?

I'm unsure of how I should proceed here ...
My old (late 2008 aluminium unibody MacBook) died last month and I now have a shiny new MB Pro. I transferred my data from one of two backup drives I have using Migration Assistant but did not transfer the Pictures folder because the new MB Pro only has a 256GB PCIE drive whereas I had upgraded my old MacBook to a 750GB hard drive. The Pictures folder was 175GB - it obviously couldn't be transferred in its entirety so at this stage I haven't transferred anything at all from my Pictures folder.
Both backup drives I use are 1TB Lacie Rugged external hard drives. I have them partitioned as follows -
Time Machine Backup - 475 GB
SuperDuper Backup - 350 GB
Pictures - 175GB (I only have the iPhoto Library on the Pictures backup)
I was thinking that I could simply continue with the existing backups, however, I realise that will be impossible because the existing backups all include the Pictures folder as part of the 'normal' backup process.
So, should I wipe my backup drives and start all over from scratch with the new MB Pro? Obviously, I don't need such a large space for the Time Machine and SuperDuper backups now so I could re-partition the drives and allocate more space to the Pictures folder (which is the one that continues to grow).
Does anyone else have experience of using their iPhoto Library on an external drive with the smaller PCIE drives in the MB Pro?
I would be very grateful for any suggestions as to how I should proceed.
Tricia

Many thanks for your response Ingo2711. It seems as if we faced pretty much the identical situation.
I've never taken much notice of Time Machine - just let it do its own thing. However, when I go to System Preferences - Time Machine - Options - Exclude these items from Backups and then choose the Pictures folder it shows that the space saved is only 1.47GB (my Pictures folder on my old MacBook is about 175GB). I clicked on the Pictures folder in Finder and discovered that it had one folder in it which is the folder I use for Desktop and Screen Saver and that the size of that folder is, in fact, 1.47GB.
So, am I right in thinking that I can just allow Time Machine to do a full backup without excluding anything and it will see that the new system is different from the previous one or am I missing something? I really don't want to lose the previous backups in case I ever need to go back to something.
Cheers
Tricia
BTW, I'm going to download iPhoto Library Manager and see if I can put my photos in chronological order by year and then just keep the current year's photos on my new Mac and keep the rest on the Pictures partition of my backup drive (which is connected via USB 3) - I'm hoping that the access to the external drive won't be so slow over USB 3.

6th Generation Airport Extreme Freezing During Time Machine Backups using LaCie 1TB Hard Drive

I recently upgraded from a 4th generation Airport Extreme (short, dual band n) to a new 6th generation Airport Extreme (tall, dual-band ac) in the hopes of having quicker backups and better WiFi performance (I also just got a 13" retina MacBook Pro).
The upgrade has gone poorly, to say the least. Initially, I set up the new Airport Extreme as I had for the old one. Then I plugged in the same hard drive I was using (a LaCie 1 TB d2 Quadra USB2 drive that I bought in June of 2009). I decided to setup my wife's Time Machine backup first (she has a 2010 MacBook Air). I removed the "old" disk (the one associated with the old base station) from her Time Machine configuration, and set up her Time Machine configuration to backup to the same disk on the new Airport Extreme. I was pleasantly surprised to find that it picked up her existing Time Machine backup and incrementally synchronized to it (the backup size was about 300 MB). A few days later, she warned me that Time Machine told her that backups were not working. When I went to look, it was indeed failing.
I tried a few things that didn't work, and I suspected that maybe the backup "transfer" hadn't gone so smoothly as it seemed, so I decided to erase the drive using Disk Utility and start the backup over again. To my disappointment, I found that the backup got about 200MB-1.5GB into the backup and "froze." I left it overnight, and it was at exactly the same place the next morning. The light on the disk connected to the Airport Extreme flashed constantly all the time, and I could hear it spinning, but nothing happened at all.
When I tried to stop the backup, it took a very long time. In the logs, I would see a message like this (this log is from my machine, not my wife's, but it looks the same):
11/19/13 9:40:59.276 PM com.apple.backupd[93334]: Forcing deep traversal on source: "***-mpbr" (device: /dev/disk0s2 mount: '/' fsUUID: 7356274E-D28F-3BC0-9CA8-7F1AA21830B4 eventDBUUID: 99941F9A-AD5F-4FAF-94D2-701C94CA9581)
11/19/13 9:41:57.609 PM com.apple.backupd[93334]: Total content size: 148.2 GB excluded items size: 17.16 GB for volume ***-mpbr
11/19/13 9:41:57.610 PM com.apple.backupd[93334]: Found 674166 files (131.05 GB) needing backup
11/19/13 9:41:57.611 PM com.apple.backupd[93334]: 152.52 GB required (including padding), 498.67 GB available
11/19/13 9:41:57.625 PM com.apple.backupd[93334]: Waiting for index to be ready (100)
11/19/13 9:59:22.407 PM UserEventAgent[11]: com.apple.backupd-auto launchd job disabled
11/19/13 10:00:15.103 PM com.apple.backupd[93334]: Cancellation timed out - exiting
Looking at the Airport Extreme in Finder, I saw that it got stuck, either "Connected as" me, or "Connecting...". The Airport Extreme wouldn't respond to the "Disconnect" or "Connect As..." buttons (depending on the context), and the eject button for the Airport Extreme itself in the sidebar was also unresponsive. Eventually, after 2+ minutes, I got a dialog saying "Couldn't connect to [my base station name]" with instructions to "check its IP" and contact my system administrator if the problem persists. During this time, Finder can seem frozen and unstable.
Through all of the above, the hard disk kept spinning and the light flashed constantly. The drive was warm to the touch in the morning.
I also found that when all this happened, I was unable to connect to the Airport device using Airport Utility. I I couldn't administer it, but the Internet continued to work for all connected devices. Unplugging the disk and plugging it back in worked immediately to bring the system back to a working state. I didn;t even have to power-cycle or reset the Airport Extreme.
I tried a number of things to correct this behavior:
Disabled Time Machine, removed disk, restarted machine, reconfigured Time Machine, and retried.
Tried backup on my 13" Retina MacBook Pro and my wife's MacBook Air.
I actually tried with TWO new 6th Generation Airport Extremes. The first one was a refurbished one. I returned it to Apple and purchased a brand new one. Both of them exhibited the behavior I described above.
Workaround:
Finally, I switched the drive out for a spare that I have (an older Western Digital MyBook and used it for a backup. This drive "Just worked."
So, I have switched to that for backup for now, and re-purposed the LaCie as a drive that I use for making periodic images of my hard drive using SuperDuper. The drive seems to work perfectly (and worked perfectly for several years with older Airport Extreme base stations), so I can only assume there's a bug in the USB driver of the current 6th-generation Airport Extreme.
I hope this helps someone else who's as confused as I was. If anyone has had a similar experience, I would very much like to read about it. I will be reporting this problem to apple right after I post this topic. Please do the same if you experience this issue.

As Bob says, backing-up that way isn't supported.
It's also unreliable. It may work for a while, but this forum, and the Time Machine forums, have many, many posts like this:
*"I've been backing-up via an Airport Extreme for* <some number of days, weeks, or months> *and all of a sudden my backups are corrupted beyond repair."*
In my case, it's happened about 4 times in a year. And that's with a desktop Mac, about 12 feet from the Airport, with the exact same hardware in exactly the same place and no interference.
It is very convenient, especially with laptops. If you want to take the risk, see [Using Time Machine with an Airport Extreme Air Disk|http://web.me.com/pondini/Time_Machine/Airport.html] (or use the link in *User Tips* at the top of this forum).
But do yourself a LARGE favor and take the prominent advice to keep secondary backups, and update them frequently. Sooner or later, you're probably going to need them.

Microsoft Word for Mac Freezes During Time Machine Backup

Since upgrading to Lion, I have found that when Time Machine is performing a backup that word for Mac freezes. I have all software updates for both Mac and MS. Running on 17" MacBook Pro.
Any ideas?
This appears to be the same issue:
https://discussions.apple.com/thread/2403912?start=0&tstart=0
Thanks in advance.

The Time Machine backup data on the network device is corrupt. The first thing you should do, if that's your only backup, is to make another complete backup to a locally attached storage device. One backup is never enough to be safe. Network backups are less reliable than local ones.
After that, hold down the option key and select Verify Backups from the Time Machine menu in the menu bar (not the Dock icon.) This operation may take a long time. If the menu-bar icon (a clock that runs backwards) isn't showing, check Show Time Machine in menu bar in the preferences.
If you continue to get panics, erase the backup device. With an AirPort device, you do that from within the AirPort Utility application; see its built-in help for details. All backups will be lost, so don't do this until you've backed up to another device. After erasing, select the device again as a backup destination in the Time Machine preference pane. The first backup should be made over a wired connection, if possible.
If you still have problems after erasing the device, it should be replaced.

System-wide freeze when Time Machine begins back up - Mac Pro 10.7.5

I have recently upgraded my MacPro Intel Early 2008 to Lion 10.7.5 on an external drive. Overall this nice fresh install has been working very well. The problem is that every 2 hours Time Machine starts its automatic back up and then ...
A) Music playing on Spotify stops
B) Curser freezes
C) Application switching freezes
D) Current app stops working
This freeze typically lasts about 15 to 30 seconds, or until the small incremental back up is finished.
I have verified the cause using the Console and reading the activity. I read the log 4 times yesterday (it has been doing this since I upgraded a week ago) to confirm this activity. Usually the log reports the begin and finish of the backup with no activity in between, but in the freeze I just had there was activity in the middle relating to Spotify. That most recent log is shown below. For the record, nearly all of the log activity is something to do with Spotify unless I am doing some other system level process.
I have studied other threads, but the symptoms don't really match those, or I don't have the same suspect apps installed. I have run Disk Utility and Disk Warrior on the Time Machine internal drive, and it appears ok. In energy settings the hard drive disks are NOT set to sleep when possible, but the computer will sleep after an hour of inactivity.
My Time Machine is getting large and using some 90% of the disc. I think I need to redo it because the old (10.5.8 & 10.6) and new system (10.7) inadvertantly wrote to the same TM backup. Thoughts on that?
Here is the last freeze (I truncated the IP addresses) ... and thanks, I appreciate your help. L
7/12/13 10:54:14.857 AM [0x0-0x1c01c].com.spotify.client: 14:54 I [audio_streamer.cpp:538
] 64k-Latency: 2 ms. Play latency: 484 ms (ap)
7/12/13 10:58:35.743 AM com.apple.backupd: Starting standard backup
7/12/13 10:58:35.771 AM com.apple.backupd: Backing up to: /Volumes/Mac Pro Time Machine/Backups.backupdb
7/12/13 10:58:44.850 AM com.apple.backupd: 6.00 GB required (including padding), 99.59 GB available
7/12/13 10:59:02.068 AM [0x0-0x1c01c].com.spotify.client: 14:59 E [watchdog.cpp:171
] Deadlock detected (Thread: gui)
7/12/13 10:59:07.386 AM [0x0-0x1c01c].com.spotify.client: 14:59 E [watchdog.cpp:191
] The deadlock was a lie! (gui, 10533)
7/12/13 10:59:09.749 AM Firewall: Allow Spotify connecting from 64.55:9907 to port 64429 proto=6
7/12/13 10:59:11.619 AM [0x0-0x1c01c].com.spotify.client: 14:59 E [watchdog.cpp:171
] Deadlock detected (Thread: gui)
7/12/13 10:59:12.739 AM [0x0-0x1c01c].com.spotify.client: 14:59 E [watchdog.cpp:191
] The deadlock was a lie! (gui, 5120)
7/12/13 10:59:16.753 AM Firewall: Allow Spotify connecting from 184.17:65289 to port 64429 proto=6
7/12/13 10:59:16.764 AM Firewall: Allow Spotify connecting from 74.40.0:50925 to port 64429 proto=6
7/12/13 10:59:16.765 AM Firewall: Allow Spotify connecting from 68.41:58285 to port 64429 proto=6
7/12/13 10:59:16.766 AM Firewall: Allow Spotify connecting from 216.23.:1526 to port 64429 proto=6
7/12/13 10:59:16.807 AM Firewall: Allow Spotify connecting from 108.2:59770 to port 64429 proto=6
7/12/13 10:59:16.959 AM Firewall: Allow Spotify connecting from 64.203:62864 to port 64429 proto=6
7/12/13 10:59:16.967 AM Firewall: Allow Spotify connecting from 12.1747:3148 to port 64429 proto=6
7/12/13 10:59:16.986 AM Firewall: Allow Spotify connecting from 76.97.:52319 to port 64429 proto=6
7/12/13 10:59:16.997 AM Firewall: Allow Spotify connecting from 70.114:60921 to port 64429 proto=6
7/12/13 10:59:17.020 AM Firewall: Allow Spotify connecting from 66.214:62861 to port 64429 proto=6
7/12/13 10:59:46.808 AM [0x0-0x1c01c].com.spotify.client: 14:59 I [audio_streamer.cpp:538
] 64k-Latency: 2 ms. Play latency: 31 ms (ap)
7/12/13 11:00:03.592 AM [0x0-0x13013].com.stclairsoft.DefaultFolderX.helper: DFX: Finder query returned error -1701
7/12/13 11:00:12.784 AM Firewall: Allow Spotify connecting from 76.14.156.134:55682 to port 64429 proto=6
7/12/13 11:00:32.831 AM [0x0-0x3a03a].org.mozilla.firefox: NOTE: child process received `Goodbye', closing down
7/12/13 11:00:58.261 AM com.apple.backupd: Copied 2527 files (130.0 MB) from volume OSX Upgrades HD.
7/12/13 11:00:58.779 AM com.apple.backupd: 5.85 GB required (including padding), 99.46 GB available
7/12/13 11:01:04.028 AM com.apple.backupd: Copied 1265 files (2.3 MB) from volume OSX Upgrades HD.
7/12/13 11:01:05.428 AM mds: (Error) Volume: Could not find requested backup type:2 for volume
7/12/13 11:01:05.429 AM com.apple.backupd: Starting post-backup thinning
7/12/13 11:01:05.429 AM com.apple.backupd: No post-back up thinning needed: no expired backups exist
7/12/13 11:01:05.771 AM com.apple.backupd: Backup completed successfully.

Hi Hatter - thanks for the info, interesting. When making these upgrades, which I resisted for as long as possible, I needed to make it as quick and painless, with "minimal" disruption in my work. It still took three weeks to plan and execute, plus it has been a week of fiddling - that is a lot of time to devote to computer maintenance. I kept the original system as a back-up in case things really went south. Also I need 10.5 because I have several active legacy client web sites in GoLive CS2, which I tried in 10.6, but it did not run well.
I agree that doing things off the internal drives is faster to operate, but my approach was prudent. Later I can swap those around. My external 10.7 drive is a WD My Passport Studio, and has had no problems (except the sucker runs pretty hot). I considered the SSD but the price is still high: NewEgg, internal 500GB regular drive today is $60 - 75, 500GB SSD is $340-370. That is a pretty big difference in a small business. I am maxed out on RAM, so that helps a lot.
One last thing though, for the Adobe Creative Suite the scratch discs are the internal drives, so it still runs fast in that sense. Fast is relative ya know, I remember programs taking 40 and 50 seconds to launch, now Photoshop is 19, barely time to drink some coffee.
I have bought a number of UPS over the years, including replacement batteries. It has been expensive frustration, because in a real emergency they seldom do what they promise. In Colorado there are big thunderstorms every summer, and I field tested them a number of times - but was never happy with the protection. Dollar for dollar, investing in a whole house (or whole office) surge arrester at the main utility panel offers protection for the equipment, with about the same amount of time to save your work (which in reality is about 1 second).
I had a ton of connection issues with Spotify working in 10.5, but I am happy to say those have completely gone away with this upgrade. I also like many of the refinements in Lion, such as the improved System Profiler.
Linc, I will will take a look at your suggestion, it is a little vaque. Am I looking for a perticular result ? I don't want to operate for too long with the firewall off.
I think my first step is getting the Time Machine figured out, that could be the whole issue.
Thanks guys for the input -- it is appreciated. L

All media files vanished. When time machine backup attempted it says disk full? Confused help.

I recently upgraded from osx leopard to snow leopard on my 2008 macbook to sync my new iphone data smoothly. After the installation it was v slow as anticipated and a time machine full restore was done successfully. Now however all my media files have vanished namely precious music videos and pictures. I tries reverting back in time machine but it says no disk space. Also i have 1000 new pictures last uploaded which gas also been backed up by time machine with the computer showing the rest of the files erased. How do i recover both sets of data the old and the new?

How much free space on your internal drive and how much free space on the Time Machine drive? You can use Disk Utility in Applications/Utilities to find free space. If Time Machine gets too full it could delete your backups. I suggest your turn off Time Machine in System Preferences until you get your files restored.
Rather than enter Time Machine using the Time Machine interface, go to the extrernal drive and drill down in the backups.backupdb folder. Go to a date when you know the files existed. Select Macintosh HD > Users > You > Pictures. Do you see the data. Check size? Do the same for Music.
You can drag from these folders to your Desktop as long as you have space on your internal drive.
I suspect you'll need to erase your Time Machine and start new or you'll need to purchase a larger drive. It's recommended that your Time Machine drive is 3X larger than internal drive.

Time Machine - Backup Starts, But Won't Complete

Hi all,
I've been using Time Machine with a 2TB Time Capsule (purchased a few months ago) that won't do a backup anymore. Here are the error messages:
+The backup was not performed because an error occurred while copying files to the backup disk.+
+The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair your backup disk.+
+Time Machine Error+
+The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair your backup disk.+
+Latest successful backup: 10-02-15 at 14:57+
Here are the log messages:
+Starting standard backup+
+Attempting to mount network destination using URL: afp://[email protected]/Data+
+Mounted network destination using URL: afp://[email protected]/Data+
+Disk image /Volumes/Data/Sean’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups+
+Backing up to: /Volumes/Time Machine Backups/Backups.backupdb+
+No pre-backup thinning needed: 45.51 GB requested (including padding), 1.62 TB available+
+Indexing a file failed. Returned 200 for: /Library/Keychains/System.keychain, /Volumes/Time Machine Backups/Backups.backupdb/Sean’s MacBook Pro/2010-02-15-155508.inProgress/F373C449-00B9-4411-88C4-95B00E51D6E3/Macintosh HD/Library/Keychains/System.keychain+
+Aborting backup because indexing a file failed.+
+Stopping backup.+
+Copied 129 files (83 KB) from volume Macintosh HD.+
+Copy stage failed with error:11+
+Backup failed with error: 11+
+Ejected Time Machine disk image.+
+Ejected Time Machine network volume.+
I've tried verifying and repairing the sparsebundle using the Disk Utility program (no improvement) and I've also tried to reset Time Machine (again, no success). What else do I need to try? The access point and printer sharing work fine, so the problem seems to be software-based.
Any suggestions as to what I should try next? I'm a bit out of ideas.
Thanks!

Thanks for the help - failed again this time...here are the logs:
+Starting standard backup+
+Attempting to mount network destination using URL: afp://[email protected]/Data+
+Mounted network destination using URL: afp://[email protected]/Data+
+Disk image /Volumes/Data/Sean’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups+
+Backing up to: /Volumes/Time Machine Backups/Backups.backupdb+
+No pre-backup thinning needed: 45.52 GB requested (including padding), 1.62 TB available+
+Indexing a file failed. Returned 200 for: /Library/Application Support/MindVision, /Volumes/Time Machine Backups/Backups.backupdb/Sean’s MacBook Pro/2010-02-15-155508.inProgress/903BABC7-5AB5-4241-97ED-37BE76D20A40/Macintosh HD/Library/Application Support/MindVision+
+Aborting backup because indexing a file failed.+
+Stopping backup.+
+Copied 75 files (21 KB) from volume Macintosh HD.+
+Copy stage failed with error:11+
+Backup failed with error: 11+
+Ejected Time Machine disk image.+
+Ejected Time Machine network volume.+
Any ideas on what to try now? Should I exclude this directory or try something different?
Thanks!

Finder Freezing when time machine back up files

I've an 24 aluminium iMac. The finder often freeze (once a day at least) and I noticed that this is often when Time Machine is backing up files.
It's impossible to relaunch the finder and sometimes other mac apps are freezing (preferences etc..). On the dock I can still see that the finder and the apps are active but in fact there are frozen and it is not possible to force quit.
Then if I shut down the computer through the apple menu it doesn't work and the only solution is to shut down manually my iMac with the back button.
Be that as it may it is less frequent since the iMac last software update (graphic card) before everything on the screen was freezing.

I have a 1tb and 540 tb Ultramax Harddrive to support my Mac Pro G5. I originally bought the 650 when the G5 was running Tiger and it worked without fault on a 800 firewire. I partly purchased this model of drive as they advertised its extendibility. When time machine was announced I purchased a second 1tb version and installed the two drives running daisy chained by 800 firewire and they worked fine. Maybe 2 weeks after installing Leopard which had caused me problems because of the application enhancer i was not ready to use time machine so declined to switch it on.
After a few weeks and after the 650 had dismounted itself i started to find after waking from sleep the mac was frozen. There was no way out other than switch it off on the front switch. I later discovered that on powering down the 650 ultramax I could recover my processes but at the danger of corrupting the drive by not removing it properly. As I tried to work out an exit strategy to save data on the 650 I got a system warning to say the Ultramax was beyond repair and was available only to recover files. Eventually it started hanging after a few seconds so i had no choice but to lose data and reformat the drive. That failed and having already contacted Iomega support for advice with little support they eventually agreed the drive had become damaged and agreed to replace the unit.
With the new unit I expected the problem would be gone.. but it was a matter of hours before the symptoms re-emerged, not as bad as before they seemed to allow other apps to continue to run and work it just disabled the finder so i could open an application from recent apps but not through a finder window and if i asked it to open or save a file it would lock the application so much not even a three fingered quit would solve the problem it would close the app in the finder but in the close app window it would remain listed as not responding.. the only way to recover use of the mac was to power off the ultramax almost on loosing power all hanging functions would re-emerge sometimes i needed to switch the mac off.
I decided to risk setting time machine on and although it worked it hung on the first back up and ever since I have woken up the mac as i run a very eco friendly power management policy I would find the hang accompanied by time machine backing up.
I am sure time machine is part culprit in this problem although i cant work out why only the 650 suffers I have tried taking it off firewire and moving to usb and it still does the same....
Any ideas or pointers to an answer of any sort would be welcome

Macbook Air freezes when changing screensaver

I am having issues when I try to change my screensaver. Whenever I click on a different screensaver option, my Macbook Air freezes, and I have to force close System Preferences. I have no problems with changing my desktop wallpaper. I have restarted my laptop but it still freezes.
I saw another board with a similiar problem except instead of the screensaver window freezing, their desktop window would freeze.
Any ideas? Thanks in advance for any suggestions!

Back up all data. Quit System Preferences if it's running.
Triple-click anywhere in the line below on this page to select it, then copy the text to the Clipboard by pressing the key combination command-C:
~/Library/Preferences/ByHost
In the Finder, select
Go ▹ Go to Folder...
from the menu bar. Paste into the box that opens (command-V), then press return. A folder should open. If it does, look for a file with a long name that begins "com.apple.screensaver". There may be several such files. Move them to the Trash.
Test. If the problem is resolved. recreate your settings in the Screen Saver tab.

My iMac freezes when time machine is running a backup

Hi Guys, this is an iMac that had tiger and I upgraded to 10.5.8
I am using time machine with a 2TB external flex drive from seagate (brand new item)
The back ups went smooth for the first few days but now my iMac totally freezes up at least once a day and the time machine status indcator shows that it is running the whole time.
I tried apple/option/escape but that does nothing so I have to force shut down using the start button on the back of the iMac.
I don't know what to do next so any help would be awesome.

bassplayer360 wrote:
Hi Guys, this is an iMac that had tiger and I upgraded to 10.5.8
I am using time machine with a 2TB external flex drive from seagate (brand new item)
Start by making sure it's set up properly, per #C1 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).
The back ups went smooth for the first few days but now my iMac totally freezes up at least once a day and the time machine status indcator shows that it is running the whole time.
That sounds like something may be corrupted, either on your internal HD or the TM drive. Verify the internal, and repair the TM drive, per #A5 in Troubleshooting
I tried apple/option/escape but that does nothing so I have to force shut down using the start button on the back of the iMac.
If a backup hangs, try to cancel it, either via +Stop Backing Up+ from the TM icon in your menubar, or by right-clicking the TM icon in your dock. If it won't cancel after a few minutes, see #D6 in Troubleshooting.
Then see #A1 for a handy widget that will display the backup messages from your logs. Look at the ones for the backup you cancelled; a clue may be lurking there.
If in doubt, copy and post them here.

MacBook keeps freezing during Time Machine?

Hello! My computer keeps freezing up about 10 minutes into Time Machine. I have an internal 320gb drive and I am attempting to back it up to the Maxtor OneTouch4 Mini 250gb external hard drive I was using previously to back up my PowerBook G4. Also is it possible to keep my G4 files on there and use it to back up my MacBook?

Strawbs7 wrote:
Thanks for the link to the safe mode start up info - I'll give that a go tonight.
Among other things, that will check the directory structure and fix it if possible. That might be all you need.
I'm on 10.6.8 and my brother upgraded me so I guess he still has the discs, I will check. Is that for a reinstallation?
You need the main one to reinstall OSX (only; that doesn't disturb anything else), or to restore from TM backups. You may not need to do either, but should always have the disc handy.
What did your Mac ship with, and do you have the original discs? One of them has an Apple Hardware Test specific to your Mac. It's not real extensive, but might find any hardware problems.
Only I'm not really wanting to do anything like that til I've backed up - bit of a catch 22!!
If you're sure the backups were completing until recently, eject and disconnect the drive until you need it. No sense risking any damage to them!
If you have or can borrow another external, you might be able to make a copy of the current contents of your HD on it, via the Restore tab in Disk Utility. From your description it sounds doubtful, but might be worth a try.
And/or, if you have some CDs/DVDs or a USB Thumb drive, you might be able to copy some stuff to them.

Macbook Air Freezes when Time Machine backup starts

Similar Messages

Maybe you are looking for