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 7, 2009 10:18 AM in response to JohanDA

I am experiencing the same problem with my Time Capsule, with the same error messages being written to the console. I have tried the exact same things as you (with the exception of rolling back the Time Capsule's firmware). In addition to the steps you've taken above, I have also tried deleting and recreating the Spotlight index for my main HD, with no luck. I also pulled the HD out of the Time Capsule and connected it directly to my Mac via USB. Ran Disk Utility on the HD, and it's perfect.

This started happening after I installed 10.5.8. Seems to be a software issue, but I'm at my wits end trying to fix this one.

Aug 7, 2009 11:57 AM in response to bjm103

I tried recreating the Spotlight index as well. Forgot that one.

I just wish that I had a spare machine to completely wipe and reload to see if the issue is fixed. Since I have two machines that stopped working at the same time... I kinda doubt it. I'd be fairly unhappy if I reinstalled the OS and it didn't help.

Aug 7, 2009 12:29 PM in response to JohanDA

Yeah, I also have tried all of those, except rolling back time capsule's firmware, and still I haven't managed to make any backups after 10.5.8 install yesterday.

These are the errors that my MBP has on it's logs:

7.8.2009 22:07:28 mds[35] (/Volumes/Backup of MBP/.Spotlight-V100/Store-V1/Stores/B253FC25-BA8D-49D9-85B8-516B85618D02)(Error ) IndexCI in ContentIndexOpenBulk:No index

7.8.2009 22:07:28 mds[35] (/Volumes/Backup of MBP/.Spotlight-V100/Store-V1/Stores/B253FC25-BA8D-49D9-85B8-516B85618D02)(Error ) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/Backup of MBP/.Spotlight-V100/Store-V1/Stores/B253FC25-BA8D-49D9-85B8-516B85618D02

But funny thing is that this only happens on my MacBook Pro, I also have Mac Mini, running 10.5.8, and it does make backups on the same time capsule.

EDIT: Also after 10.5.8 my EyeTV now complains that I have less than 250MB free on my external HDD and refuses to record anything. This external drive has over 140GBs free.

Message was edited by: Ocid

Aug 7, 2009 12:45 PM in response to Ocid

I think I have finally managed to get this working after 2 days of frustration. It won't be the answer for everyone because it involves opening up your Time Capsule, but this is what I did.

I noticed on this page ( http://www.macfixit.com/article.php?story=20090806095905196) that people were having trouble with file permissions under 10.5.8. When I checked my Console logs during an attempted backup, I noticed chown "Operation not permitted" errors, so I began to suspect that Time Machine didn't have sufficient privileges to do the backup.

I couldn't find a way to run Disk Utility on the Time Capsule Disk, so I opened up the Time Capsule, removed the HD, put the HD into a USB enclosure and connected it to my Mac. When I ran Disk Utility "Verify" and "Repair" on the Time Capsule Disk partition, it returned the following:

-----8<------------------------------------
08/07/09 Friday, August 7, 2009 2:47:34 PM Disk Utility[202] Verify and Repair volume “TimeCapsuleDisk”

08/07/09 Friday, August 7, 2009 2:47:34 PM Disk Utility[202] Starting repair tool:
08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] Checking Journaled HFS Plus volume.

08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] Checking Extents Overflow file.

08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] Checking Catalog file.

08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] Checking multi-linked files.

08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] Checking Catalog hierarchy.

08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] Checking Extended Attributes file.

08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] Incorrect number of Access Control Lists

08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] (It should be 0 instead of 39)

08/07/09 Friday, August 7, 2009 2:47:35 PM Disk Utility[202] Checking volume bitmap.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking volume information.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Volume Header needs minor repair

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Repairing volume.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Rechecking volume.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking Journaled HFS Plus volume.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking Extents Overflow file.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking Catalog file.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking multi-linked files.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking Catalog hierarchy.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking Extended Attributes file.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking volume bitmap.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] Checking volume information.

08/07/09 Friday, August 7, 2009 2:47:36 PM Disk Utility[202] The volume TimeCapsuleDisk was repaired successfully.

