Temporally solution for Spotlight indexing

Hi ALL,
After reading endless tips and tricks I found a temprally solution for the Spotlight indexing issue that came up after the update Lion 10.7.5
The problem is that is long Spotlight is trying te finish the indexing TimeMachine can't make a backup.
TimeMachine is conected to Spotlight.
So, if you like to backup again than you have to quit the Spotlight indexing task.
To do so read this website.
There are 2 commandlines in it you can drop into Terminal.app
file://localhost/Users/eurodata/Desktop/How%20to%20Disable%20(or%20Enable)%20Spo tlight%20in%20Mac%20OS%20X%20Lion.webloc
I will wait until Apple **** with the solution to fix the Spotlight issue.
Until than you can search for document etc. by using the search window in Finder window.
The most important is NOW that I can make backups.
Good luck ...
Dimaxum

Hello Hanas,
Glad to hear that it worked.
But sinds the latest update 10.7x the issue is gone.
The best you can do is to download the Combo-Updater from the Apple official download website.
Good luck ...
Dimaxum

Similar Messages

Solution for spotlight not finding all files and plea to apple...

ok, here is the deal:
you are looking for a file named "new_template.lso" which is a logic song template, that you created with logic studio.
this file resides in ~/Library/Application Support/Logic/Song Templates/ a location where logic insists on putting the song templates.
looking for it via the spotlight menu shows nothing.
looking for it with the finders search reveals ... nothing. *** ?
here is the wonderful solution:
-open a new finder search: cmd-f.
-goto the first dropdown menu
-choose "others"
-look for "system files" check the corresponding box.
-go back to the search window and search for the file - no result
-now go to the first dropdown menu and choose the newly added "system files" entry.
-finally go to the second dropdown menu and choose "contains".
boom, totally easy and fast and user friendly... you got your file.
this solution isn't even possible in the spotlight menu!!!
so why am i not supposed to find files in my user library?
i am 32 years old.
i use my computer to make a living.
i used macs since 10 years.
i promise i will not sue apple if i find and delete files by mistake.
seriously this dumbing down the system starts to get unbearable.
does anyone know of a workaround?
are there any hidden preferences for spotlight, which i could change so it shows "system files" by default???

I completely agree. Everyone who has a problem with this (and I see it is a hot topic in these forums) should send apple a a note and tell them that we don't all stick to iLife and some of us go into the LIBRARY. Leopard is great, but Tiger let me efficiently find stuff in the library and I was always confident I'd find all I needed.
Send your comments here to apple feedback. http://www.apple.com/feedback/macosx.html/

Is there a fix for spotlight indexing yet?

I've searched a few times regarding this issue and it seems like there's no resolution. At least for me.
It seems like spotlight randomnly starts indexing with an annoying frequency. So much so I feel that it is harming my computer and hamering not only it's abilities, but it's life itself.
Fans will kick in high. Normal apps like Safart and Mail will start to run sluggish. It's killing me.
Anyone know of a fix?
Methods I've tried:
-Resetting PRAM
-Reindexing Spotlight by adding then removing the Mac Hard Drive in System Preferences.
-Excluding certain programs such as dropbox
None have worked.
Is there a way to manually delete the index? Is that safe?
I know I can just turn it off, but it's incredibly useful. If that's my only option then so be it. I just need to be sure.
Thanks in advance folks. Hope I dont sound as frustrated as I actually am LOL. Part of me is hoping I'm missing something here.
-Greg
Running 10.8.3 on a 13-inch MBP 2.4 Intel Core Duo

If you have more than one user account, these instructions must be carried out as an administrator.
Triple-click anywhere in the line below to select it:
syslog -k Sender mdworker -k Message Sne boxd -o -k Sender mds | tail | open -f -a TextEdit
Copy the selected text to the Clipboard (command-C).
Launch the Terminal 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 Terminal in the icon grid.
Paste into the Terminal window (command-V).
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
A TextEdit window will open with the output of the command. Post the contents of that window, if any — the text, please, not a screenshot.

Lost the ability to Spotlight Index my Time Machine drive

