Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Time Capsule/ Endless Preparing - no backup

I've seen similar threads and I believe that I've tried all of their fixes.

I'm seeing the following errors in the console:
Aug 7 10:30:34 HomeMac /System/Library/CoreServices/backupd[191]: Waiting for index to be ready (909 > 0)
Aug 7 10:30:34 HomeMac mds[33]: (/Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/F9F6764C-F1D9-46D4-804E-4CFDC556F1E8)(E rror) IndexCI in ContentIndexOpenBulk:No index
Aug 7 10:30:34 HomeMac mds[33]: (/Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/F9F6764C-F1D9-46D4-804E-4CFDC556F1E8)(E rror) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/F9F6764C-F1D9-46D4-804E-4CFDC556F1E8
Aug 7 10:30:34 HomeMac mds[33]: (/Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/FB0AF823-52BC-455D-9BE4-5267CC68CEB9)(E rror) IndexCI in open indexfile:bad file size: 16, min size 4096, 0.indexHead
Aug 7 10:30:34 HomeMac mds[33]: (/Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/FB0AF823-52BC-455D-9BE4-5267CC68CEB9)(E rror) IndexCI in ContentIndexOpenBulk:0.indexHead invalid, will try to recover
Aug 7 10:31:00 HomeMac com.apple.launchd[1] (0x109db0.cron[397]): Could not setup Mach task special port 9: (os/kern) no access
Aug 7 10:31:04 HomeMac /System/Library/CoreServices/backupd[191]: Waiting for index to be ready (909 > 0)
Aug 7 10:31:04 HomeMac mds[33]: (/Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/F9F6764C-F1D9-46D4-804E-4CFDC556F1E8)(E rror) IndexCI in ContentIndexOpenBulk:No index
Aug 7 10:31:04 HomeMac mds[33]: (/Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/F9F6764C-F1D9-46D4-804E-4CFDC556F1E8)(E rror) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/F9F6764C-F1D9-46D4-804E-4CFDC556F1E8
Aug 7 10:31:04 HomeMac mds[33]: (/Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/FB0AF823-52BC-455D-9BE4-5267CC68CEB9)(E rror) IndexCI in open indexfile:bad file size: 16, min size 4096, 0.indexHead
Aug 7 10:31:04 HomeMac mds[33]: (/Volumes/Backup of HomeMac/.Spotlight-V100/Store-V1/Stores/FB0AF823-52BC-455D-9BE4-5267CC68CEB9)(E rror) IndexCI in ContentIndexOpenBulk:0.indexHead invalid, will try to recover

Things that I've tried:
- Erase disk both with "quick" and "zero out" options.
- Restore defaults
- Roll back firmware to 7.4.1
- changed time machine to use different disk, successful backup to that disk, set back to time capsule.
- tried to add "Backup of HomeMac" and "TimeCapsule" to the spotlight privacy settings. These settings are lost at reboot.... and if I don't reboot it says that it fails to mount "Backup of HomeMac". Likely because it is already mounted?
- I have 2 macs that backup to this time capsule. It has worked for several months. Now doesn't work for either. One is running 10.5.8.. the other is running 10.5.7.
- Tried to use DiskUtility on the sparsebundle. It looks clean after a reboot, but then timemachine won't run... possibly because it is already mounted?? It looks corrupted in DiskUtility after I quit the time machine backup. In any case, I keep "erasing" the time capsule hard drive, so if there is a problem with the bundle, it is created from scratch and still has the problem.
- verify permissions on my Mac's main HD.
- changed the name of the TimeCapsule.


I think that is all. I get the same error every time. I don't know if this is a spotlight issue or a time capsule issue. It does affect 2 macs with different OS versions (10.5.7, 10.5.8), so I assume that it is the time capsule.

One other possibly unrelated issue: When I used to run time machine the backup volume would be mounted with my name. Now it just says the network name. (i.e. it used to say something like "Backup of John Smith's Mac" and now it says "Backup of HomeMac") I assume this is unrelated, but I figured I would mention that too.

Anyone have any ideas?

Thanks.

Time Capsule - 1G, Mac OS X (10.5.8), Mac Pro (2008), Macbook Air 2008

Posted on Aug 7, 2009 8:49 AM

Reply
210 replies

