Spotlight Gone Crazy indexing TIme Machine Backup!!

I was having issues with mdworker crashing, and spotlight hanging forever while indexing something..


So I decided to turn off the Spotlight indexing, thought I would flush its caches and start over.


Consequently I executed " sudo mdutil -a -1 off "


The response I received back was that spotlight indexing had been turned off for all volumes, EXCEPT that it was now turned on for

/Volumes/TMbackup/Backups.backupdb . This is my TimeMachine backup volume - I don't want this indexed.


I rebooted the machine, and lo and behold mds gets very busy indexing the above mentioned volume. I can hear the backup drive chattering like crazy.

SENDER PID FACILITY LEVEL MESSAGE

mds 37 user Error (Normal) DiskStore: Reindexing /Volumes/TMbackup/.Spotlight-V100/Store-V1/Stores/B1DEE27E-93F7-46D3-97DF-E3166 A1C363E because no basetime was found.

mds 37 user Error (Normal) DiskStore: Rebuilding index for /Volumes/TMbackup/Backups.backupdb

mds 37 user Error (Normal) DiskStore: Creating index for /Volumes/TMbackup/Backups.backupdb

mds 37 user Error (Warning) Server: No stores registered for metascope "kMDQueryScopeComputerIndexed"


I tried "sudo mdutil -i off /Volumes/TMbackup/Backups.backupdb " with the USELESS response:


/Volumes/TMbackup/Backups.backupdb:

Indexing enabled.


Then I went to the Spotlight Privacy tab. I made sure that /Volumes/TMBackup was in the exclude list. I tried adding /Volumes/TMbackup/Backups.backupdb, but it wouldn't let me.


I finally made it stop by ejecting the Time Machine volume.


This is really frustrating ... I'm having system problems, and now I can't use my backup drive.


Any suggestions out there on how to stop this unwanted indexing.

iMac, Mac OS X (10.6.8), 27", i5

Posted on Mar 10, 2012 9:25 PM

Reply
12 replies

Mar 11, 2012 6:04 PM in response to ericnepean

ericnepean wrote:

. . .

The response I received back was that spotlight indexing had been turned off for all volumes, EXCEPT that it was now turned on for

/Volumes/TMbackup/Backups.backupdb . This is my TimeMachine backup volume - I don't want this indexed.

You have no choice. It must be indexed for Time Machine to work properly. See the note in section 2 here: http://docs.info.apple.com/article.html?path=Mac/10.6/en/8991.html.


The index must be corrupted. First, try repairing your backups, per #A5 in Time Machine - Troubleshooting.


If that doesn't fix it, see the pink box in #D2 of the same link.

Mar 12, 2012 7:59 AM in response to Pondini

Hi Pondini ... can I ask for your help again?


I've come to the conclusion that after a thorough backup, and doing HW checks, and after potentially identifying bad sectors or replacing the hard drive (as needed), I should do a clean install of the OS. The OS that is now limping along on my machine has effectively been continuously upgraded since 10.4.8, taking into account transferring all the accounts and settings from my old Mac to the current HW.


Since I was planning to upgrade to Lion, I may as well do a clean install of Lion, instead of installing a clean copy Snow Leopard, and upgrading.


Which leads back to the question of the Time Machine backup from 10.6.8, possibly with bad indexing.


Is it reasonable to attach the Time Machine drive to my machine with the new 10.7.3 OS, and let it deal with any indexing issues there, or am I better off to attach it to my MB Air which is stable at 10.6.8 but doesn't have any TM backup configured, and deal with any issues there. Or must I have the the "home" system attached to correctly reindex the Time Machine volume?

Mar 12, 2012 8:53 AM in response to ericnepean

ericnepean wrote:

. . .

The OS that is now limping along on my machine has effectively been continuously upgraded since 10.4.8,

That's not really true. Upgrading replaces everything in OSX and the default Apple Apps. What's left behind are 3rd-party apps and the files that support them. That's where most of the problems come from -- especially apps that you no longer use or have deleted, but left some pieces behind. Those will take up some space, but as long as nothing is running, there's no performance hit from them.


What does happen is, if the leftover pieces were background or "helper" processes, they may continue to run, or, worse, try to run, then fail because some parts are missing, and restart over and over.


You can usually identify them by looking at your system.log. See the tan box in OSX Log Files to find it, then the blue box, especially the Application Installation or Removal problems section, to find such problems.



Since I was planning to upgrade to Lion, I may as well do a clean install of Lion, instead of installing a clean copy Snow Leopard, and upgrading.

That's a bit easier said than done, unless you buy the Lion USB stick ($69). The reason is, to buy Lion from the App store ($30), you must be running Snow Leopard to download it. You can do that, then instead of installing, copy the installer to a DVD, USB stick, or partition on an external HD. Then erase your internal HD, boot from the installer, install Lion, then use Setup Assistant to transfer your user accounts and data from your backups, then reinstall all your 3rd-party apps from the original discs (or re-download them). See Making a Lion Install disc or partition for instructions.


Just installing Lion over Snow Leopard will get rid of everything in your current version of OSX (as would installing Snow Leopard without erasing).


