Time Capsule + Spotlight

Hello guys, Ive searched the forums for an answer, but every thread just ends with a suggestion thats never verified.
So, heres my problem:
My Spotlight wont recognize my Time Capsule.
What do I do?
It appears that Apple simply prevents Spotlight from recognizing the Time Capsule to prevent Spotlight from re-indexing the Time Capsule every time it is connected. So, we're left with a backup storage device with no search feature.

Time Machine visual search only sorry.

Similar Messages

  • How can I search the time capsule using spotlight or time machine?

    Every time I try to use spotlight in finder, to find anything on the time capsule, spotlight automatically turns to the mac.
    While using timemachine the connection to the time machine greys out.
    How can I use these options, or different options to search the time capsule?

    I've been looking for the star wars gui, but I only ended up watching scifi movies all night.
    LOL..
    Oh well it is new year.. seems as good a use of time as any.
    Click on the time machine icon in the dock.. that opens finder inside the backup.
    http://www.dummies.com/how-to/content/using-time-machine-to-find-old-files-on-yo ur-mac.html

  • Spotlight indexing of Time Capsule - feature or bug?

    I understand why backups are indexed: the ability to use Spotlight from within Time Machine is a fantastic feature.  But the method by which this index is created does not make sense where a Time Capsule is in use (or indeed most networked storage, but since many configurations are officially unsupported let's just keep this discussion focused on the officially approved one!).
    Typically (from my sample size of 1), a complete system backup is of the order of 100GB; however, after the initial backup is complete, Time Machine only needs to copy modified files to the backup drive, which can lead to very small and fast subsequent backups: unchanged files are created in-situ with a hardlink to the existing copy on the backup drive.
    A problem arises when, after a backup completes, Spotlight attempts to index the changes to the backup drive: it appears that it inspects every unindexed file (involves transfer to the local machine) including such unmodified/hardlinked files.  This therefore gives rise to a situation where a backup that writes only a few kilobytes to the backup drive results in Spotlight reading hundreds of gigabytes from that drive.
    Even with a throughput of 100Mbps, this would take close to an hour and a half (in reality, especially over wireless networks, it takes many hours); meanwhile Time Machine reaches its next scheduled backup and cannot proceed until Spotlight has finished indexing.
    Altogether, this appears to render Time Capsules useless for system backup (unless one is connected via gigabit ethernet, which is neither a requisite nor a desirable constraint).  One does not need to look far to see how many users this issue is affecting.
    In previous versions of OS X, one could workaround this issue by disabling Spotlight indexing of the backup volume; however, since Lion (or Snow Leopard?), this is no longer possible.
    To my mind, the design is flawed - some might call it a "bug": there should be a more efficient method of indexing drives, especially networked ones (ideally avoiding the redundancy of reindexing hardlinked files).  At worst, Time Machine could provide to Spotlight all the metadata it requires for the entire backup: thus avoiding the need for Spotlight to read such files from the backup volume.
    ...or have I misunderstood something?

    nickety wrote:
    I understand why backups are indexed: the ability to use Spotlight from within Time Machine is a fantastic feature.
    That's not the reason; Time Machine requires the indexing in order to work, especially for the "Star Wars" display.
    Altogether, this appears to render Time Capsules useless for system backup
    That's not normal; you have something else wrong, possibly a corrupt index.  See the pink box in #D2 of Time Machine - Troubleshooting.
    In previous versions of OS X, one could workaround this issue by disabling Spotlight indexing of the backup volume
    Not really.  The backups were still indexed;  you just didn't get a message.  See the note in item 2 here: http://docs.info.apple.com/article.html?path=Mac/10.6/en/8991.html

  • Spotlight does not find files on Time Capsule disk

    I have the 2TB time capsule configured with a DATA and FIL disks.  The DATA is used for the Time Machine backups.  The FIL disk is used as a NAS (Network Access Storage) disk.  The FIL disk works as advertised except Spotlight.  When I mount the FIL as a shared disk and go into Spotlight and seach for a file by the filename, nothing happens.  I spent hours on this.  I seached Google and found nothing.  I also tried mounting the disk as a SMB.  This works partially when I alter the search criteria to seach only "Shared".  But it only works within the folder.  It does not search the entire tree.  Any suggestions will be greatly appreciated.  Thanks

    By default, network drive is not indexed.
    See here for the default list of folders that Spotlight will search:
    http://docs.info.apple.com/article.html?artnum=301533
    You can manually turn on spotlight on a specific volume by using Terminal and enter:
    sudo mdutil -i on /Volumes/X
    (where "X" is the name of the network volume.)
    If the index is corrupted, and you want to rebuild it, enter:
    sudo mdutil -E /Volumes/X

  • Disabling spotlight for Time Capsule

    Hi,
    I need to disable (please do not ask the reason, I just need) indexing for backups on the Time Capsule. I know that the help on Spotlight says Time Machine needs spotlight bla bla... and, it can't disable indexing for this. I just don't beleive it, because when I disable spotlight for good with the following command:
    sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
    time machine continues to function just fine. Everything seems perfect as far as the time machine is concerned. However, other apps (like Mail) which relies on spotlight for searching forced me to reenable the spotlight (with the following command) with tears in my eyes:
    sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
    So, please help me to find a workaround for disabling spotlight/indexing just for time machine.
    By the way I tried the following methods without any success, so do not bother to recommend them:
    1) Including TM volume and/or Backup directory in the TM volume to the privacy list of Spotlight
    2) sudo mdutil -i off /Volumes/VolumeName and sudo mdutil -E /VolumeName
    3) Erased .Spotlight-V100
    4) touch .metadata_never_index in the root and/ot Backup directory of time machine volume
    5) creating a dummy file named  .Spotlight-V100
    [rebooted in all instances...]
    PLEASE HELP

    So, you've read through the FAQs and couldn't find a solution, eh? Sorry, but I don't use TM nor do I muck with CLI commands that I don't fully comprehend. You'll have to wait for someone more knowledgeable to pop in.

  • Time Capsule backup gets stuck, Spotlight related?

    This just started yesterday: my Time Capsule backs up as normal, and seems to be finished, but doesn't quite make it. The Time Machine icon in my menu bar stops spinning and even says the backup has completed, but the backup icon on my desktop does not eject, and I can hear the drive still spinning. I downloaded the Time Machine Buddy widget on the advice of other posts here, and have retrieved the following message from there: "Backup completed successfully.
    Waiting for Spotlight to finish indexing /Volumes/Backup of MacBook/Backups.backupdb"
    This repeats until I manually eject the backup icon from the desktop. I tried exempting the Time Capsule from Spoltlight searches in System Preferences, and this seemed to do the trick. After doing this, the backup will complete successfully, the icon will eject, and the drive stops spinning, but I would like to include my Time Capsule in my Spotlight searches, so any ideas? Thanks.

    Thanks for the reply. Tried the repair, it completed, but didn't report anything, is this normal? Here's a copy of the widget log form my most recent backup, this one is probably a bit longer than usual because the back was verified:
    Starting standard backup
    Attempting to mount network destination using URL: afp://Stephen%20Agusta@Time%20Capsule%20b724f1.afpovertcp.tcp.local/Stephen%20Agusta's%20Time%20Caps
    Mounted network destination using URL: afp://Stephen%20Agusta@Time%20Capsule%20b724f1.afpovertcp.tcp.local/Stephen%20Agusta's%20Time%20Caps
    Running backup verification
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Backup verification passed!
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Stephen Agusta's Time Caps-1/Stephen Agusta’s MacBook_002332bf0274.sparsebundle mounted at: /Volumes/Backup of Stephen Agusta’s MacBook
    Backing up to: /Volumes/Backup of Stephen Agusta’s MacBook/Backups.backupdb
    No pre-backup thinning needed: 2.87 GB requested (including padding), 372.13 GB available
    Copied 42457 files (1.5 GB) from volume Macintosh HD.
    No pre-backup thinning needed: 214.1 MB requested (including padding), 370.72 GB available
    Copied 965 files (2 KB) from volume Macintosh HD.
    Starting post-backup thinning
    Deleted backup /Volumes/Backup of Stephen Agusta’s MacBook/Backups.backupdb/Stephen Agusta’s MacBook/2010-03-04-192143: 370.72 GB now available
    Deleted backup /Volumes/Backup of Stephen Agusta’s MacBook/Backups.backupdb/Stephen Agusta’s MacBook/2010-03-03-182013: 370.72 GB now available
    Deleted backup /Volumes/Backup of Stephen Agusta’s MacBook/Backups.backupdb/Stephen Agusta’s MacBook/2010-03-31-232041: 370.72 GB now available
    Deleted backup /Volumes/Backup of Stephen Agusta’s MacBook/Backups.backupdb/Stephen Agusta’s MacBook/2010-03-31-221502: 370.72 GB now available
    Deleted backup /Volumes/Backup of Stephen Agusta’s MacBook/Backups.backupdb/Stephen Agusta’s MacBook/2010-03-31-215517: 370.72 GB now available
    Post-back up thinning complete: 5 expired backups removed
    Backup completed successfully.
    Waiting for Spotlight to finish indexing /Volumes/Backup of Stephen Agusta’s MacBook/Backups.backupdb

  • Spotlight and Time Capsule

    Does spotlight work on Time capsule? If it does, can I turn it off so it doesn't index TC?

    When you use Time Machine spotlight within Time Machine searches the Time Capsule Disk.
    Not sure if you could turn it off, without turning off spotlight on your Mac as well. I was able to add my Time Capsule folder to my Spotlight Privacy list, but I didn't want to do this. System Prefs Spotlight privacy list does allow you to select the folder on TC where backups are stored.

  • Time Capsule and Spotlight

    Hello, I have question about Time Capsule's Spotlight searching. The problem is that Spotlight doesn't want to find anything on my Time Capsule. Interesting, 'cause indexing works but after it happened nothing. Any idea?

    A normal search will not show up material in a TM backup.. you must be using TM to search for info and apparently Spotlight is necessary to that working.
    See some of the posts under "More Like This" on the right column.
    eg https://discussions.apple.com/message/11398191#11398191
    A bit old but still probably correct. Most of what Pondini says is gospel.

  • Time capsule and spotlight - yes or no?

    When the Time Capsule is mounted, spotlight starts indexing the disk image. However the file has become very big together with all the backups, so the indexing actually never ends before the backup is finished or before I turn off the macbook at night. Is there a reason why spotlight should index the time capsule? If not then maybe it is better to turn off spotlight for time capsule which may accelerate the overall backup time in the future.

    A normal search will not show up material in a TM backup.. you must be using TM to search for info and apparently Spotlight is necessary to that working.
    See some of the posts under "More Like This" on the right column.
    eg https://discussions.apple.com/message/11398191#11398191
    A bit old but still probably correct. Most of what Pondini says is gospel.

  • Question about Time Capsule and Spotlight

    I have a simple question about using Time Capsule and Spotlight. Is everything that goes on to Time Capsule indexed into Spotlight? It would appear so but when I search for something (that is still on my hard drive and also backed up to Spotlight) only the local copy appears. Would it be that it finds the closest copy and if that were not there it would point to the Time Capsule copy? Thanks in advance for clarifying this for me.

    The automatic setup in the airport utility has changed something.
    Is the line down to the TC from the express dotted.. in other words is wireless??
    Funny stuff happens.
    Please post the screenshots of the 3 pages from the airport utility setup for both airport express and TC..
    Make sure wireless is set to off in the express.
    Both should be set to dhcp on the internet tab and both set to off bridge mode on the network tab.
    So for example the bridge on the network tab.
    The summary page can also be a help.
    There is a half summary page when you click the item in the airport utility.
    There is also a fully summary page, when you hold option key and double click the TC icon for example.

  • How do I get Spotlight to search a shared Time Capsule drive?

    I purchased a 2TB Time Capsule that I am storing all of my photos, videos, etc. on, but I've found that Spotlight does not index and search that drive. I have searched everywhere for a solution, but can't find one.  Does anyone have a solution to this?  It is not physically attached to my MacBook Air - I am accessing it wirelessly.
    Thank you for any help you can provide!

    OK, the Terminal is a the way that you access UNIX shell commands (the Mac command line interface). Instead of clicking on things you have to type the actual command into the "prompt" hit return, and then the shell executes the command. So you go to the Utilities folder and double click Terminal to launch it. Exactly what you see when it finishes launching will depend on how you have configured it, so it won't be exactly what I see, but there will be some words of encouragement and then the prompt, where you will type things:
    Last login: Tue Mar 20 14:06:01 on ttyp1
    Welcome to Darwin!
    -bash:~francine$
    The "$" is where you start typing, or you can copy and paste things in also. You would then type:
    sudo mdutil -i on /Volumes/YOURDRIVENAME/
    You must make sure everything you type is exactly as given, thus you may want to simply copy and paste this:
    sudo mdutil -i on /Volumes/
    and, making sure there is no space after that final "/" character, type the name of your drive exactly as it appears in Finder. If the name has any spaces in it be sure to surround it with quotes:
    sudo mdutil -i on /Volumes/"MY FAT DRIVE"/
    Then hit the Return key. You will be asked for your admin password, and given a little lecture (this is only delivered the first time you use a sudo command). The password you type is not echoed to the screen in anyway whatsoever, so type very carefully and when you finish hit the Return key again. You'll then get the notice that indexing is enabled. Type the word exit, hit Return, and then quit Terminal.
    Francine
    Francine
    Schwieder

  • Time capsule not backing up - spotlight doesn't stop indexing!

    I have asked Spotlight not to index the backup drive however it ignores this and continues to try and do so. However it continues to estimate index time without providing a time, and hence the backup never proceeds.
    Rebooting hasn't helped, and I'm even pluggintg the MBP into the TC via ethernet.
    Any ideas please?

    I'm having the same problem. Added the time capsule to the privacy list but this doesn't appear to prevent indexing. Basically every time time machine backup kicks off it indexes the time capsule, which is of no value to me. I believe this is a recent issue, but I can't say for certain what changed. Recent software update? Anyway, did you ever get to the bottom of it? My backups do complete, however it slows down the process and of course i can't use spotlight while its "estimating/completing" index of time capsule.

  • Time Capsule disabling Spotlight??

    I installed Time Capsule about a week ago on my iMac, and after taking about six days to index (and many problems), now that it's finally backed up, Spotlight isn't working properly.
    I can't exactly figure out what it is or isn't searching, but I know it is no longer finding items in my address book or calendar, and in many folders on my hard drive. In fact, I can't even use the spotlight in iCal to find items within the calendar itself.
    What the heck is going on? I've searched the forums, but have found no explanation or solution for this problem.
    Can anyone help?
    Thanks!

    So, you've read through the FAQs and couldn't find a solution, eh? Sorry, but I don't use TM nor do I muck with CLI commands that I don't fully comprehend. You'll have to wait for someone more knowledgeable to pop in.

  • Time Machine and Time Capsule - Failing with Network Problem

    My problems with TM/TC have been ongoing for a couple of months now and I am going round in circles - need help.
    This is the second post I have made, the first got lost in people suggesting the obvious - so I will try to be a little more specific if I can.
    I will detail the current state first - i.e. where I am now - after I will list what I have done so far to get to this point.
    Currently, my iMac (intel) is directly connected by Ethernet 1GB to the Time Capsule. The TC is then connected to a Netgear router which in turn is connected to Internet.
    I have no network problems at all - internet connection is fine. the Netgear Router has the latest firmware version and is working fine. The porblems i have are nothing to do with this.
    The time Capsule is in Bridge mode and getting a reserved dhcp IP address from the Netgear router.
    The Time Capsule has been fully reset - i.e. power cable out, hold the reset button, plug in power cable (spark, spark), hold reset button, fast blink for 20 seconds or so, light goes out, release button.
    I have re-applied the latest Time Capsule firmware.
    I have renamed the disk on the Time Capsule.
    I have renamed my iMac and deleted all the time capsule entries from Keychain.
    I have re-installed Mac OSX and re-updated to the latest 10.5.6 release.
    At the moment I have kicked off a backup with a lot of large files - like music folder, video folder etc excluded. I also have parallels and have excluded the disk image. I have 1 other 50GB disk image which is also excluded.
    I am expecting the first initial backup will complete successfully.
    I will then remove music and video from exclusions and allow them to backup. I am expecting this will complete no problem. (I do this because the upcoming problem will happen if I move away from the machine - and I dont want to sit there for 2 days).
    So up to this point TM and TC have performed flawlessly. The issue that follows started happening before the 10.5.6 update after backing up with no issues for months. At this point I will be able to use TM to browse the backup and restore files. I will be able to mount the sparse bundle and browse files. Spotlight reports no issues and indexes quickly.
    If I leave my machine after a successful backup and the hourly update kicks in it will fail with 'A Network problem' basically saying the backup has filed because of a network problem, but is not any more specific, logs show far too much to put the whole thing here, but the following is an excerpt
    Dec 23 05:19:49 MickMac /System/Library/CoreServices/backupd[1499]: Backup destination mounted at path: /Volumes/Backup
    Dec 23 05:19:50 MickMac hdiejectd[1519]: running
    Dec 23 05:19:51 MickMac kernel[0]: jnl: disk1s2: replay_journal: from: 28864512 to: 30084096 (joffset 0x1d0f000)
    Dec 23 05:21:49 MickMac kernel[0]: jnl: disk1s2: journal replay done.
    Dec 23 05:21:49 MickMac /System/Library/CoreServices/backupd[1499]: Disk image /Volumes/Backup/MickMac_001ec215ce76.sparsebundle mounted at: /Volumes/Backup of MickMac
    Dec 23 05:21:49 MickMac /System/Library/CoreServices/backupd[1499]: Backing up to: /Volumes/Backup of MickMac/Backups.backupdb
    Dec 23 05:21:49 MickMac com.apple.launchd[1] (com.apple.netauth.sysagent[1500]): Stray process with PGID equal to this dead job: PID 1503 PPID 1 check_afp
    Dec 23 05:21:55 MickMac fseventsd[38]: event logs in /Volumes/Backup of MickMac/.fseventsd out of sync with volume. destroying old logs. (3627 125 5482)
    Dec 23 05:27:33 MickMac /usr/sbin/ocspd[1539]: starting
    Dec 23 05:30:27 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 5 reqID 5400 flags 0x9 afpCmd 34 so 0x7e78cc0
    Dec 23 05:30:27 MickMac kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x7e78cc0
    Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Backup prevTrigger 0 currTrigger 1
    Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Backup
    Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Backup
    Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Backup
    Dec 23 05:30:27 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Backup
    Dec 23 05:31:26 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot -1 error 89 reqID 1 flags 0x9 afpCmd 0 so 0x7e78cc0
    Dec 23 05:31:26 MickMac KernelEventAgent[34]: tid 00000000 received VQ_DEAD event (32)
    Dec 23 05:31:26 MickMac KernelEventAgent[34]: tid 00000000 type 'afpfs', mounted on '/Volumes/Backup', from 'afp_0V1fqC1mgalO00mE1H0Pyetl-1.2d00000a', dead
    Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Open Session failed 57 /Volumes/Backup
    Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: max reconnect time reached 60 > 30 /Volumes/Backup
    Dec 23 05:31:26 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEAType IO] [ErrNo 5] [IOType Read] [PBlkNum 1248] [LBlkNum 155] [FSLogMsgID 501572642] [FSLogMsgOrder First]
    Dec 23 05:31:26 MickMac kernel[0]:
    Dec 23 05:31:26 MickMac fseventsd[38]: failed to unlink old log file /Volumes/Backup of MickMac/.fseventsd/0000000000ccb02b (Input/output error)
    Dec 23 05:31:26 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED)."
    It goes on and on and is repeated every hour. For each one I get an error message on screen saying backup failed due to a network error. However I have tried a manual download over the same period set at an extremely slow rate so that it was downloading during this time and it showed no errors. I.e. the network connection from imac, through TC to netgear and out to internet - and monitored this while time machine showed these errors (i.e. at the same time) and this showed no connection problems at all and completed succesfully.
    I know TM uses an internal address to do backups, but uses the same cable and network card to get the job done. I am simply removing the cable as a source of issue although I have also replaced this making no difference.
    Applecare are involved and have so far been sent 2 sets of logs and so far have not been able to find the cause. New TC is on its way to try that, although they think it is something on the imac that is causing this.
    Sleep mode is turned off although screen sleep is on. The tick is not in the box for putting hard drives to sleep whenever possible.
    Now, after this has happened, and back at the machine. I restart both imac and TC. Try running a backup, spotlight starts to re-index - i.e. will mount the backup volume and start the index process, gets to about 90% then fails - again excerpts from log
    "Dec 23 09:18:50 MickMac /System/Library/CoreServices/backupd[161]: Backing up to: /Volumes/Backup of MickMac/Backups.backupdb
    Dec 23 09:18:50 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/li ve.0.; needs recovery
    Dec 23 09:18:57 MickMac com.apple.launchd[67] (com.apple.netauth.useragent[147]): Stray process with PGID equal to this dead job: PID 152 PPID 1 check_afp
    Dec 23 09:19:48 MickMac mds[32]: (Error) Server: machmsgdispatch: (ipc/send) invalid destination port [msgh_id 14016]
    Dec 23 09:29:35 MickMac /usr/sbin/ocspd[197]: starting
    Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 11 reqID 3204 flags 0x9 afpCmd 60 so 0x8051b28
    Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP HoldPendingReqs: holding slot 12 reqID 3205 flags 0x9 afpCmd 34 so 0x8051b28
    Dec 23 09:42:48 MickMac kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x8051b28
    Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Backup prevTrigger 0 currTrigger 1
    Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Backup
    Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Backup
    Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Backup
    Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Backup
    Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Backup
    Dec 23 09:42:49 MickMac kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Backup
    Dec 23 09:42:49 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 11 error 35 reqID 3204 flags 0x19 afpCmd 60 so 0x8051b28
    Dec 23 09:42:49 MickMac kernel[0]: ASP_TCP CancelOneRequest: cancelling slot 12 error 35 reqID 3205 flags 0x19 afpCmd 34 so 0x8051b28"
    And later....
    Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x39 (UNDEFINED).
    Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 received VQ_DEAD event (32)
    Dec 23 09:45:49 MickMac kernel[0]:
    Dec 23 09:45:49: --- last message repeated 1 time ---
    Dec 23 09:45:49 MickMac kernel[0]: hfs_clonefile: cluster_read failed - 5
    Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 type 'afpfs', mounted on '/Volumes/Backup', from 'afp_0V1fqC1mgalO00mE1H0Pyetl-1.2d000005', dead
    Dec 23 09:45:49 MickMac kernel[0]: HFS resolvelink: can't find iNode791959
    Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x39 (UNDEFINED).
    Dec 23 09:45:49 MickMac kernel[0]: ore-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431/store.db] [FSLogMsgID 1580919258] [FSLogMsgOrder Last]
    Dec 23 09:45:49 MickMac KernelEventAgent[34]: tid 00000000 found 1 filesystem(s) with problem(s)
    Dec 23 09:45:49 MickMac kernel[0]: jnl: disk1s2: dojnlio: strategy err 0x5
    Dec 23 09:45:49 MickMac kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 49664 bytes to the journal!
    Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
    Dec 23 09:45:49 MickMac kernel[0]:
    Dec 23 09:45:49: --- last message repeated 1 time ---
    Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexSDB in dbcheckdatastore:store.db : dbgetdatastore: ERR: could not read 4096 bytes
    Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
    Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexCI in CIMetaInfoSync:write err: 5
    Dec 23 09:45:49 MickMac kernel[0]:
    Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431)(E rror) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/6CC2B046-5E28-4179-96B7-9DFF9F7EE431
    Dec 23 09:45:49 MickMac kernel[0]:
    Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexSDB in adddirtychunk:/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/st ore.db : ERR: Can't write DST header (Input/output error)
    Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
    Dec 23 09:45:49 MickMac kernel[0]:
    Dec 23 09:45:49: --- last message repeated 1 time ---
    Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
    Dec 23 09:45:49 MickMac kernel[0]:
    Dec 23 09:45:49: --- last message repeated 1 time ---
    Dec 23 09:45:49 MickMac kernel[0]: disk1s2: 0x14 (UNDEFINED).
    Dec 23 09:45:49 MickMac kernel[0]:
    Dec 23 09:45:49: --- last message repeated 1 time ---
    Dec 23 09:45:49 MickMac mds[32]: (/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE)(E rror) IndexSDB in dbflushdatastore:/Volumes/Backup of MickMac/.Spotlight-V100/Store-V1/Stores/266E0E5F-E002-4EB5-A049-9B50582510FE/st ore.db : dbsyncdatastore: write-errors flushing cache/writing map.
    Am I the only one having these problems? any help from anybody please...

    Got the same problem with a 3 months old TC.
    The replacement TC, does it work now flawless?

  • Time Machine Won't Back Up to Time Capsule

    I have an iMac 11.2 which was working really well with Time Machine and a 500GB Time Capsule when I was using Moutain Lion.  I then Update my machine to Mavericks (10.9.1) and my problems started.  It wiped everything in my backup and tried to start a new one.  So far it has stalled either in the prep phase or has managed start but is extremely slow - it took over a week to back up 300GB, but could not complete the last 50GB because it kept getting a sparsefile error.  I have tried the following in isolation or in combination :-
    1/  Deleting the plist file
    2/  Running disk utility on the sparse file - no issues found
    3/  Backing up in safe mode
    4/  Deleting the hard drive content and starting again
    5/  Backing up through my LAN rather than WAN - can't even find the drive.
    I have thought about buying a new Time Capsule, but I cannot be sure the problem lies with my current one.  If anybody has any ideas they would be gratefully received.  If not then I can only hope Apple read this and they do something to restore my faith in their operating system.
    Many thanks

    Before you do anything else, if you now have no current backup, back up all data to a USB hard drive.
    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.

Maybe you are looking for