I have an external, Firewire Time Machine drive which has been working without problems up to now. This evening I had a backup which hung up in the "preparing" stage (no file transfers begun yet). When I went to look in the console, there was a device error apparently related to trying to detect the powered-on state of my Time Machine drive. Apparently Time Machine did not handle this gracefully. In the course of trying to clear that I got into a state where I had to force shutdown of the system (holding the power button). (I accidentally clicked on the Time Machine icon which got hung up trying to display the histories, and left me with no access to the Desktop....)
Things appeared to check out fine when I brought the machine back up (including Verify Disk of both the main and Time Machine drives and Repair Permissions of the main drive), and I finally did a Back Up Now in Time Machine. Due to the forced shut down, this became a "Deep Traversal" "preparing"stage. We'll I've seen those before, so no worries. However it lasted quite a bit longer than it should, at which point I noticed that Spotlight was indexing the Time Machine drive.
So at this point I dragged the Time Machine into the Spotlight Privacy list. Rather than going away completely as I expected, the indexing of the Time Machine drive apparently went into some sort of clean-up phase that said it was still indexing for another 5 minutes (where it had, just prior, said it was going to be indexing for another 2 hours). The progress bar advanced normally as if it really did do 5 minutes more of indexing of the Time Machine drive. I've not seen this before
When that finished, the backup which had been "preparing" during all of this also finished "preparing", transferred the several MB of files I expected, and finished normally. There were no errors in the console related to any of this.
I rebooted, and once again did a pair of Disk Verifies and a Repair Permissions without problems. Opened up the console to track things, and poked around in the Time Machine. All was normal as far as I can tell. I also explored the Time Machine drive via the Finder. No problems.
So I now went into Spotlight Privacy and removed the Time Machine drive from the privacy list expecting it to do the re-indexing I had stopped above. Spotlight started indexing the drive and a couple seconds later it stopped. I tried again -- into and out of privacy -- same result, a couple seconds of indexing and then it stopped.
At this point I noticed the console was saying I had some bus errors in the I/O system, and that's what was terminating the md worker process and stopping the indexing.
So I shut down, unplugged the Time Machine drive, and went through my maintenance ritual.
I reset the PMU (this is a powerbook), reset PRAM, booted once in Safe Mode, booted normally, and ran Disk Utility again to Verify and Repair Permissions on the main hard drive. All of that went without a hitch. No failures, faults or funnies.
I ran through the list of Applications I use, keeping an eye on the console. Again no problems.
So I shut down, plugged the Time Machine drive back in and booted back up. I put the drive into Spotlight Privacy and turned off Time Machine backups. I then did a Verify Disk on that drive. No problems. I went into the Time Machine history display. No problems. And no problems looking at it in the Finder either. In particular, no bus errors or anything else funny in the console.
I rebooted and did a new Back Up Now. It completed without problems. It was another Deep Traversal backup due to the Safe Mode Boot, but it went without a hitch. I rebooted and did another Back Up Now and got a normal speed incremental backup again without a hitch. The bottom line is that as far as I can see that Time Machine drive is working just fine.
So I went into Spotlight Privacy and removed it from the list. Once again it started to index and stopped in a couple seconds. But this time there were NO Console error messages.
I moved my main hard drive into Spotlight Privacy and removed it and it re-indexed from scratch just fine. Tried again with the Time Machine drive -- indexing stopped in a couple of seconds with no message in the Console. Spotlight searches find all the right stuff in the main drive. Spotlight and finder searches find only the top level Time Machine folders in the Time Machine drive.
I also tried removing the Spotlight plist from my account's Library / Preferences. Spotlight created a new plist as expected but it still won't index that darned Time Machine drive.
Apparently there is something left over from when I originally aborted the Spotlight indexing of that drive which is causing Spotlight to think it has no work to do. I'm not seeing any I/O errors of any sort any more (I think my maintenance pass took care of that) and Time Machine backups and history access continue to work just fine. And again, the Time Machine disk Verifies just fine.
So I've run out of things to try.
Is there a hidden file that I need to remove from that drive so that Spotlight no longer thinks it already has it indexed?
--Bob