Aug 8, 2009 10:48 AM in response to bjm103

Same issues here 😟
Copied the sparsebundle on my usb harddisc, works fine directly.
deletet the capsule hard disc.
Tried a new Backup, but always have this reply in the console:

08.08.09 19:12:35 [0x0-0xa00a0].com.apple.systempreferences[2189] chown: /Volumes/TC-1/.001XXXXXXX: Operation not permitted

I have no idea, tried chown (didnt work with the sparsebundle, same reply like in the console above) and chmod. The apple service guy had no clue and obviously not known issue at apple (german dep) so far.

10.5.8. changed something with afp. maybe that could be a point?

****, I have this expensive machine there and its useless (can use it as a server, but thats pretty expensive clunker..need cash for clunker as well...

Cheers
Jan

Aug 8, 2009 10:49 AM in response to JohanDA

I am having the problems described above with my MacBook OSX 10.5.7 and iMac OSX 10.5.8 connected to the same Time Capsule. The backups were working smoothly until two days ago when I started to get all kinds of error messages. I erased the disk, reset the capsule, changed the name of the disk, repaired permissions, selected the disk in time machine preferences, etc. according to suggestions on several forums. Luckily I also back up to an Mozy online.
I checked the system log files and the message says "Tried to create index when index already existed." Okay, but now what?
I'm thinking of buying an external hard drive to connect to the Time Capsule. I'll keep checking this thread to see if someone comes up with something that will work for me.

Aug 8, 2009 6:50 PM in response to JohanDA

A couple of thoughts. 1) Is anyone seeing this behavior (funny index messages about duplicate indexes, etc.) without Mozy installed? I have it and see some people have. 2) Does everyone find that the Backup of ... disk fails to disconnect/unmount after Time Machine tries the backup? Just wanting to see if we can identify common software/behaviors.

John
PS: Looks like 10.5.8 isn't the only factor. Also confirm if you see the issue with 10.5.7. It appears some folks are seeing the error with other OSes. Also, I have two Macs with 10.5.8 working with the Time Capsule (backups back to 10.5.7 and even 10.5.6). My MacBookPro has the problem and it started it seems when my backup got corrupted when my machine hung. Now I cannot get a good backup even after deleting the old sparseimage.

Aug 8, 2009 7:41 PM in response to John Vestal1

Works like a charm without Mozy installed 😉 Thanks John!

Mozy did update to version 1.4.something few days ago and after I uninstalled it Time Machine started to backup to Time Capsule with very short preparing time.

Looks like it's time to hit the Mozy forums!

EDIT: Yep, re-installed mozy-1 4_11-6770 and immediately Time Machine was hosed with same log markings. Un-installed Mozy and Time Machine works!

Message was edited by: Ocid

Aug 8, 2009 8:45 PM in response to bjm103

Glad I found this thread! I've been receiving the same error when backing up to my Time Capsule. After examining the console logs I tried just about everything I could think of including wiping my time capsule. Searched forums for related problems and tried all of the recommended solutions. No matter what I tried I could not get the Time Machine to back up to the Time Capsule (endless preparing). However, Time Machine did successfully backup to a Firewire drive.

Whoever pointed out Mozy, thanks! That was it. I had 1.4.0 installed and upgraded to 1.4.1 hoping that would fix the problem, but no dice. After uninstalling Mozy and rebooting Time Machine is backing up to my Time Capsule with no issues.

Hope Mozy will get the issue resolved soon!

Aug 8, 2009 9:47 PM in response to jravelli

Genius...

I wasted the better part of my weekend fighting with my Time Capsule after flawless operation for about six months now.

Never thought to isolate Mozy...

Uninstalled Mozy after...

-slick/reload 10.5.x
-patched to latest updates
-reloading firmware
-reformatting TC numerous times

In short, I did everything on every other forum I came across.

What's worse is it worked great with a USB hard drive, failed miserably over my LAN.

Kind of frustrating that it was an exercise in futility...

...but hopefully some one else will try uninstalling Mozy before going through everything I did.

That's a two minute fix compared to the two day's I've been messing with my TC.

Thank you for the forum post! Nice to know I wasn't suffering alone!

Message was edited by: kmsbeazst

Time Capsule/ Endless Preparing - no backup

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.