Spotlight doesn't stop indexing

Hi guys,
Every time I start my iMac (everything up to date, Mac OS X 10.8.2) Spotlight starts calculating the time it will take to complete the indexing. And it takes many, many hours until it actually starts indexing - today I waited 15 hours, then shut the indexing of, restarted the SystemUIServer and waited again maybe 6 hours of calculating the time. Now Spotlight actually startet the indexing; I had that one or two times but then shut my computer off since I had to go to bed, now I'll keep it on to see what happens. I'll post tomorrow what happened, but that Spotlight takes so long to start indexing is a problem that shouldn't be and that should be mentioned and fixed.
Greetings,
Jannis

Please read this whole message before doing anything. This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it. The purpose of this test is to determine whether your problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows: 
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click  Log in.
 *Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Similar Messages

  • 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.

  • Spotlight does not stop indexing

    I need help: Just started the brand new MacPro 2x 2.66. The long desired spotlight (I run osx 1.3.9 before) does not work. Spotlight never stop to index. It runs and runs. If I add the hard drive to privacy in the system preferences it stops, but as soon as I get it back it just continues to index. So I've never been able to use Spotlight. Another harddrive in the machine (one without just data, no system) is swiftly indexed. But as soon as I have the main HD open for indexing, Spotlight continues to index for ever.
    The harddrive causing the prooblem has previously been used in another computer under 1.3.9
    Any ideas for fixing this would be much appreciated.
    MacPro 2x 2.66 Mac OS X (10.4.8)

    Hello,
    I'm seeing the same kind of problem. Here are the symptoms:
    -Some or all data from a Mac previously running 10.3, is migrated to a Mac using 10.4. The Migration Assistant is used.
    -Spotlight will continuously re-index, stop for a brief period, and repeat, either by itself, or when a search is attempted.
    -Erasing the indices with mdutil -E, running fsck, fixing permissions and stopping/starting Spotlight doesn't resolve the problem.
    -Excluding the migrated user directory will stop the madness. I.e., other users and shared directories like Applications, are searchable, and Spotlight will stop the continuous re-indexing.
    -Recreating the user directory from scratch, and then copying in data from a backup, may once again start the madness.
    The big question is, what, exactly, causes the indexing cycle?
    The client affected by the problem is very disappointed, and had cause to wonder "how is this any better than Vista? I would have been better off with a Windows PC". I really need to resolve this, but I'm not sure of the best way to get Apple Tech involved with this bug.
    Many Macs   Mac OS X (10.4.8)  

  • Spotlight won't stop indexing mail

    i have unchecked messages and chats in the spotlight search results but i still get these cluttering up my search efforts. any idea how to stop this or why it is happening?
    thanks.

    i have unchecked messages and chats in the spotlight search results but i still get these cluttering up my search efforts. any idea how to stop this or why it is happening?
    thanks.

  • Spotlight won't stop indexing in Lion 10.7.3

    I read several other posts and think I have a fix.

    I read several other posts and think I have a fix.

  • Spotlight wont stop indexing

    My Spotlight wont stop indexing. It says (and has always said) there is about 2000 hrs left until it has finished indexing... hence I cant use. Any idea of how I can fix this? THANKS!

    Launch the Terminal app in /Applications/Utilities/, copy & paste this command into the window that pops up, and hit the return key:
    *sudo mdutil -E /*
    When the Password: prompt pops up, enter your admin password, carefully, since nothing shows up on the screen, and hit the return key. When the prompt returns, quit the Terminal app.
    The command +causes the local store for the boot volume to be erased. The store will be rebuilt.+ The store is what contains the index and supporting items.

  • Spotlight stopped indexing?!

    I have recently upgraded firefox 3 (but just drag and drop and replacing the old one) and also Skype to the most update to date version. However, spotlight can not find these... I use bootcamp and parallels for windows XP system and the spotlight will only show the windows version of the software!!!
    Help! Is there a way to force spotlight to index everything? I have checked everything in the preference panel. Is my spotlight somehow corrupted? If so, is there a way to fix it?
    Thank you in advance for all your help!

    Hello everyone! I am having the same problem with my Spotlight not indexing anymore. In fact, when I use Spotlight, putting in a term that I KNOW a file exists for, it returns the error "nothing found." I used the following tip found on the site to manually turn on indexing (or so it said) but still no indexing. Does anyone have any ideas on what I can do? It's really becoming a pain not having spotlight work. Thanks to everyone!! P DUB
    (Here is the solution I tried that didn't seem to work--at least not for me---I will say this however:
    AFTER I completed these steps, I did get a message in TERMINAL that said "indexing enabled." which was encouraging---but spotlight has still not indexed!! Again, any ideas??
    This tip is useful, but a way too complicated way to do this. A better and simpler solution is as follows:
    1. Login in to your server as an administrator.
    2. Open the Terminal application (in your /Applications/Utilities folder)
    3. Type the following exactly as written in to the Terminal:
    sudo rm /.metadataneverindex
    It will ask you for your password. I have never seen this file, so you may get a "file not found" error - in which case move on to step 4 anyway.
    4. Type the following in to the Terminal:
    sudo mdutil -i on /

    5. Spotlight in the right corner of your server login should indicate it is indexing, and before long will start working.
    I don't believe editing of hostconfig is required at all, and you don't need to do all this stuff with making invisible files visible since you are already in the Terminal anyway.)
    THANKS TO EVERYONE FOR YOUR HELP!! P DUB OKC

  • Spotlight doesn't appear when I click on it or when I use the cmd space....

    All of a sudden it stops coming up. ??????

    I'm having the same problems. Spotlight doesn't respond when I click on its icon in the menu bar, and splat-space highlights the icon but doesn't open any windows.
    If I click on a Finder window and hit splat-F I can open a finder window but it appears it stopped indexing a while ago because I don't see any new info. I've deleted the index and it's reindexing now, but no change in the Spotlight icon behavior.
    I have Now-Up-to-Date as well, and I'm running the current version, but I'm a bit nervous about deleting that startup folder without knowing what that will do. If that simply removes the icon from the menu bar I'm fine with that.
    Spotlight does occasionally work. I don't know why but it'lll suddenly kick into gear. These days, though, it's not available 95% of the time, which is a bummer as I really like it and used it a lot.

  • Spotlight doesn't find html files

    I'm a web developer. I have thousands of ".html" files, such as "india.html"
    Spotlight won't find them.
    It does find "india.cfm" files so I'll assume the problem is the html extension.
    If I Show All in Finder it does them ... in a Find window section called "Developer" ... which doesn't appear in Spotlight, or is a choice in Spotlight Preferences.
    This used to work. I'm now using 10.9.5. I don't know at which update it stopped working ... I don't perform this often but when I do it's critical.
    I've repaired permissions and reindexed the drive (twice, by adding and removing the drive from Spotlight index preferences).
    Thanks.

    A test...
    Made a plain text file, saved to desktop, apple.html. Spotlight doesn't find it. Duplicated it. Change the name to apple.txt. Spotlight immediately finds it.
    Spotlight is having a problem with html.
    Checked the Spotlight RichText.mdimporter and it has:
    <array>
    <dict>
    <key>CFBundleTypeRole</key>
    <string>MDImporter</string>
    <key>LSItemContentTypes</key>
    <array>
    <string>public.rtf</string>
    <string>public.html</string>
    <string>public.xml</string>
    <string>public.plain-text</string>
    <string>com.apple.traditional-mac-plain-text</string>
    <string>com.apple.rtfd</string>
    <string>com.apple.webarchive</string>
    <string>org.oasis-open.opendocument.text</string>
    <string>org.openxmlformats.wordprocessingml.document</string>
    </array>
    </dict>
    </array>
    ... so that's in there...

  • SpotLight takes forever to index

    I know there are a few questions with this title, but they are really about SpotLight taking forever to prepare the indexing. In my case, it takes forever to index. It starts, get a few pixels' worth of the progress bar done, and then stops forever. I've left my computer on for hours on end hoping SoptLight will eventually finish its job; it doesn't. (By the way, it also doesn't give me an estimated remaining time; I just get the progress bar.)
    I'm running Mavericks (10.9.5) on a MacBook Pro from September 2014; my computer runs on a 2.2-GHz i7 processor and has 16 GB of RAM. I've got about 420 GB of data (recovered from a TimeMachine backup) split up as follows: about 200 GB is in the computer's 250-GB internal flash-memory "hard disk", and the rest of it is in an external SeaGate 2-TB drive.
    For the sake of my battery (which is eaten up ridiculously quickly by SpotLight), I've turned indexing off with the terminal command sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist. However, I do want the indexing to get done so I can actually search my Mac for stuff. I've already run into one instance of the computer being unable to find a document which I know is there (I think it was in the SeaGate drive, but it was looking everywhere, not just in the internal disk); I don't want that to happen again. So how do I get the indexing to actually get done? (Oh, I have a STRONG preference for solutions which don't involve installing third-party software.)
    I'd never had this problem before, and I've restored data from TimeMachine backups in the past.
    Thanks in advance for any help.

    Thanks for your reply, Linc Davis.
    The first terminal command resulted in the following (not knowing whether they are privacy-related or not, I replaced the hex codes after MDSImporterProxy with Xs):
    Oct  4 17:25:46 (Error) ImportServer: <MDSImporterProxy 0xXXXXXXXXXXXX shutdown:NO got shutdown notification:NO> still waiting for plug-in info from bundle finder
    Oct  5 12:14:16 (Error) ImportServer: <MDSImporterProxy 0xXXXXXXXXXXXX shutdown:NO got shutdown notification:NO> still waiting for plug-in info from bundle finder
    Oct  5 18:20:28 (Error) ImportServer: <MDSImporterProxy 0xXXXXXXXXXXXX shutdown:NO got shutdown notification:NO> still waiting for plug-in info from bundle finder
    Oct  6 08:27:29 (Error) ImportServer: <MDSImporterProxy 0xXXXXXXXXXXXX shutdown:NO got shutdown notification:NO> still waiting for plug-in info from bundle finder
    Oct  6 19:48:33 (Error) ImportServer: <MDSImporterProxy 0xXXXXXXXXXXXX shutdown:NO got shutdown notification:NO> still waiting for plug-in info from bundle finder
    Oct  7 09:23:53 (Error) ImportServer: <MDSImporterProxy 0xXXXXXXXXXXXX shutdown:NO got shutdown notification:NO> still waiting for plug-in info from bundle finder
    The second terminal command resulted in the following:
    Spotlight server is disabled.
    I therefore reactivated SpotLight indexing (with the same command as in my original post, only replacing unload with load), after which I immediately reran the second terminal command. I got the following:
      Error: unexpected indexing state.  kMDConfigSearchLevelTransitioning
    /Volumes/SeaGate:
      Error: unexpected indexing state.  kMDConfigSearchLevelTransitioning
    I then waited a few seconds so SpotLight would start "indexing" and ran the comman a third time, this time getting the following:
      Indexing enabled.
    /Volumes/SeaGate:
      Indexing enabled.
    In the console, under "Diagnostic and usage information", there are three sections: "Diagnostic and usage messages", "User diagnostic reports" and "System diagnostic reports". I wasn't sure which of these I should look under, so I selected each of them and searched for "spotlight" (searching for either "mdworker" or ".crash" produced 4 or 5 results, all unrelated to SpotLight, and searching for "mds" returned no results). Only the first section, "Diagnostic and usage messages", had results. At first there was a single result, which I am quoting below (again, I replaced the UUID with Xs); after I turned SpotLight indexing off again (using the command on my original post), I got a second message which was identical to the one below but had no date and had the then-current time. (Note that 10.07 is the date in the format I specified in the system prefs and 11:31:47.238 is, I suppose, the time in Apple's preferred format.)
    10.07 11:31:47.238 SystemUIServer[185]: com.apple.message.domain: com.apple.batterymenuextra.signature
    com.apple.message.signature: com.apple.metadata.Spotlight
    com.apple.message.summarize: YES
    Sender_Mach_UUID: XXXXXX

  • Spotlight does not complete indexing

    About 2 months ago I noticed two unusual things on my wife's MBP (see specs below). The first was that the spotlight kept indexing and it did not end regardless of how much time I allowed it to run. On the other hand, time machine backups would start when the external Time Machine HD was connected but it would stall before completing the backup to the point that I would have to cancel the backup completely.  I noticed these two conditions basically at the same time, and at first I thought they were unrelated.
    Regarding the spotlight indexing I tried several remedies I found on different forums, but none worked for my particular problem.
    Tried several times to rebuild the index by adding and then removing the Macintosh HD into System Preferences/Spotight/Privacy/ panel.
    Repaired disk using the [Disk Utility on] install disk.  No problems were found.  Also repaired permissions just in case, but no luck either.
    Tried resetting the PRAM.
    Tried resetting the home folder permissions and ACLs via reset password utility on the OSX Install disk.
    Tried to index the HD from another user account (which had also Administrator privileges).
    Using the Console and the Activity Monitor I noticed that when the indexing started, I would see the mds, mdworker and mdworker32 processes running.   Also I would see disk activity and if I clicked on the spotlight icon I would see that the time remaining to complete the index would decrease.  However, at some point both mdworker processes would halt (disappear from the activity monitor), and then the mds process CPU usage would jump to 98% or more.  At this point the spotlight indexing time remaining would start to rise gradually.  I remember seeing indexing completion times as high as 52 hours.  The only way to get out of this was to exclude the Macintosh HD from the spotlight and then reboot the machine.  I am aware that this would also delete whatever progress was made with the index file and that future attempts would need to rebuild the index from scratch.
    After making several attempts to rebuild the index and having the same result, I though that there was a maybe corrupted file or folder that would be causing the problem.
    In an attempt to isolate the problem, I made the following:
    First I had the Macintosh HD excluded from the spotlight search and rebooted the machine.
    I added all the folders under Macintosh HD (e.g. Applications, Library, System, Users, etc.). After adding the folders, I then removed Macintosh HD.  This would have the same effect as adding the Macintosh HD excluded, but with the flexibility of being able to build the index by adding folders one by one until the problem showed up again.
    I started removing folders from the Spotlight privacy panel until the problem arose.  I noticed the problem had occured when the mds process would reach 98% or more AND the mdworker processes had disappeared from the Activity Monitor.
    Once I found the folder where the problem was (in my case was the Users folder), then I would add all the folders under the Users folder and repeat the process again.
    After several iterations, I found that the folder causing the problem was ~/Library/Application Support/Mobile Sync/Backup/<UDID>; where <UDID> corresponds the my wife's iPhone's UDID number as seen on iTunes.  By excluding the <UDID> folder the spotlight would run without problems.  If I added this folder, then the problem would reappear.
    Turns out that the folders that is causing the problem is the backup folder for my wife’s iPhone.  I don’t mind this folder being indexed, however I also discovered that the Time Machine problem I mentioned earlier would be resolved by excluding this same folder from the TM backups; and THIS concerns me.
    I though the problem was a corrupt backup folder so in an attempt to solve this I deleted the backup from iTunes and made a full phone backup.  Unfortunately this did not solve my problem.  I am still not able to include the iPhone backup folder as part of either spotlight or TM.
    Any help on this matter is greatly appreciated.
    MacBook Pro 13in. Core 2 Duo 2.4GHz (mid 2010)
    4GB RAM
    OSX 10.6.8
    iTunes 11.4
    iPhone 5 (model MD641LL/A), iOS 6.1.4

    Hello,
    I'm seeing the same kind of problem. Here are the symptoms:
    -Some or all data from a Mac previously running 10.3, is migrated to a Mac using 10.4. The Migration Assistant is used.
    -Spotlight will continuously re-index, stop for a brief period, and repeat, either by itself, or when a search is attempted.
    -Erasing the indices with mdutil -E, running fsck, fixing permissions and stopping/starting Spotlight doesn't resolve the problem.
    -Excluding the migrated user directory will stop the madness. I.e., other users and shared directories like Applications, are searchable, and Spotlight will stop the continuous re-indexing.
    -Recreating the user directory from scratch, and then copying in data from a backup, may once again start the madness.
    The big question is, what, exactly, causes the indexing cycle?
    The client affected by the problem is very disappointed, and had cause to wonder "how is this any better than Vista? I would have been better off with a Windows PC". I really need to resolve this, but I'm not sure of the best way to get Apple Tech involved with this bug.
    Many Macs   Mac OS X (10.4.8)  

  • Spotlight doesn't work

    Hi there,
    I have a problem with spotlight indexing.
    It fails on me in a number of different ways.
    Sometimes, when I try to reindex, it will never finish (Estimating indexing time... appears forever).
    Sometimes, when I try to reindex, it will never finish (100 hours left ... appears forever).
    Sometimes, it finisches indexing, but will not index any new file that I create,
    or find out that I actually changed the location or the content of some of the already indexed files.
    I write sometimes, because I really did not find out when happens when.
    I tried everything available on the internet of course:
    Reindexing by adding/removing the entire harddisk from the privacy tab,
    using the commandline tools
    mdutil -i off /
    mdutil -E
    mdutil -i on /
    removing /.Spotlight-V100
    in a number of combinations,
    unmounting the disk, booting with an external disk, then mounting and repairing the disk,
    in addition repairing permissions on the disk,
    resetting the pram/nvram of my macbook pro early 2008,
    adding a huge number of folders to the privacy tab before starting to index,
    then slowly removing them...
    Nothing helped.
    I am absolutely stuck.
    No hint on the internet how one could lead spotlight to reindex just a specific part of the
    filesystem. No hint how spotlight behaves and why.
    Every help appreciated.

    Thanks Tony,
    You are right, these are pages explaining a bit how it works.
    However, my special problem seems to be that spotlight, at some point,
    stops indexing. And I did not find out which is the switch that tells
    the spotlight indexing machine to restart indexing when a new file is created or an old one is changed, or to continue indexing yet unknown files. It seems to me that this is somehow the fundamental thing that's broken in my case.
    When doing what you propose (as I already wrote above), spotlight does start
    to index again, but somewhere down the road justs stops.
    Right now, it has indexed for over 24 hours, and when searching for something,
    I just get "estimating indexing time".
    mds and mDNSResponder are the only processes that start with "md", and both run
    at quasi 0% CPU.
    No mdworker process has been running for over 22 hours.
    The size of /.Spotlight-V100 is 3.4 MB.
    Now, I have a standard macbook pro early 2008 running standard 10.6.3 with a standard 500 GB drive, more than half of it available.
    What could be wrong with this structure?

  • Spotlight doesn't search in word documents

    Hello,
    I have a Question regarding Spotlight: If I look for any phrase which is in word documents, Spotlight doesn't find it. (I got some documents from a friend, each about 100 pages). When I use OpenOffice and export the documents to pdf: no problem, Spotlight works perfectly.
    Is there a way to force Spotlight to index this folder? I thought, Spotlight would index word documents automatically...

    I found out the reason:
    The *.doc documents were rtf-documents with a doc at the end. Spotlight doesn't index rtf as it seems.
    Saving them as word solved the problem.

  • Yosemite Spotlight doesn't give results in the internet?

    I already check the web results in spotlight preferences but still it won't search the net. Im from australia.

    Might be corrupted Spotlight preferences.
    Open the Finder. From the Finder menu bar click Go > Go to Folder
    Type or copy paste the following:
    ~/Library/Preferences/com.apple.Spotlight.plist
    Click Go then move the com.apple.Spotlight.plist file to the Trash.
    Restart your Mac then try a Spotlight search.
    If that doesn't help, reindex Spotlight >  Spotlight: How to re-index folders or volumes

  • Leopard's Spotlight doesn't search...

    Hi there!
    I've got a problem with Leopard Server...
    It's the first time that I run a server version.
    Everything works great! But... Spotlight...
    Spotlight doesn't search anything on my internal HD. On my external HD (connected with FireWire) it works!
    I already deleted the .Spotlight Folder on my startup disk... But that doesn't help... I added my HD to the "privacy" Tab in Spotlight and deleted it after that... But that doesn't help, too...
    Has anybody of you an idea how to make this work?
    Thanks a lot!

    I got to Spotlight to search and index my internal harddisk again.
    I rebuilt the .Spotlight-V100 folder including the subfolder which I copied from a working (searchable external harddisk) which I initially deleted in my trial to get Spotlight working again.
    After a lot of tinkering with mdutil, Cocktail (a superb OS X system utility) and the Spotlight preference panel the overal problem for Spotlight might have been that I have got the internal and the Windows partition named starting the same name "Aristoteles" then a "blank" and the "HD" on the OS X partition and "WinXP" on the Windows partition. Obviously that got Spotlight confused because when I specifically excluded the windows partition (using the Spotlight preferences panel) and reactivated the remaining OS X partition using the "sudo mdutil -i on /Volumes/Internal" command (I renamed the OS X disk partition from "Aristoteles" to "Internal") ... bang Spotlight kicked in ... but the strange thing is that Spotlight kicked in telling me it is searching the OS X partition "Aristoteles" instead of "Internal".
    I cannot remember any technical comment (this is pure "trial and error" on my side) that Spotlight only takes the first part of a disk name. But if two partitions on the same disk start with the same name Spotlight may run in to troubles unless one is excluded from searching ... and even a later renaming of a partition doesn't help ...
    Message was edited by: OlympusUser

Maybe you are looking for

  • Is OCZ Vertex Turbo 60GB 2.5" SSD compatible with my Mac Pro, or do I need

    Is OCZ Vertex Turbo 60GB 2.5" SSD compatible with my Mac Pro, or do I need the Vertex Mac Edition? I have decided to purchase a SSD to use as a boot drive in the spare optical drive bay. There are so many brands available, and Intel X25-M 'G2' seems

  • Option for saving a file as a pdf is not available in scroll down menu

    I've been trying to save a file as a pdf by selecting print but pdf does not show up for one of the options in the scroll down menu. All I have to choose from is Fax, hp psc 1200 series and Microsoft XPS Document Writer. I was able to do this back in

  • Problem in applying startup script

    In a domain with a windows 2008 R2 domain controller, windows 7 computers apply the startup script but windows xp sp3 boxes show this log in event log:  Source: UserInit Event ID: 1000 Could note execute the following script \\192.168.1.4\scripts\pin

  • Goop Wizard vs. OpenGoop

    Hi NG I have tried the Goop Wizard 1.0 (Endevo) and want to rewrite an existing app with objects. Yesterday i discovered OpenGoop. I haven't tried it yet and I am in hurry. I want to start the reprogramming best yesterday. Other people are waiting. S

  • SET CHAINED command not allowed within multi-statement transaction

    Hi, i need to do one transaction and i am setting autocommit(false) and once i am don ewith my 2 inserts i am settins it to true. i have like 20 thousand rows and when it is working fine for some inserts but after that it is throwing "SET CHAINED com