Well unfortunately the command
sudo mdutil -E /Volumes/MyDiskName
didn't help.
The command itself echoed the name of the volume and then said "Indexing Enabled", which looked good. But the Spotlight indexing stopped after a couple seconds. The Console reported the Terminal sudo command and nothing else.
I tried moving the Time Machine drive in and out of Spotlight privacy and once again the indexing started and stopped a couple seconds later with no Console messages.
I then tried another trick I've learned to make Spotlight indexing happen which is to do a Finder search for, say, all folders (limited to the one drive) via Command-f and while Including both System Files and files both Visible and Invisible. And indeed Spotlight indexing started but again stopped a few seconds later.
However, this time there were console messages and a crash report.
The Console shows (with personal information x'ed out):
12/31/07 1:30:38 PM mds[28] (/)(Error) IndexCI in openindex_filelazy:open file error: 2, 0.indexGroups
12/31/07 1:30:41 PM ReportCrash[146] Formulating crash report for process mds[28]
12/31/07 1:30:42 PM com.apple.launchd[1] (com.apple.metadata.mds[28]) Exited abnormally: Bus error
12/31/07 1:30:42 PM com.apple.launchd[1] (0x10ba40.mdworker[96]) Exited: Terminated
12/31/07 1:30:42 PM com.apple.launchd[1] (0x1004a0.mdworker[108]) Exited: Terminated
12/31/07 1:30:42 PM mds[147] (/Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF/0. ; needs recovery
12/31/07 1:30:43 PM ReportCrash[146] Saved crashreport to /Library/Logs/CrashReporter/mds2007-12-31-133038Xxxxxx-Xxxxxx-Computer.crash using uid: 0 gid: 0, euid: 0 egid: 0
The Crash Report reads as follows (again with personal information x'ed out):
Process: mds [28]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
Identifier: mds
Version: ??? (???)
Code Type: PPC (Native)
Parent Process: launchd [1]
Date/Time: 2007-12-31 13:30:38.746 -0500
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000030
Crashed Thread: 15
Thread 0:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0000cfa0 0x1000 + 49056
5 mds 0x00005580 0x1000 + 17792
Thread 1:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 2:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 3:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 4:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 5:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 6:
0 libSystem.B.dylib 0x92eda3ec _semwaitsignal + 12
1 libSystem.B.dylib 0x92f16fa0 pthread_condwait + 1580
2 mds 0x00009648 0x1000 + 34376
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 7:
0 libSystem.B.dylib 0x92ee0ea0 read$UNIX2003 + 12
1 mds 0x000091b4 0x1000 + 33204
Thread 8:
0 libSystem.B.dylib 0x92f15438 kevent + 12
1 mds 0x0007e584 0x1000 + 513412
Thread 9:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 10:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 11:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 12:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 13:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.spotlight.index 0x00207f0c _handleExceptions + 208
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 14:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 Crashed:
0 com.apple.spotlight.index 0x002046cc ContentIndexContainsContentByDocId + 204
1 com.apple.spotlight.index 0x00164358 QueryFunctionCallbackContext::findContent(db_obj*, __CFString const*, char*, int) + 244
2 com.apple.spotlight.index 0x001634d0 qpContentIndexMatch(datastoreinfo*, dblazyobj*, query_piece*, void*, int) + 328
3 com.apple.spotlight.index 0x0015587c comparefile_againsttree + 828
4 com.apple.spotlight.index 0x00155d30 comparefile_againsttree + 2032
5 com.apple.spotlight.index 0x00155d5c comparefile_againsttree + 2076
6 com.apple.spotlight.index 0x001e307c -[SISearchCtx isObjectInQuery:withQuery:shortcut:] + 144
7 com.apple.spotlight.index 0x001fa268 -[SISearchCtx_FSWalk performSearch:] + 996
8 com.apple.spotlight.index 0x001e2cbc -[SISearchCtx executeSearchContextCracked_2:jobNum:] + 136
9 com.apple.spotlight.index 0x00177e80 siwork_queueprocess + 752
10 com.apple.spotlight.index 0x0017811c sischeduleronce + 356
11 com.apple.spotlight.index 0x0017816c sischeduleronce + 436
12 com.apple.spotlight.index 0x001784f8 sischeduler_run_waitingtimeout + 640
13 com.apple.spotlight.index 0x0016529c runLoop + 72
14 com.apple.spotlight.index 0x00165308 query_runLoop + 32
15 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 crashed with PPC Thread State 32:
srr0: 0x002046cc srr1: 0x0200f030 dar: 0x00000030 dsisr: 0x40000000
r0: 0x002046a4 r1: 0xf09a4380 r2: 0x00000000 r3: 0x00000000
r4: 0xf09a43c0 r5: 0x00000000 r6: 0x000074d1 r7: 0x00000000
r8: 0x003fc080 r9: 0x00000000 r10: 0x00000000 r11: 0x44000444
r12: 0x92ede094 r13: 0x00000000 r14: 0x00000000 r15: 0x00373410
r16: 0x00000000 r17: 0x00239e98 r18: 0x00000001 r19: 0x00227b9c
r20: 0x00000000 r21: 0x00245554 r22: 0x00000001 r23: 0x00000001
r24: 0x00000000 r25: 0x00000005 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x00000005 r30: 0xf09a43c0 r31: 0x00204610
cr: 0x24000444 xer: 0x20000004 lr: 0x002046a4 ctr: 0x92ede094
vrsave: 0x00000000
Binary Images:
0x1000 - 0xc1ffb mds ??? (???) <af9cc958b4b030835101ff024186c7d3> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
0xde000 - 0xe0ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
0x139000 - 0x23fffb com.apple.spotlight.index 10.5.0 (398.1) <5843125c709dd85f22f9bd42744beea5> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/Spotlight Index
0x1ca9000 - 0x1caaffc liblangid.dylib ??? (???) <5f078ac1f623f5ce432ea53fc29338c0> /usr/lib/liblangid.dylib
0x2198000 - 0x22bdffb libmecab.1.0.0.dylib ??? (???) <cd875e74974e4ec3a0b13eeeb236fa53> /usr/lib/libmecab.1.0.0.dylib
0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
0x90123000 - 0x9016effb com.apple.Metadata 10.5.0 (398) <b6bb1fd5a7a9135f546b2d8cbd65eafc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x901ab000 - 0x902d0ff3 com.apple.CoreFoundation 6.5 (476) <9073c2bfdf6842562c8b7f0308109c02> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9060a000 - 0x90612fff libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
0x90683000 - 0x90688ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x90757000 - 0x907d2fff com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x9088a000 - 0x9090ffff libsqlite3.0.dylib ??? (???) <7b379cb4220346e99c32c427d4539496> /usr/lib/libsqlite3.0.dylib
0x90aa7000 - 0x90ab5fff libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
0x90b50000 - 0x90be2fff com.apple.framework.IOKit 1.5.1 (???) <591b8b0cc4261db98a6e72e38eef5f9a> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x91105000 - 0x9116cffb libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
0x9116d000 - 0x912b5ff3 libicucore.A.dylib ??? (???) <250daed2fb2e6bf114480e2e4da0728b> /usr/lib/libicucore.A.dylib
0x91c3c000 - 0x91d32ffc libiconv.2.dylib ??? (???) <05ae1fcc97404173b2f9caef8f8be797> /usr/lib/libiconv.2.dylib
0x91d3a000 - 0x91db4ffd com.apple.CFNetwork 220 (221) <00b882d3d3325526b78ded74880759fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x9236a000 - 0x92382ffb com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x92383000 - 0x9238effb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x92742000 - 0x92769fff libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
0x92777000 - 0x92860fff libxml2.2.dylib ??? (???) <6f383df1e1e775be0158ba947784ae13> /usr/lib/libxml2.2.dylib
0x928aa000 - 0x928b9fff com.apple.DSObjCWrappers.Framework 1.2 (1.2) <2411674c821a8907449ac741ce6a40c3> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x92a17000 - 0x92afafeb libobjc.A.dylib ??? (???) <4a90e315bd1718c3f5ae09ee6c23e36c> /usr/lib/libobjc.A.dylib
0x92afb000 - 0x92bc9ff7 com.apple.CoreServices.OSServices 210.2 (210.2) <bad4943629f870d305f2bc7c6dfffe2d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x92bde000 - 0x92dbfffb com.apple.security 5.0.1 (32736) <15632bf9bbdb223194b3d79a2e48e02d> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x92e9a000 - 0x92ec5ff7 libauto.dylib ??? (???) <c1f2bd227817ad7c7bf29ec74729ac7c> /usr/lib/libauto.dylib
0x92ed2000 - 0x9306bfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
0x931a7000 - 0x934a7ff3 com.apple.CoreServices.CarbonCore 783 (783) <fd2acaf23e95472f78b8a077fa039986> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x946f2000 - 0x9472afff com.apple.SystemConfiguration 1.9.0 (1.9.0) <d925dde7699e6231c88a41b0254a7591> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x94933000 - 0x9494eff3 com.apple.DirectoryService.Framework 3.5 (3.5) <3246a5d1c6a3d678798a90e8c5cd3677> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x9494f000 - 0x9494fffa com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x94c68000 - 0x94c9dfff com.apple.AE 402 (402) <a4b92c8ac89cc774b85fb44c48b9d882> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x96831000 - 0x9683afff com.apple.DiskArbitration 2.2 (2.2) <9c8f8ade43fa25b32109ef9dcc0cb5d5> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9683b000 - 0x968d1ff7 com.apple.LaunchServices 286 (286) <a3a0b2af862e9a8945072f8cb523678f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x969bc000 - 0x96c00ffb com.apple.Foundation 6.5.1 (677.1) <4152239382fb0f48abbcbf35bd04afa6> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0xfffec000 - 0xfffeffff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Apparently the mdutil command didn't actually delete the Spotlight index file which is causing the problem, or at least didn't leave the indexing files in a consistent, empty state to start indexing over again. I may have to Erase this Time Machine disk and start over.
I should point out that except for Spotlight indexing this disk is otherwise working just fine. It passes Verify Disk with no errors and both new Time Machine backups and viewing and restoring via Time Machine and Finder work without problem.
Any suggestions before I just Erase the disk and start over with a new backup?
--Bob

How can I make OSX index a network share for spotlight?

How can I make OSX index a network share for spotlight?
I am using a QNAP NAS with SMB network shares, which I mount with OS X Mavericks. They are not searchable, as far as I know because of the indexing of network share is by default not activated.
To force the OS to index them I activated this via mdutils. But this is no solutions. This makes spotlight to index the share once. But I want spotlight to index it always and keep it up to date. I have a huge amount of documents & fotographs, which is very difficult to manage without being searchable.
Unfortunately the only solution I found in the www was the mdutils-way, which seems not to work, maybe only works not for me.
I would appreciate any assistance,
Thank you,
Stefan

My thanks to everyone who has contributed to solving this problem here.
It appears that there still is NOT a good, reliable solution. Please correct me if I'm wrong.
I did find this on http://jonathansblog.co.uk/how-to-enable-spotlight-indexing-on-a-network-drive:
===================================
To enable spotlight indexing on a network drive:
# mdutil /Volumes/name -i on
To disable the indexing of a connected network drive:
# mdutil /Volumes/name -i off
To check the status of indexing on a connected network drive:
# mdutil /Volumes/name -s
===================================
And, I found this on the Synology NAS forums:
cd /Volumes
mdutil shareName -i on
mdimport -Vp ./shareName
where shareName = name of your share
I have used the mdutil /Volumes/name -i on, and it seems to work.
But, if I understand it correctly, it is a one-time indexing -- the index is NOT keep up-to-date with changes.
So, how can we keep the index up-to-date?
My thought was to schedule a Terminal file to execute each night with the mdutil code.
Would this work? If so, how would you setup a scheduled run?
Would it have to be done on each Mac that accesses the Share?

A possible cause for the Lion freezes: Spotlight indexing

Does your Mac freeze mysteriously after upgrading to Lion?
Mine had that problem, but after troubleshooting, I seem to have identified the culprit (at least for my MacBook) and, after deleting the offending file, I have since experienced no problem. Here, I will share a case report with the hope that it will help others troubleshoot their computers experiencing the same problem.
The Problem: Mac (running Lion 10.7 or 10.7.1) freezes sometime after logging on. The freeze begins by an inability to get a response to clicks. The cursor is still active, but after a click or two the cursor turns into a spinning disc. After some time, the clock stops updating on the menu bar.
Mine froze consistently after about 15-20 min after logging on. It happened regardless of which application I was using, it froze even if I didn't do anything after logging on. It required a reboot (control-command-power button on a MacBook) everytime.
Was Spotlight indexing active right before the freeze happened? When Spotlight indexing is active, the magnifying glass icon on the upper right corner of your display will show a blinking dot. Mine was.
A Possible Culprit: Spotlight may have encountered a corrupt file on the hard disk during indexing.
What you can do:
Before you do anything, it is recommended that you have backed up all your files. Unfortunately, it is difficult to back up now because the Mac may freeze during the back up process.
1. Check the errors related to Spotlight by opening Console, which is an utility app that you can find in the Applications>Utilities folder. Do you see error messages for "mdworkers"? It does not always show up before the freeze, but this may indicate some problems during Spotlight indexing.
2. Confirm the problem by turning off Spotlight indexing. You can do this in a number of ways, but I will list two ways below:
a) Go to System Preferences and click on Spotlight icon. Under the Privacy tab, click on "+" icon and add the "Users" folder (or any particular folder that you may suspect). The indexing will not happen to files in that folder. Also, turn off Time Machine and disconnect back up disks, if you use any. Apparently Spotlight indexes within the Time Machine backups. OR
b) For experienced users: Open Terminal and type "sudo mdutil -i off" without the quotes. (To turn it back on, type "sudo mdutil -i on /" without the quotes)
3. Try using your computer with Spotlight turned off. Does it still freeze? If it does not, you have confirmed that the problem is with Spotlight indexing.
4. Find the offending file that causes problem by turning Spotlight indexing back on...
a) Remove the folder by highlighting and clicking on "-" button under the Privacy tab. OR
b) For experienced users: Type "sudo mdutil -i on /" without the quotes.
5. ...and then repeating steps 2a, 3, and 4a. Try isolating different folders until you can narrow down the problem. This process may take a while.
6. Once you narrowed down to a few folders, try QuickLook through the contents of the folder while the Console is open. To use QuickLook, highlight a file in the Finder and hit a space bar on your keyboard. It is helpful to set the Finder in a column view so you can use arrow keys to navigate through the folders. Does Console show you an error when you QuickLook a file? Can you double click and open that file? If not, the file may be corrupt. Trash that file and empty trash.
7. Now turn Spotlight indexing back on (step 4) and use your computer for a while. Does it still freeze? If so, repeat the process and find other corrupt files.
For me, it was a single corrupt image file in the Documents folder that caused the freezing problem. I deleted it and the problem went away. Since that file had been untouched for years, and I did not experience the same freezing problem in Snow Leopard, I suspect that Spotlight in Lion is somehow less permissive of corrupt files assuming that the file did not corrupt after the upgrade.
Steps 4-7 is cumbersome and it takes a long time to troubleshoot. If you know of a faster way to identify corrupt files, please share in this thread. Also, I think Spotlight should alert the users when it encounters a corrupt file and give us a choice to delete it on the spot. Please join me by sending a feedback to Apple about this.