If you do erase, I'd strongly recommend making a second full backup on a different HD with the Restore tab of Disk Utility, or CarbonCopyCloner or SuperDuper, just in case something goes wrong with your TM backups or either HD. That's rare, of course, but does happen.



Which leads back to the question of the Time Machine backup from 10.6.8, possibly with bad indexing.


Is it reasonable to attach the Time Machine drive to my machine with the new 10.7.3 OS, and let it deal with any indexing issues there, or am I better off to attach it to my MB Air which is stable at 10.6.8 but doesn't have any TM backup configured, and deal with any issues there. Or must I have the the "home" system attached to correctly reindex the Time Machine volume?

The structure of Spotlight indexes has changed in Lion. It will create a new index on every volume -- your OSX drive, TM backups, and any other drives/partitions (which may take a while, of course, so don't be surprised if your Mac is rather sluggish until that's done).


If you connect it to your MB Air, I don't think it will be indexed unless you select it as the TM destination and start a backup to it, but I can't swear to that.

Mar 13, 2012 7:29 AM in response to Pondini

Thanks again Pondini.

Upgrading replaces everything in OSX and the default Apple Apps. What's left behind are 3rd-party apps and the files that support them. That's where most of the problems come from -- especially apps that you no longer use or have deleted, but left some pieces behind. Those will take up some space, but as long as nothing is running, there's no performance hit from them.


What does happen is, if the leftover pieces were background or "helper" processes, they may continue to run, or, worse, try to run, then fail because some parts are missing, and restart over and over.

That describes my stuation very well, and I think I may have more than one of these going on. I think there are also bits leftover from an anti-virus program that I tried and rejected. Although I have checked the system log's a number of times, and deleted a few suspicious items, I can't seem to cure the restarts. Hence I've come to realise that eventually I will need to do a clean install. Given this weeks problems, that will be coming soon, I think.


I'm getting suspicious of the DISK I/O errors that I occssionally see. The only seem to occurr when certain processes run and cash (mdworker), and they don't seem to affect the many gigabytes of data I'm reading ad copying to the backupdrive.


I'm spending a couple of days backing everything up throughly, then I'll have a go fixing at original indexing issue. Then I'll report here how that went.

Mar 16, 2012 11:40 AM in response to Pondini

So.... 3 backups on two different drives, plus time machine. Now I don't care what happens to the hard drive.


I ran the the Apple Hardware test, extended mode, several times, and the result in each case was "No Trouble Found".


I also observe that I copied 650GB of data off the drive, about 4 times, and the copying encountered a disk I/O error only when copying one particular file. I eventually deleted this unimportant file, however mdworker continues to crash after DiskI/O errors.


On to some more HW tests, I want a thorough check for bad sectors, although I really am suspecting this is a problem with corrupted OS caches or OS configuration files. Genius bar appointment on Sunday.

Mar 16, 2012 11:47 AM in response to ericnepean

ericnepean wrote:

. .

I really am suspecting this is a problem with corrupted OS caches

If so, you might want to try deleting them. The free OnyX app is good for that. When it starts, it wants to do a permissions check and verify disk -- you can skip those, since you've already done them. Then you need your Admin password, and it shows some warnings, etc, via Help. Select the Cleaning icon in the toolbar and you can select some or all caches, etc.


or OS configuration files.

You could try installing the 10.6.8 "combo" update, per Installing the ''combo'' update and/or Reinstalling OSX. If that doesn't help, a fresh version of OSX (that won't disturb anything else) might be worth a try, per the same article.

Mar 17, 2012 9:50 AM in response to Pondini

Many thanks Pondini. I reset all the caches with Onyx and most of the crazyness disappeared, indexing seems back to normal and Time Machine is back up and running. I ran the 10.6.8 combo update afterwards, but it was the cache cleaning that fixed the problem.


I note that in Onyx there 6 sets of caches in the clean menu, and each set has to be cleaned sepaerately. Some of them are specific to the users account, so they have to be cleaned for each user account.


I'm still having one problem, can't get mobile me working on one account (it works on the other account), I think I'll need to referr to the mobile mee forum or Apple for assisatnce in that regard.

Mar 17, 2012 10:02 AM in response to ericnepean

ericnepean wrote:

. . .

I note that in Onyx there 6 sets of caches in the clean menu, and each set has to be cleaned sepaerately. Some of them are specific to the users account, so they have to be cleaned for each user account.

Yes. General cache cleaning usually isn't a good idea; normally, if you're having a problem with one app in one account, just delete the cache in question. Caches are good 99.9% of the time; they speed up your Mac. Only when one gets corrupted should it be deleted (with the possible excption of a browser cache).


I'm still having one problem, can't get mobile me working on one account (it works on the other account), I think I'll need to referr to the mobile mee forum or Apple for assisatnce in that regard.

I just got around to converting to iCloud. Never had much trouble with MobileMe, so don't know a lot of troubleshooting, either, so that's probably your best bet.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Spotlight Gone Crazy indexing TIme Machine Backup!!

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