Time Machine not speaking to my Mac (error message -6753)
My time machine has stopped backing up and when I try to reconnect Time Capsule gets the connect messages but will not respond, except with error messages saying it is not available.
1. Airport Utility recognises that the Time Capsule hard drive exists but will not do a manual or auto configuration.
2. Time Machine app does list the Time Capsule ("Data" on "Time Capsule") in the "Select backup disk..." but does not display the amount of Gb available though it does with the other disks listed - these are all FireWire connected, while Time Capsule is connected via Ethernet (which I prefer to AirPort).
3. Have tried deleting the plist, but this has not solved the problem.
4. Have looked at the help lists tried a few other thing but nothing works (including changing from Ethernet to AirPort). I have searched online for error -6753, but get 0 results.
5. I have done a few screen shots but it seems I cannot attach files
Since I cannot put my screenshots online, here is a line from NetBarrier indicating that my Mac is connecting to Time Capsule:
18/02/2010, 16:50:02
Source: 192.168.1.64
Destination: 169.254.141.19
Protocol: TCP
Src Port: 51942
Destination Port: 5009
Flags: S
Interface: en0
Kind: Outgoing connection
I feel my description of the problem is rather inadequate, so if anyone feels they could help if I provided more info then please ask me.
Thanks for any help.
Forgot to mention that the light is green on my Time Capsule and all the lights with the cables are also green.
Similar Messages
-
Time Machine prepares backup but cancels without error message before starting backup
Hello.
I'm running OS 10.9.1 on a 2013 iMac. Time Machine has not backed up for a few weeks. Have tried verifying the backup with no problems reported. Can't mount 1TB Time Capsule or relevant sparsebundle in Disk Utility. Went to Console and copied the relevant logs:
1/12/14 8:25:06.310 AM com.apple.backupd[1456]: Starting manual backup
1/12/14 8:25:06.320 AM com.apple.backupd[1456]: Network destination already mounted at: /Volumes/Data
1/12/14 8:25:29.000 AM kernel[0]: hfs: mounted Time Machine Backups on device disk4s2
1/12/14 8:25:31.268 AM com.apple.backupd[1456]: Disk image /Volumes/Data/Macintosh.sparsebundle mounted at: /Volumes/Time Machine Backups
1/12/14 8:25:31.284 AM com.apple.backupd[1456]: Backing up to /dev/disk4s2: /Volumes/Time Machine Backups/Backups.backupdb
1/12/14 8:25:31.481 AM mds[65]: (Error) Volume: Root store set to FSOnly with matching create! (loaded:1)
1/12/14 8:26:00.273 AM com.apple.backupd[1456]: Deep event scan at path:/Users/[redacted]/Pictures/iPhoto Library cellphone/Database/apdb reason:contains changes|must scan subdirs|fsevent|missed reservation|file event|
1/12/14 8:26:04.372 AM com.apple.backupd[1456]: Finished scan
1/12/14 8:26:04.376 AM com.apple.backupd[1456]: Not using file event preflight for Macintosh HD
1/12/14 8:26:44.000 AM kernel[0]: disk4s2: 0xc005 (UNDEFINED).
1/12/14 8:26:51.000 AM kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
1/12/14 8:26:51.601 AM diskimages-helper[1470]: terminating disk4 - image is no longer available
[here follows various repeated disk4s2 undefined messages]
1/12/14 8:26:51.603 AM com.apple.backupd[1456]: Stopping backup to allow backup destination disk to be unmounted or ejected.
[here follows various repeated disk4s2 undefined messages]
1/12/14 8:26:52.000 AM kernel[0]: hfs: Runtime corruption detected on Time Machine Backups, fsck will be forced on next mount.
1/12/14 8:26:52.000 AM kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
[last two lines repeated about a dozen times]
1/12/14 8:26:52.000 AM kernel[0]: hfs: cat_delete() failed to delete thread record id=81 on vol=Time Machine Backups
1/12/14 8:26:52.000 AM kernel[0]: hfs: Runtime corruption detected on Time Machine Backups, fsck will be forced on next mount.
1/12/14 8:26:52.000 AM kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
1/12/14 8:26:52.000 AM kernel[0]: disk4s2: 0xe000c2e4 (UNDEFINED).
1/12/14 8:26:52.239 AM com.apple.backupd[1456]: Backup canceled.
1/12/14 8:26:52.000 AM kernel[0]: hfs: BlockMarkFreeInternal() trying to free unallocated blocks on volume Time Machine Backups
1/12/14 8:26:52.000 AM kernel[0]: hfs: Runtime corruption detected on Time Machine Backups, fsck will be forced on next mount.
1/12/14 8:26:52.000 AM kernel[0]: hfs: unmount initiated on Time Machine Backups on device disk4s2
1/12/14 8:26:57.284 AM com.apple.backupd[1456]: Ejected Time Machine disk image: /Volumes/Data/Macintosh.sparsebundle
1/12/14 8:26:57.000 AM kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data, flags 0, pid 1500
1/12/14 8:26:57.000 AM kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xffffff8054511530
1/12/14 8:26:57.000 AM kernel[0]: ASP_TCP Detach: Reply queue not empty?
1/12/14 8:26:57.759 AM com.apple.backupd[1456]: Ejected Time Machine network volume.
This basic sequence seems to have happened every time I've tried to run backup lately. Pondini's A6 mentions the deep event scan related to iPhoto but not what to do about it. Help?I decided, based on various clues from Pondini's page, that the hard drive in my Time Capsule was failing. I started a full backup on my second Time Capsule and am currenly only using the original as an internet router.
-
Time Machine won't backup – but no error message
Hi community,
I'm using TimeMachine with MacOs Version 10.6.8, on an iMac with an 3.2 GHz Intel Core i3 Processor.
Actually, I was pretty happy with it for several months, never had any error messages.
But suddenly, TimeMachine started to backup the same files over and over again. It created new folders with the current and correct date, but in the folders there are no "new" files, even if there are numerous of new files on my hard drive.
So I thought, perhaps there's not enough space left on my external drive, so I bought a new one. Same problem here. It backed up correctly a few weeks, then it started to back up the same files over & over again.
My hard drive has a capacity of about 1 TB, my USB drive is a Samsung with 600 GB Capacity, formatted with MacOS Extended (Journaled)
Space used on my hard drive: 417 GB, free space on my USB drive: 252 GB > haha, that's probably the problem, but I thougt TimeMachine erases the older files on the external drive if there is no more space left?
And: why isnt't there an error message, then?
Hope anyone can help! Thanks in advance!
Verenahi eric,
thank you for your quick answer! what the console says is the following (extract):
Post-back up thinning complete: 5 expired backups removed
Backup completed successfully.
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
No pre-backup thinning needed: 1.13 GB requested (including padding), 206.20 GB available
Copied 744 files (2.7 MB) from volume [myvolume].
No pre-backup thinning needed: 1.13 GB requested (including padding), 206.20 GB available
Copied 67 files (93 bytes) from volume [myvolume].
Starting post-backup thinning
Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/[myvolume]/2011-10-05-170346: 206.20 GB now available
Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/[myvolume]/2011-10-05-110315: 206.21 GB now available
Post-back up thinning complete: 5 expired backups removed
Backup completed successfully.
Actually, this time it really backed up my data … but why now and a few days ago it didn't? (Console also says "Backup completed successfully." for this date.)
Hm anyways, seems to work now, but I don't like the thought that I can't rely on it … would like to understand what this machine is doing … :-) -
"Time Machine is unable to complete backup" error message
I've tried to run Time Machine 3 times since last night and each time it gets through about 85 GB with about 150 GB remaining. Then a message comes up that says "Unable to complete backup. An error occurred while copying files to the backup volume." I checked the Support Troubleshooting section before the last attempt, and reformatted the disk as it suggested. (The disk is a new Western Digital 500 GB). Based on the response to a similar discussion posted recently, I went into my Console and copied the below. Obviously this is all Greek to me, so if anyone has any insight on how I can get Time Machine to work as it's intended, I'd sure appreciate it!
Emilie
5/11/08 12:40:23 PM Disk Utility[51268]
5/11/08 12:40:53 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 12:41:30 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 12:43:03 PM DYMO Label[51342] * -[NSConcreteTextStorage useTypingAttributesFontSize]: unrecognized selector sent to instance 0x167410
5/11/08 12:43:03 PM DYMO Label[51342] <NSATSTypesetter: 0x16ab30>: Exception * -[NSConcreteTextStorage useTypingAttributesFontSize]: unrecognized selector sent to instance 0x167410 raised during typesetting layout manager <NSLayoutManager: 0x169eb0>
1 containers, text backing has 0 characters
selected character range {0, 0} affinity: upstream granularity: character
marked character range {0, 0}
Currently holding 0 glyphs.
Glyph tree contents: 0 characters, 0 glyphs, 1 nodes, 32 node bytes, 0 storage bytes, 32 total bytes, 0.00 bytes per character, 0.00 bytes per glyph
Layout tree contents: 0 characters, 0 glyphs, 0 laid glyphs, 0 laid line fragments, 1 nodes, 32 node bytes, 0 storage bytes, 32 total bytes, 0.00 bytes per character, 0.00 bytes per glyph, 0.00 laid glyphs per laid line fragment, 0.00 bytes per laid line fragment
, glyph range {0 0}. Ignoring...
5/11/08 12:53:26 PM SpamSieve[51227] * -[NSCFNumber count]: unrecognized selector sent to instance 0x313be0
5/11/08 12:53:26 PM SpamSieve[51227] Exception raised during posting of notification. Ignored. exception: '* -[NSCFNumber count]: unrecognized selector sent to instance 0x313be0' invoked observer method: '* -[ABAddressBook databaseChangedExternally:]' observer: 0x4f75430 notification name: 'ABDatabaseChangedNotificationPriv'
5/11/08 12:53:58 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 12:55:11 PM com.apple.launchd[213] ([0x0-0x6c66c6].com.apple.finder[40722]) Exited abnormally: Bus error
5/11/08 12:55:19 PM com.apple.launchd[213] ([0x0-0x719719].com.apple.finder[51524]) Exited abnormally: Bus error
5/11/08 12:55:27 PM com.apple.launchd[213] ([0x0-0x71a71a].com.apple.finder[51527]) Exited abnormally: Bus error
5/11/08 12:55:35 PM com.apple.launchd[213] ([0x0-0x71b71b].com.apple.finder[51531]) Exited abnormally: Bus error
5/11/08 12:55:43 PM com.apple.launchd[213] ([0x0-0x71c71c].com.apple.finder[51533]) Exited abnormally: Bus error
5/11/08 12:55:51 PM com.apple.launchd[213] ([0x0-0x71d71d].com.apple.finder[51537]) Exited abnormally: Bus error
5/11/08 12:55:59 PM com.apple.launchd[213] ([0x0-0x71e71e].com.apple.finder[51539]) Exited abnormally: Bus error
5/11/08 12:56:07 PM com.apple.launchd[213] ([0x0-0x71f71f].com.apple.finder[51543]) Exited abnormally: Bus error
5/11/08 12:56:15 PM com.apple.launchd[213] ([0x0-0x720720].com.apple.finder[51546]) Exited abnormally: Bus error
5/11/08 12:56:23 PM com.apple.launchd[213] ([0x0-0x721721].com.apple.finder[51549]) Exited abnormally: Bus error
5/11/08 12:56:32 PM com.apple.launchd[213] ([0x0-0x722722].com.apple.finder[51553]) Exited abnormally: Bus error
5/11/08 12:56:41 PM com.apple.launchd[213] ([0x0-0x723723].com.apple.finder[51557]) Exited abnormally: Bus error
5/11/08 12:56:49 PM com.apple.launchd[213] ([0x0-0x724724].com.apple.finder[51559]) Exited abnormally: Bus error
5/11/08 12:56:58 PM com.apple.launchd[213] ([0x0-0x725725].com.apple.finder[51563]) Exited abnormally: Bus error
5/11/08 12:57:08 PM com.apple.launchd[213] ([0x0-0x726726].com.apple.finder[51566]) Exited abnormally: Bus error
5/11/08 12:57:16 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 12:57:52 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 1:04:21 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 1:18:34 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 1:26:28 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 1:27:58 PM com.apple.launchd[1] (0x10a5a0.mdworker[51425]) Exited abnormally: Segmentation fault
5/11/08 1:28:07 PM com.apple.launchd[1] (0x10a5a0.mdworker[52109]) Exited abnormally: Segmentation fault
5/11/08 1:29:04 PM com.apple.launchd[1] (0x10a5a0.mdworker[52113]) Exited abnormally: Segmentation fault
5/11/08 1:29:11 PM com.apple.launchd[1] (0x10a5a0.mdworker[52128]) Exited abnormally: Segmentation fault
5/11/08 1:51:17 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 2:08:20 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 2:29:00 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 4:08:42 PM mdworker[51312] Cannot find function pointer MetadataImporterPluginFactory for factory 1674F1EB-76AA-4CAB-A44F-789AB49B4980 in CFBundle/CFPlugIn 0x1434d0 </Applications/RealPlayer.app/Contents/Library/Spotlight/RealMedia Metadata Importer.mdimporter> (bundle, loaded)
5/11/08 4:38:38 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 5:03:35 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 5:11:30 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 5:12:54 PM com.apple.launchd[1] (0x10a5a0.mdworker[54826]) Exited abnormally: Segmentation fault
5/11/08 5:13:03 PM com.apple.launchd[1] (0x10a5a0.mdworker[55455]) Exited abnormally: Segmentation fault
5/11/08 5:13:52 PM com.apple.launchd[1] (0x10a5a0.mdworker[55457]) Exited abnormally: Segmentation fault
5/11/08 5:14:00 PM com.apple.launchd[1] (0x10a5a0.mdworker[55470]) Exited abnormally: Segmentation fault
5/11/08 5:26:11 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 5:33:57 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 6:53:34 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 7:02:55 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 7:03:27 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 7:03:41 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
5/11/08 8:10:45 PM mdworker[51312] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.Well now I've got a whole new, much bigger problem. I did the renaming and then went through the indexing procedure for the 3 partitions of my main drive. So after that I did a restart. However, after the restart, there were (and are) no icons on my desktop. Nothing for my drives, files, etc. The only thing that shows is the dock at the bottom. If I open an application from the dock, it opens fine and then I've got the menu bar at the top. But the finder won't open. When this first happened, and I checked the Spotlight icon top right, it said was 'estimating index time" for both of my external hard drives (which I did not select when I was in the Privacy tab, etc.). One of those has my iPhoto library of 5,000+ photos and one is the empty back-up drive for Time Machine. Those "estimating indexing time" messages stayed for some time but have now gone away (without ever indicating that indexing was taking place), but still no change. I've restarted again and it's the same. Help!
-
Time machine after migration to new mac - problem
After migrating all of the data from a MacBook Pro to a new iMac 27, I discovered a glitch in the Time Machine backup. I kept getting error messages that Time Machine could not back up 560 gigs but my new machine had only 160 gigs on the hard drive for backup. After discussions with the hard drive manufacturer, and an Apple representative, I read on the forum about backing up multiple hard drives. This gave me an idea, and sure enough, I have two additional hard drives daisy chained to the backup hard drive. Apparently Time Machine was also trying to back up the two additional hard drives (which I use for additional backups). After excluding those two extra hard drives in system prefs under Time Machine options, the problem went away. Now for the first time in a few years, Time Machine is backing up only my primary computer.
Sorry, I was posting this for anyone who had a similar problem. I solved my own question - dufus as I was - and posted this for the edification of others.
-
Time Machine not backing up. Very slow, essentially hanging. I have 10.7.5 Mac OS X Lion (11G63). I have put in all updates. I tried to put my folders into "private" in the Spotlight (b/c I read that might be the problem). Still not working.
Thanks in advance for any help!For all things Time Machine see Pondini's excellent information here...
http://pondini.org/OSX/Home.html
Start at Troubleshooting. -
I used migration assn't to load a Time Machine backup onto a new mac. The first TM backup after that took some time, perhaps not surprising. But the backups thereafter have all taken hours, with huge amounts of "indexing" time. Time to reload TM?
Does every backup require lots of indexing? If so, the index may be damaged.
Try Repairing the backups, per #A5 in Time Machine - Troubleshooting.
If that doesn't help, see the pink box in #D2 of the same link. -
Help w/ Time Machine Not Backing Up
I have a MacBook Pro running Mac OS X v. 10.7.5 and an older (flat, not tall) Time Machine which keeps showing an error and not backing up. The error says: "The backup disk image …(then it talks about my sparse bundle) could not be accessed (error -1)." and then does not back up. It's done this once every few months for the past few years. I've found several quick fixes on the internet to solve it for a few months but then it starts again, usually after I restart the computer or for no good reason at all. I don't remember exactly what I've done but it's usually something involving making sure the name of the disk doesn't have an apostrophe in it or making sure the name of the Time Capsule matches the backup disk, I think. I'm kind of sick of doing this every time though, and I'd like to find the real reason why it's happening and top it once and for all. I found one answer that says that the Time Machine software isn't compatible and I should get a new model of Time Machine but I have a Mac and the Time Machine is a Mac so it seems crazy that they aren't compatible. And I did find a few answers that are very technical involving "mount the remote disk for read/ write access" but I really don't know what that means or how to do it. So if someone has advice in layman's terms, I'd really appreciate it. Thanks!
We don't see this error much nowadays.. since Yosemite it has much worse issues.
This is classic Pondini troubleshooting.
http://pondini.org/TM/C17.html
He has a fairly long list of links and you can go back and read through the whole C section.. as what you have already done is part of the fix.
http://pondini.org/TM/Troubleshooting.html
This particular fault was mainly on Lion and Mountain Lion.
How old and what model is your TC?
The fix.. as you call it might be to wipe the existing backup and start again.
After a backup has been in use for a while it seems to become increasingly flakey.. A start over can be very helpful.
If that also proves to be less than reliable.. are you using wireless?? If so it definitely introduces issues.
Time Machine is not the only game in town for backups. Indeed I strongly recommend to people now to supplement their TM backup with something like Carbon Copy Cloner.. especially if you can do a clone backup to a USB drive as that can then be used to boot the computer if anything goes wrong.
Consider other backups.. as TM may just be too complex for its own good. -
i cannot able able to start my macbook and then i started my mac in a recovery mode now mac os X utility window opens with 4 options 1. Restore From Time Machine Backup 2. Reinstall Mac OSX 3. Get Help Online 4. Disk Utility if i try to restore my mac with time machine no option appears if i reinstall from Mac OSX error comes and cannot able to recover from disk utility please help how can i reinstall mac OSX
Guitar21,
your MacBook Pro has booted into its Recovery mode. From the OS X Utilities menu, select Disk Utility. On the left-hand side of the Disk Utility window, select your internal disk’s boot partition (typically called “Macintosh HD”). On the right-hand side, press the Verify Disk button if it’s not greyed out; if it is greyed out, or if it reports that errors were found, press the Repair Disk button. Once the verification/repair is completed, exit Disk Utility and select Restart from the Apple menu to restart in normal mode. Does it get to the login screen now? -
How to restore OS from time machine to a non-booting Mac HD
My Mac HD has been playing up for some time and today it finally decided to not work at all. This was after I had installed 10.7.3 yesterday. I booted from my OS Leopard CD and installed it on my second HD which is usually used for data storage. I did try to restore the Mac HD from my Time Machine backup but I kept getting errors and the computer (MacPro early 2008 model - 6gb ram, 300gb HD) kept rebooting.
So the computer now boots from the second HD and I have repaired the Mac HD and verified it but it still will not boot. How can I use Time Machine to restore the system to the now non-booting Mac HD? When I try, it wants to do a backup of the new booting second HD which doesn't have all of my apps, docs etc (which are all on the Mac HD still).
ThanksOn the second HD, I'm using 10.5.8 (couldn't find my Snow Leopard disk) while the corrupted Mac HD had the latest 10.7.3. I did try migration assistant but it didn't work, I guess because the 2 operating systems are different. I will spend time today to try and find my Snow disk and upgrade and then upgrade again to my download version of Lion - on the second HD. When I look at the Mac HD it appears to be intact (that is, all files seem to be there) so I don't know why it can't boot unless on one of my migration attempts, something has gone awry. I still have Apple Care on the machine and have put in a service request so will see what happens from there.
Thanks for the help.
Cathie -
I have been using time machine to back up my Mac Book Pro 3.1 to my Time Capsule. Now the Time machine hangs up on "calculating time remaining".
Mac Book Pro - 3.1-15-inch 2.4/2.2GHz), Processor 2.2 GHz Intel Core 2 Duo
Operating system : OS X 10.10.1
Time Machine Version 1.3, Copyright 2007-2014 Apple Inc., Modified Tuesday, September 9, 2014 at 6:03 PM
Time Capsule: 500 GB C 2007
This Time Machine software worked satisfactory until Monday Nov, 10 2014 and I have backups until that time. For several years, the software deleted the oldest back up to save the latest one. This is acceptable to me as I have off site storage that is updated every 3 months. How do I get Time machine working again?I have spent a couple of days trying to respond to Linc Davis. Finally I figured it out . The following is a copy of data from my console from the initiation of a time machine backup until it gets stuck trying to calculate the time remaining. There is no indication that anything starts saving. I copied about 3 minutes of data. This is probably way too much data, but I do not know what is relevant.
Thanks for the help,
calcool
12/22/14 3:16:54.655 PM com.apple.backupd[551]: Starting manual backup
12/22/14 3:16:55.057 PM com.apple.backupd[551]: Attempting to mount network destination URL: afp://”name”%20”lastname”@Home%20Network%20Time%20Capsule._afpovertcp._tcp.loca l./Time%20Capsule
12/22/14 3:16:57.262 PM mds[33]: (Volume.Normal:2464) volume:0x7fed5ab54000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Time Capsule
12/22/14 3:16:57.565 PM com.apple.backupd[551]: Mounted network destination at mount point: /Volumes/Time Capsule using URL: afp://”name”%20”lastname”@Home%20Network%20Time%20Capsule._afpovertcp._tcp.loca l./Time%20Capsule
12/22/14 3:17:08.000 PM kernel[0]: hfs: mounted Backup of “name” “lastname”’s MacBook Pro on device disk3s2
12/22/14 3:17:09.625 PM com.apple.backupd[551]: Disk image /Volumes/Time Capsule/”name” “lastname”’s MacBook Pro (2).sparsebundle mounted at: /Volumes/Backup of “name” “lastname”’s MacBook Pro
12/22/14 3:17:11.112 PM com.apple.backupd[551]: Backing up to /dev/disk3s2: /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb
12/22/14 3:17:24.931 PM “name”[593]: audit warning: soft /var/audit
12/22/14 3:17:24.944 PM “name”[594]: audit warning: allsoft
12/22/14 3:17:24.958 PM “name”[596]: audit warning: closefile /var/audit/20141222201654.20141222201724
12/22/14 3:17:26.544 PM com.apple.backupd[551]: Event store UUIDs don't match for volume: Macintosh HD
12/22/14 3:17:34.767 PM com.apple.backupd[551]: Deep event scan at path:/ reason:must scan subdirs|new event db|
12/22/14 3:17:34.768 PM com.apple.backupd[551]: Reading cached event database from: /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb/”name” “lastname”’s MacBook Pro (2)/2014-12-22-151726.inProgress/F85FEA51-E137-471A-84DA-A2C00E4ECB42/.1BEF88C6 -20C3-3DDC-AE30-05EAB2AFCC15.eventdb
12/22/14 3:17:38.115 PM com.apple.backupd[551]: Using cached disk scan
12/22/14 3:17:39.114 PM com.apple.backupd[551]: Saved event cache at /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb/”name” “lastname”’s MacBook Pro (2)/2014-12-22-151726.inProgress/5BC46A53-25E8-4C4A-8947-AFB221D1FA0C/.1BEF88C6 -20C3-3DDC-AE30-05EAB2AFCC15.eventdb
12/22/14 3:17:39.355 PM com.apple.backupd[551]: Not using file event preflight for Macintosh HD
12/22/14 3:19:14.782 PM CoreServicesUIAgent[294]: unexpected message <OS_xpc_error: <error: 0x7fff77befc60> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff77beff70> { length = 18, contents = "Connection invalid" }
}>
12/22/14 3:20:15.207 PM locationd[182]: Location icon should now be in state 'Active'
12/22/14 3:20:17.267 PM locationd[182]: Location icon should now be in state 'Inactive'
12/22/14 3:20:17.884 PM locationd[182]: Location icon should now be in state 'Active'
12/22/14 3:20:18.483 PM sandboxd[296]: ([310]) com.apple.metada(310) deny mach-lookup com.apple.cfnetwork.cfnetworkagent
12/22/14 3:20:21.646 PM com.apple.metadata.SpotlightNetHelper[310]: [SLSUGGESTIONS] Location managed failed with error Error Domain=kCLErrorDomain Code=0 "The operation couldn’t be completed. (kCLErrorDomain error 0.)"
12/22/14 3:20:23.892 PM WindowServer[143]: disable_update_timeout: UI updates were forcibly disabled by application "Spotlight" for over 1.00 seconds. Server has re-enabled them.
12/22/14 3:20:26.526 PM WindowServer[143]: common_reenable_update: UI updates were finally reenabled by application "Spotlight" after 3.63 seconds (server forcibly re-enabled them after 1.00 seconds)
12/22/14 3:20:28.298 PM sandboxd[296]: ([310]) com.apple.metada(310) deny mach-lookup com.apple.cfnetwork.cfnetworkagent
12/22/14 3:20:29.094 PM com.apple.xpc.launchd[1]: (com.apple.quicklook[599]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
12/22/14 3:20:30.670 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:30.670 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:32.294 PM com.apple.InputMethodKit.UserDictionary[600]: -[PFUbiquitySwitchboardEntryMetadata setUseLocalStorage:](808): CoreData: Ubiquity: “name”~00000000-0000-1000-8000-001B63947FCF:UserDictionary
Using local storage: 1
12/22/14 3:20:32.317 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:32.769 PM locationd[182]: Location icon should now be in state 'Inactive'
12/22/14 3:20:34.580 PM Console[601]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
12/22/14 3:20:35.540 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
12/22/14 3:20:36.388 PM com.apple.xpc.launchd[1]: (com.apple.auditd[604]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd
12/22/14 3:20:36.693 PM “name”[608]: audit warning: soft /var/audit
12/22/14 3:20:36.718 PM “name”[607]: audit warning: allsoft
12/22/14 3:20:37.045 PM “name”[610]: audit warning: closefile /var/audit/20141222201724.20141222202036
12/22/14 3:20:37.438 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:42.437 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.437 PM QuickLookSatellite[611]: Invalid Connection ID 0
12/22/14 3:20:42.477 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.477 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.612 PM QuickLookSatellite[611]: [QL] No sandbox token for request <QLThumbnailRequest stackshot.log>, it will probably fail
12/22/14 3:20:42.613 PM QuickLookSatellite[611]: [QL] No sandbox token for thumbnail request file:///Library/Logs/stackshot.log, it will probably fail
12/22/14 3:20:42.615 PM QuickLookSatellite[611]: [QL] No sandbox token for request <QLThumbnailRequest stackshot-syms.log>, it will probably fail
12/22/14 3:20:42.615 PM QuickLookSatellite[611]: [QL] No sandbox token for thumbnail request file:///Library/Logs/stackshot-syms.log, it will probably fail -
"Time Machine can't back up - sparsebundle error 1" question
Hi,
I'm getting the "Time Machine can't back up - sparsebundle error #1" message, and am trying to see if the fix posted below is the answer:
http://support.apple.com/kb/TS2048
So, when I installed Time Capsule, I gave it a password ("network password").
Fairly recently, I renamed the Airport. Now the Airport disk password and Airport base station password are the same as the network password, and the Airport network password is different.
Is this what the Apple support message I referenced is getting at? Are these passwords supposed to be the same... ???
Thanks for any help,
reluctantuserI'm not sure what you mean by "We also used the Time capsule as a hard drive for backing up." after you've already mentioned that you use Time Machine to back up three Macs to the Time Capsule.
Check this Web page for advice on the space issue. -
Time Machine not configured / won't open / but it runs?
I'd appreciate some assistance troubleshooting a Time Machine issue.
I recently purchased a 2TB Time Capsule and set it up on my home network. I have set Time Machine up using it to back up 2 out of 3 MacBook Pros with no issues.
On the third MacBook, the Time Machine setup appears to work just fine (I have selected the Time Capsule disk, it has done the first full backup and periodic incremental backups). However, I have the following problems:
I cannot open the Time Machine application. Clicking on the App causes absolutely nothing to happen. No error. No windows. Nothing.
The icon in the menu bar is greyed out and gives no indication of backups in progress (no spinning clock like the other macs). Clicking on it reveals the top, greyed out menu choice that says "Time Machine not configured". (I can open time machine preferences and observe status from within that window.)
I have searched this and other sites for solutions. I have done steps A4 and E4 from this site (repeatedly) with no success.I'd appreciate some assistance troubleshooting a Time Machine issue.
I recently purchased a 2TB Time Capsule and set it up on my home network. I have set Time Machine up using it to back up 2 out of 3 MacBook Pros with no issues.
On the third MacBook, the Time Machine setup appears to work just fine (I have selected the Time Capsule disk, it has done the first full backup and periodic incremental backups). However, I have the following problems:
I cannot open the Time Machine application. Clicking on the App causes absolutely nothing to happen. No error. No windows. Nothing.
The icon in the menu bar is greyed out and gives no indication of backups in progress (no spinning clock like the other macs). Clicking on it reveals the top, greyed out menu choice that says "Time Machine not configured". (I can open time machine preferences and observe status from within that window.)
I have searched this and other sites for solutions. I have done steps A4 and E4 from this site (repeatedly) with no success. -
Time Machine not recognizing full space available on NAS.
I recently purchsed and set up an Iomega Storcenter ix4-200d NAS with Time Machine support. The NAS has 8 TB storage total, with ~4.6 TB available.
I have TIme Machine support turned on in the Storcenter, assigned to a folder called "Time-Machine." In my OSX Time Machine preferences, I select the "Time-Machine" folder on my NAS as the back-up disk, and my Mac connects to it just fine.
The challenge is Time Machine returns an error saying there isn't enough space on the backup disk to complete the backup.
For some reason, Time Machine is only recognizing 536.36 GB of space available on the backup disk, even though there are ~4.6 TB available. I tried manually moving my iTunes media folder (~700 GB) to the "Time-Machine" folder on my NAS to see if the Iomega NAS was arbitrarily setting a max size to a Time Machine folder. I was able to manually move just under 1 TB of data to the same "Time-Machine" folder that Time Machine says only has 536.36 GB of space.
I tried deleting the Time-Machine store on my NAS, turning Time Machine support off, then turning it back off and creating a new "Time-Machine" folder. I did this several times and still get the same behavior.
I even tried running Time Machine piecemeal, excluding larger folders at first and running a back-up, to see if maybe Time Machine wasn't liking that large of an initial backup. This worked, and then I gradually removed some exclusions and ran back-ups again, so each back-up size was never more than 200 GBs or so. However, after several back-ups, I received the same error message saying there wasn't enough space on the backup disk when the total sparsbundle size reached 536.36 GBs.
Since I can manually move more than 536.36 GB of data to the backup disk, I'm guessing it must be something with Time Machine not recognizing the full space available on the NAS.
Any ideas? Has anyone seen this before?Hello,
not that it helps, but I see the same on the exact same configuration. My message is also about not having enough space, ip-to exactly the same amount of room being available (only 536.36 GB available)?
I tried everything, including a full reset of the StorCenter, but to no avail. The timemachine backup used to work, however I thought that this was just because it didn't exceed the limit of one physical disk in the StorCenter (I've got 4 x 1 TB).
What is strange is that the original author has 2TB disks and still has the same problem? So it likely isn't related to the physical disk size. It seems like the maximum backup can only be 536.36 GB ?? -
For the last month or so, every time I download anything I get an error message stating "........could not open ...... .dmg because it is either not a supported file type or because the file has been damaged...." I do not know what to do to fix this issue. Any ideas?
hmmm.... try this
basic troubleshooting:
Repair Disk Permissions http://support.apple.com/kb/PH5821
Repair Disk http://support.apple.com/kb/ht1782
reset ACLs http://osxdaily.com/2011/11/15/repair-user-permissions-in-mac-os-x-lion/
Maybe you are looking for
-
When I start the computer I try to open the safari but it start to reaload over and over, so I turn off the Wi-Fi and after turn on, then start Safari again, and it starts to work again. I believe that is not a problem of RAM because I put 16GB of RA
-
Email sent but not received by individuals
Hello, I am facing an issue in email distribution through WF. Emails are generated and can be seen in SAP basis inbox. (i.e. you can see the email address/user ids in To field or Cc field). Few of the users are getting email notification in their inb
-
Why is the Apple contacts application so mediocre?
The app is great for adding and keeping new contacts but absolutely teribble for helping you to manage them and stay connected. Something as simple as creating a group is nigh impossible on the stock app. I'm thinking that this is a phone primarily a
-
Loading flat idoc via report RSEINB00 into integration server fails
Hi, we have PI/700. We get idocs (in flat format NOT XML) via filesystem from an external partner. Now I try to load these idocs with the report RSEINB00 into my integration server. My problem is, that the report says that the sender port + client(of
-
"backup failed while creating the backup folder"
Time machine fails backup. Backup volume is a 1TB USB External. Message appears: "backup failed while creating the backup folder" However whwn enter time machine is entered, there is displayed many-many backup depictions.