My G5, PPC, came with Tiger installed and ran great. I decided to upgrade to Leopard (not snow leopard) and at first it seemed to work well.
Here is where you should backup, reinitialize, and make sure you use retail 10.4 rather than any OEM DVD?
After several days I noticed I have Permission errors that Disk Utility would not fix. (The only way to repair this was to insert the install disk and run Disk Utility from there: which means you have to reimport/install all the OS updates over again)
Some real confusion. Permissions can and should be done while booted from your hard drive; never run from older version of OS X.
Not all permission messages are errors.
Bootable backups (clones).
Invest in 3rd party repair programs.
Eventually the OS was crashing and freezing so I went to a local Apple repair store to ask why. Apparently Leopard is unstable on some G5 towers.
No, not really.
But you do have to insure your hardware, your software, is also current.
I decided to reinstall Tiger and still had problems. After about 5 attempts at reinstalling the OS I realized I was using a disk from a G4 tower that my kids use, so I found the disk that come with my G5 and the install worked perfectly.
So it appears that not all OS install disks are the same:
No secret there. NEVER use an OEM disc except your own; or, use retail full install versions is all. I guess you never came across that bit.
Sorry you had to take so much time, but sounds like came away with some misconceptions.

Spotlight Indexing, Systemstats, Missing File, All After Mavericks Upgrade