08/07/09 Friday, August 7, 2009 2:47:37 PM kernel jnl: disk1s3: journal start/end pointers reset! (jnl 0x72c4930; s 0x44ee00 e 0x44ee00)
08/07/09 Friday, August 7, 2009 2:47:37 PM Disk Utility[202] Repair tool completed:
-----8<------------------------------------

Following the repair, I opened Time Machine preferences, and set it to point to the Time Capsule Disk (which was still connected via the USB enclosure). The backup started working almost immediately. I cancelled the backup, put the HD back into the Time Capsule and rebooted everything.

After repointing Time Machine preferences back to the Time Capsule Disk (now safely back in the actual Time Capsule), I initiated a backup. The backup started working almost immediately (the most success I've had in 2 days) and has been backing up successfully for the past 1/2 hour. I won't be satisfied that I've solved the problem until it completes and I try a restore, but we'll see...

--
To be clear: this is a ridiculous "solution" to the problem. I must have formatted the Time Capsule Disk about 15 times using Airport Utility over the past 2 days, including an incredibly long "zero out" format. I have no idea why this wouldn't have correctly reset the disk with the correct settings. If anyone can figure out how to run Disk Utility on the drive without having to tear the Time Capsule apart, it would certainly be a much better solution.

Cheers, Ben.

Aug 7, 2009 12:49 PM in response to JohanDA

By the way, I had already tried Disk Utility on the drive before (see my initial post). I'm not sure why it didn't work the first time. It may have been the fact that I actually initiated a Time Machine backup onto the drive on my second attempt that corrected the problem. At the end of the day, it's more Time Capsule black-magic than anything else.

Aug 7, 2009 2:11 PM in response to bjm103

So close! I was completely with you... until I put the disk back into the time capsule and tried to restart time machine. Perhaps when I stopped time machine (while it was in the usb enclosure) it didn't leave it in as good of a state as yours for some reason.
I saw it backing up great in the usb enclore... stopped it. Once it was back in the time capsule I was getting errors saying that the disk needed to be repaired and was being mounted read-only etc. I once again erased the disk with the airport utility, and I'm back to the original problem. Perhaps I'll try again. Maybe the 2nd time is the charm 🙂

Aug 7, 2009 10:45 PM in response to JohanDA

Looks like this defect is also affecting other networked drives. I tried to connect one of my external drives to my Mac Mini and to backup my MBP to it. Time Machine gives the same error messages as the Time Capsule.

Looks like I have to do the backup the hard way, remember to connect external USB drive and remembering to unmount it before sleep ;(

Aug 8, 2009 5:36 AM in response to Ocid

And this bug affects USB disks also, I'm able to backup few GBs and then time machine craps out again with errors like:

8.8.2009 15:26:00 mds[3453] (/Volumes/WD/.Spotlight-V100/Store-V1/Stores/798B28DC-6028-491B-B7B9-FADAD60FA4 BA)(Error) IndexCI in CIMetaInfoSync:sync err: 22

I have tried 3 different USB drives which all worked flawlessly on 10.5.7.

OT: 10.5.8 is causing problems on ChronoSync also

2009-08-08 12:45:43 +0300] * Error: File is exclusively open by another application.
[2009-08-08 12:45:43 +0300] Occurred while copying file:
[2009-08-08 12:45:43 +0300] /Users/pete/Virtual Machines/WMLI011047.vmwarevm/Applications/Backup Outlook.cmd — WMLI011047.app/Contents/Resources/document.icns

These never occured before 10.5.8

Aug 8, 2009 7:15 AM in response to JohanDA

I tried backing up to a freshly formated HD in a USB enclosure overnight last night. The backup completed with no errors. However, following the adage that "If you haven't tested your backup, you don't have a backup", I made some changes to my Documents folder, did another backup, and then tried to restore to the original version. Time Machine only ever shows me the most recent folder version i.e. I can't actually go "back in time" to retrieve any files. In other words, it's completely useless.

I tried to open up the .sparsebundle file, and received a "you don't have sufficient privileges" error message. I don't recall ever having that message before when opening up the .sparsebundle. I changed the owner/permissions on the .sparsebundle file to my user account. Now I receive the error "No mountable file systems".

For me at least, 10.5.8 has completely hosed Time Machine. I would love to roll back to 10.5.7, but I can't because 10.5.8 screwed up all of my backups!

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.