Dear Mac Support Communities,
The upgrade to OS X 10.9.4 has crippled my computer.
My main question is: should I reformat, or should I wait for a patch to come out to solve whatever is wrong with Mavericks? I explain below.
Spotlight is constantly indexing. The mdworker is all over the place on the Activity Monitor—4% and then it explodes to 85% of CPU usage. Systemstats kicks in randomly (connected to spotlight perhaps?) and eats up 90% of my CPU and 3gigs of RAM. Time Machine takes AGES to backup.
I have not been able to stop Spotlight's endless indexing. I have moved my hard drive and my Time Machine backup into the 'private' filter in 'Spotlight Preferences.' I have also tried the "sudo mdutil -a -i off" trick to stop indexing altogether. But Spotlight Indexing goes "off" and then automatically turns "on" in Terminal. Spotlight carries on, and the computer performance is choppy.
I've run disk repair. First, I repaired permissions. Then I verified and attempted to repair the the hard drive. There is a missing file apparently, and I therefore must reformat. This is very first issue I've ever had with the hard drive since I bought the computer. Considering how awful Mavericks has been—I have been reading other Support Communities posts—I'm nervous about something going wrong, or that all these problems will persist after the reformat.
All of this has occurred three days after my upgrade to to OS X 10.9.4. I have heard of numerous people having problems with Mavericks. All similar problems concerning missing files, haywire spotlight, systemstats devouring any remaining CPU power and memory space, and slow Time Machine back-ups.
Anyone with the same problems? Care to theorize some solutions?
I have a late 2008, 15inch MacBook Pro., 2.53 GHz Intel Core 2 Duo, 8 GB 1067 MHz DDR3, running OS X 10.9.4 (13E28).
Cheers! I appreciate the help.

Older Macs have more troubles under Mavericks. Considering the age of your Mac, it's not uncommon to start have hardware issues like drive failure.
To repair the drive you must boot from the Recovery Drive.
Boot into the Recovery Drive by holding down Command R when restarting.
Run Repair Drive and Repair Permissions using Disk Utility in Recovery.***
Next Reset Home Directory Permissions and ACLs following directions here This will serve two purposes. It will reset YOUR permissions. Not the same as Disk Utility reset permissions and it will cause Spotlight to re-index your drive when restarting.
Restart
Download and run the combo updater to refresh your OS X files.
OS X Mavericks 10.9.4 Update (Combo)
http://support.apple.com/kb/DL1755
MORE INFO ON WHY RUNNING COMBO FIXES ISSUES
Apple updates available from the Software Update application are incremental updates. Delta updates are also incremental updates and are available from Apple Downloads (software updates are generally smaller than delta updates). The Combo updates contain all incremental updates and will update files that could have become corrupted.
Combo updaters will install on the same version as they're applying--no need to roll back or do a clean install.
"Delta" updaters can only take you from one version to the next. For example: 10.9.3 to 10.9.4. If somehow the 10.9.3 is missing something it should have, and that something isn't changed between 10.9.3 and 10.9.4 it will still be stale after the delta update.
***If Disk Utility is unable to repair you will have to copy your data to an external drive first. Reformatting will erase the drive. You should have a backup regardless, if your data is important to you. Just like a seat belt and an air bag protect you in different ways when driving, you need both Time Machine and a clone for full protection. If you don't have an external drive for backup, I can give you some suggestions to get you started.
Both of these applications can be used to create a clone.
SuperDuper! http://www.shirt-pocket.com/
CCC http://www.bombich.com/download.html

Spotlight Indexing Problem

I've been scouring the internet looking in forum after forum for the answer to this problem for several hours now. I've tried all the usual fixes (which I will detail below) and none of them seem to be working.
I recently installed Leopard from Tiger on my MacBook. Since then I've been having a problem with Spotlight hanging while it's indexing. It gets about 80% of the way through before it starts hanging. I have no external hard drives connected (and therefore have not begun using Time Machine).
I Repaired Disk Permissions and booted up from the install disc and Repaired Disk.
I opened Terminal and entered +sudo mdutil -E /+ which restarted Spotlight indexing, but the problem arose again.
I added my entire hard drive to the Privacy list within Spotlight options. Spotlight stopped indexing (as would be expected). When I removed my hard drive from the Privacy list, the problem arose again.
Now, I have told Spotlight not to index any of the categories within Spotlight preferences. I will add each category in, one-by-one. This is currently taking place, and I will add posts as progress persists.
Can anyone help? I would really appreciate any kind of assistance in this matter.

I've been seeing the exact same problem and have posted queries with no solution. Currently my status is that I have switched off Spotlight indexing with an app called Spotless and am using EasyFind as my search tool. This is far from satisfactory though, as Spotlight is embedded inside many Apple apps as the search tool (Mail, for instance) and EasyFind doesn't replicate the function of searching inside apps. Since I rely on searching my mail more often than anything else on my drives, I'm not happy.
Spotlight has failed on both my my MacBook Pro and also my dual quad MacPro, despite my having done complete clean installs on both these machines. I've tried a process of elimination to attempt to find the file/files that are the culprit for the indexing hangs but it is a tedious and indefinite process, principally because it's impossible to know exactly when Spotlight gets hung up (I basically just have to listen for my fans to spin up watch the Activity Monitor for mds taking over the CPU). The console logs are almost no help in trying to find out what's going on, as they seem only to register the problem after I have quit Console and relaunched it (ie, they are not seeing the process hang as it happens).
One thing that may help you (although it didn't help me) is that Spotless allows you to delete old indexes created under earlier systems, that, as I understand it, may hang around through the install of 10.5 and interfere with new indexing.

Confirmation on How to Stop Spotlight Indexing an External Hard Drive

Hello everyone,
I know there are a number of posts on this but I just want to confirm: Can I stop Spotlight from indexing my external FireWire hard drive by adding its name to the Privacy pane in Spotlight's preferences when the drive is mounted? (I'm a little low on internal hard disk space on my iBook so I want to keep the index as lean as possible.)

Georgy
Keep in mind that the index is stored on the drive that is being indexed. As such, indexing an external volume does not affect your main drive.
Remember also, that when you do update your external drive, the indexing only updates the changes made to the drive on the fly, provided of course if it is mounted and allowed to do so.
My suggestion, let Spotlight index the drive. Particularly if you are using it as a backup. Once in place, updating the index and searching is extremely fast.
Be careful however, of using third-party solutions. Some will affect Spotlight's normal indexing process and their preferences have to be changed for Spotlight to work.

Gmail, Apple Mail, and excluding mailbox spotlight indexing

Hello,
I use Apple Mail with my gmail IMAP account. Therefore I have a big mailbox "All Mail" where I have duplicates for all emails in "Sent" and my other tags (mailboxes in Apple Mail).
Whenever i search for something, I always get duplicate results, one from Inbox, the same email in All Mail, for example. I've added the "All mail" mailbox to the list of Spotlight exclusions, but Apple Mail seems to ignore this, because I still get results from that mailbox.
Also tried resetting hte spotlight index but this doesn't fix it.
Any ideas on how to force a mailbox not to be indexed by spotlight?
Thanks.

Thanks, Andy. I should have posted a closure statement on this thread as I finally figured everything out. The most frustrating thing is Google's own advice at http://mail.google.com/support/bin/answer.py?answer=78892# couldn't further from correct. After many hours of experimenting with settings, I finally came up with the correct ones. In fact, I'm in the process of writing an article about it since there is simply no definitive guidance on the web that I've been able to find in the time I've searched.
Your comments are on target...everything on the *Behaviors Tab* needs to be checked (excepts Notes) and the *Delete when* settings must be set to Never. But there are a few other things that must be done, including some changes on Gmail Settings before Mail and Gmail will be perfectly synchronous. I'll post the entire solution on this forum when I finish the graphics.

Mountain Lion: problem with Time Machine directories and spotlight indexing

I'm using a fresh install of 10.8 Mountain Lion on a 2011 MBP. It's a work laptop with many ASCII files containing numerical data (floating point numbers), with varying file extensions. Some of the files are multi-gig, some are only a few hundred K, and there are tens of thousands of them. Roughly 500G of numerical data.
I can disable spotlight from indexing certain subdirectories of my home directory on the local drive. However, when using Time Machine to backup, I seem to be entirely unable to prevent spotlight from attemping to fully index the external drive (Time Machine volume). I actually let spotlight run for over 36 hours this weekend in a futile attempt for it to finish indexing the TM volume. The /.Spotlight-V100 index on the external drive is roughly 100G and continuously written and overwritten. /var/log/system.log had various "Merging failed" messages for temp spotlight files. I deleted the index, let spotlight run again overnight, but it did not finish indexing. "sudo fs_usage -f filesys mds mdworker mdimport mdworker32 | grep open" showed spotlight slowly chugging through the thousands of numerical files.
I believe the problem is related to this old report from someone who noticed a leopard -> snow leopard change:
http://hintsforums.macworld.com/showthread.php?t=106703
http://forums.cnet.com/7723-6126_102-366184/snow-leopard-10-6-spotlight-indexing -and-disk-usage/
However, I don't see an easy solution. In ML, if you drag the TM volume to the spotlight privacy list it gives you a message about how you can't disable indexing of TM volumes because it's essential for TM. I have not yet tried to manually put in some kind of .metadata_never_index file in the relevant TM volume directories (I am not sure if that will do anything, or perhaps break TM backups), but that's one possible next step.
Anyone have ideas on how I can have my TM backups work but the spotlight indexing of all these data files (their subdirectories) disabled? I'm not specifically TRYING to back up those data files with TM (they're duplicated elsewhere), they're just on the same machine as a bunch of other stuff I need backed up via TM. Apple has a disaster on their hands for anyone trying to backup a machine which also has large data sets.

I'm not aware of any avenue to tell spotlight to not index all or part of a backup.
However, the indexing should work, even if takes a long time.
I don't think this is a new issue and has been part of TM from the start.
Realistically, it may be time to consider whether TM is the best choice for these data files?
Are they very volatile do they change frequently both as to content of individual files and total set of files?
If not, then a clone or syncing type of backup might be better suited for these files.
I do not back up all my files via time machine. I keep photographs and music outside of Time Machine. to be sure they are backed up but via clones.
To show why this might the best take photographs. My photographs are basically immutable once they enter the system, but I may come back with 5000 images from a trip and whittle that down to a few hundred eventually. This would cause a lot of files to be saved in TM that are no longer wanted, - but are not easy to remove formthe backup. while the ones I want haven't changed. TM is not geared to make handling that easily.
As a further aside, ideally one should back everything of value up twice via 2 different means.
I've had backup drives fail.I've had TM logically fail (disk is fine -TM internal data structures bad).

Re: Spotlight indexing behaviour problem

Hi,
My .Spotlight-V100 problem is in relation with network users. We have an xServe in the office with multiple users. When somebody logins from an iMac with a network user the spotlight starts to reindex the whole database. Every time somebody logs out then in, the spotlight rebuilds the index folder.
Is there any solution for this problem besides turning of the spotlight? We have to use the spotlight for searching in thousands of mails and it would be great if it could use the index folder without rebuild it every time the computer starts. I tried to solve the problem with fixing the permissions of the folder .Spotlight-V100 but it seems ok now, and the problem remains.
Thanks a lot in advanve.

I'm having the same problems too. Still searching for a solution.

How can I determine if Spotlight indexing is running?

I am having occasional severe slowdowns, during which the machine becomes extremely unresponsive. Attempts to switch to a different app can take minutes, even clicking in the menu bar can take more 30 seconds to bring up the menu.
Most of the time this happens, in fact probably all the time, is when I return to the machine after it's been "inactive". My energy saver settings are "never put the computer to sleep when it is inactive" and "put the display to sleep when the computer is inactive for 15 minutes". Screen saver is set to "never".
I believe the cause could be spotlight indexing, but how can I verify that? Occasionally when this happens I've gotten into the terminal window and run "top", but I don't notice anything unusual (but I may not know what to look for). Once, I brought up the spotlight window and it had a line that said something like "indexing in progress". Or perhaps I imagined that, because I haven't seen it since.
I am also using Time Machine, but TM never claims to be doing anything during these slowdowns. TM backs up to a 500G external drive, and I have three drives that I rotate through monthly. At one point I added the top directory on the external drive to Spotlight's privacy list, hoping this would prevent it from indexing the backup. That didn't seem to solve my problem, and in any case the three external drives have different names, and spotlight doesn't seem to remember them. And trying this today spotlight won't let me add the top level folder (Backups.backupdb) but instead forces me to go one layer deeper and add all the folders in that folder (one for each machine I backup).
It would be rather annoying to continually tell spotlight about the backup folders. And I don't even know that spotlight is really the problem.
I've found this thread:
http://discussions.apple.com/thread.jspa?messageID=8977265
but I'd like to verify that spotlight is indeed the cause, and that the solution mentioned there is indeed a proper solution.
Thanks for any help,
Bob H

There are several background operations and actions taking place in the system
and at various levels, too; you may have noticed them in Activity Monitor utility,
and by clicking once to highlight an active one in the list, you can further look into
any one of particular interest to see what else it may have going on.
However, some of these layers of function are rather cryptic to the casual user
who may not get around to learning about their usually hidden reason for being.
You may spot something or another in Activity Monitor's list of All functions, and
depending on how that list is ordered or preferences set to be viewed, more or
less information may be available immediately.
And then, there is the Console utility, where you can see what may have been
going on at or near a specific time; since the reports and logs are time dated.
Sometimes, when my computers (no more than two at a time, are on) seem to
be running something or another, but I haven't a clue exactly what, I will look
into both of these utilities to see why; or what it was busily doing.
In Console, you can sometimes see groupings of messages that repeat and
they can appear to be commands that failed or were ignored by the system;
and it still works just fine, at least for the most part. If you find a list of odd
long log messages that are about the time you hear the machine working, it
may be worth a try to discover what the process is, that is running that long.
{It is possible to force spotlight to re-index, and some other things, too. But
the need to do so should be researched before doing that. A tool such as
OnyX can do more than most users would need, outside of its Automation
selection of most common maintenance chores. Be careful if you use it.}
You may have to check into the functioning of the computer to be sure
the system and hardware are OK.
Good luck & happy computing!

10.5.3 update -A possible solution for those who have hard spinning fans!!!

Hey people!
I've been diggin around the internet for a solution to this problem... I couldn't find anything at all till I started to mess with my macbook around... I tried to reindex the spotlight by deleting the previous indexed list of files with an app called "spotless" but nothing happened. I even tried to reset the SMC - system management controller - but still nothing happened... I tried some other things out but I had come out unsuccessful TILL... I remembered myself to try all this out in safe mode....
This was so far the strangest thing I've ever experienced on a mac... by entering in safe mode the fans just started to ramp down and my laptop returned to what it used to be! Just that - entering on safe mode! After entering and after listening to the fans loosing speed, I rebooted in normal mode and my laptop was healthy again!
To start up into safe mode (to "Safe Boot"), do this:
- Be sure the computer is shut down.
- Press the power button.
- Immediately after you hear the startup tone, press and hold the Shift key.
Tip: The Shift key should be held as soon as possible after the startup tone but not before.
Release the Shift key when you see the gray Apple and progress indicator (looks like a spinning gear).
P.S. - if you get lucky with this procedure just reply me and spread the word!
Good luck!
Rui Caldeira
Message was edited by: Caldeira

Actually... it really solved the problem for me! My computer have sounded like a jet plane for the last couple of days. But I'm not sure if the only solution is to boot into safe mode. I recommend you to do like this:
1.) Remove the spotlight indexes and disable the service if you don't use it. You can use Spotless to do this. You find it here: http://mac.softpedia.com/progDownload/Spotless-Download-9834.html
2.) Reset the SMC. Om a MacBook, you turn the computer off and remove AC and the battery. Hold the power button for about 10 seconds. Insert the AC but NOT the battery and boot the computer. Shut it down and install the battery.
3.) After the SMC reset, boot the computer into safe mode by holding the shift key during boot up.
4.) Let the fans spin down in safe mode for a couple of minutes.
5.) Restart the computer into normal mode and the fans should now be spinning normally again!
This worked for me, but only in the order above!
/D

Is the spotlight index stored on the boot drive or individual volumes?

Hello!
My questions are pretty simple, and are sumarized here (from the block of text below):
First, if I have several external hard drives, is the Spotlight index file for each drive stored on the external hard drive, or on OS X's boot drive?
Secondly, if it's stored on the boot drive, can I copy these files to another Tiger-running Mac to eliminate the need to re-index the hard drives? Where do I find them?
Third: Leopard's Spotlight has quite a few new features. Even if the Tiger index files are stored on the external drive, will it need to re-index the drive to support the new feature set?
Now for the long explenation:
I have been preparing to upgrade my Powerbook to Leopard within the next month or two, and as such, I bought a new hard drive to dedicate one of my old drives to Leopard and Time Machine. Because I have three extrernal hard drives, I needed to move about 500 GB of data between the thee drives to make room for what was on the now-dedicated drive. Of course, this requires that Spotlight re-index the "new" drives.
Today, I left all of the drives attached to my old G4, running Tiger, while it sits there indexing the three drives, totaling around a terrabyte of external storage. Because Spotlight tends to hog all of the available CPU time, and the G4 should be done indexing the drives, it would save me a lot of time if I could copy the index files over from the G4 to my Powerbook to avoid indexing them all over again. That is, if the index files are not on the external drives already. If they are on the G4's boot drive, where do I find these files?
Finally, I plan to reformat the internal hard drive of my Powerbook when I install Leopard - I make a habit of doing a fresh install for every major upgrade (eg, 10.3, 10.4, 10.5, etc). To estimate the amount of time needed to upgrade, I'd be nice to know if Leopard will need to re-index the files on the external drives - even if Tiger's spotlight index is stored on the externals - for Leopard's new Spotlight features. Will it need to re-index? I would assume that until Leopard arrives, most people wouldn't know this, of course.
Thanks a bunch,
-Dan

Each drive's Spotlight index is located on that drive.
(25154)

Temporally solution for Spotlight indexing

Similar Messages

Maybe you are looking for