sageonthehill
Level 1 (1 points)

Q: Mavericks: Spotlight Indexing Forever!

Upgraded to Mavericks and system is unbelievable slow. Searched this forum and found many hints regarding Spotlight. Noticed that mine keeps indexing forever. It tells me all the time "estimating indexing time", sometimes it starts the actual indexing, but then I find myself back again waiting for this #$@! estimating the time. This is going on now for 2 full days without the slightes improvement.

 

Not only the slow speed makes the computer almost unusable, files cannot be found anymore neither via spotlight nor finder! Same applies to email.

 

Any advice will be highly welcome. Thanks!

 

Screen Shot 2013-10-27 at 7.31.58 AM.png

MacBook Pro, OS X Mountain Lion (10.8.2), Gmail

Posted on Oct 27, 2013 6:22 AM

by sageonthehill,Solvedanswer
sageonthehill sageonthehill
Level 1 (1 points)
A:

Well, lacking any input and thus alternatives, I just went for the timemachine backup. 3 hours for restoring, now waiting another half an hour for mail import. At least I can work again. Thank you Apple...!

Posted on Oct 28, 2013 11:55 PM

Close
sageonthehill

Q: Mavericks: Spotlight Indexing Forever!

  • All replies
  • Helpful answers

Page 1 of 8 last Next

  • by sageonthehill,

    sageonthehill sageonthehill Oct 27, 2013 5:00 PM in response to sageonthehill
    Level 1 (1 points)
    Oct 27, 2013 5:00 PM in response to sageonthehill

    Day 3 starts and I want to smash this machine against the wall! Seriously.

     

    It seems I have to accept a slow-down in my work either by staring at beachballs or go for another clean install like I had to do after my last OS up-grade. What an annoyance! I wonder why I am (we are?) so patient with Apple who continue to release products that are just not properly tested.

  • by sageonthehill,

    sageonthehill sageonthehill Oct 27, 2013 6:15 PM in response to sageonthehill
    Level 1 (1 points)
    Oct 27, 2013 6:15 PM in response to sageonthehill

    I found a hint by Linc Davis and used the "mdutil -as" and "mount" command in Terminal. This is what I get. Does this tell anyone anything? I'm not a geek...

     

    mdutil -asHomes-MacBook-7:~ Home$ mdutil -as

    /:

              Error: unexpected indexing state.  kMDConfigSearchLevelTransitioning

    /.MobileBackups:

    2013-10-28 07:58:55.884 mdutil[920:507] Metadata.framework [Error]: mdsCopyStoreAttributes failed: (8) (os/kern) no access

              No index.

    /Volumes/MobileBackups:

              Index is read-only.

    /Volumes/MobileBackups/Backups.backupdb:

              Index is read-only.

    Homes-MacBook-7:~ Home$

     

    Homes-MacBook-7:~ Home$ mount

    /dev/disk0s2 on / (hfs, local, journaled)

    devfs on /dev (devfs, local, nobrowse)

    map -hosts on /net (autofs, nosuid, automounted, nobrowse)

    map auto_home on /home (autofs, automounted, nobrowse)

    localhost:/E9uZVax9sCSPTZGTxR6cXF on /Volumes/MobileBackups (mtmfs, nosuid, read-only, nobrowse)

    Homes-MacBook-7:~ Home$

  • by Carolyn Samit,

    Carolyn Samit Carolyn Samit Oct 27, 2013 6:23 PM in response to sageonthehill
    Level 10 (124,473 points)
    Apple Music
    Oct 27, 2013 6:23 PM in response to sageonthehill

    Open Activity Monitor located in HD > Applications > Utilities

     

    Select CPU on the left.

     

    Select:  mdworker   under Process Name on the left.

     

    Then click the Force Quit icon (circle with an x) top left in the Activity Monitor window.

     

     

    mdworker is the Spotlight process.

  • by sageonthehill,

    sageonthehill sageonthehill Oct 27, 2013 7:06 PM in response to Carolyn Samit
    Level 1 (1 points)
    Oct 27, 2013 7:06 PM in response to Carolyn Samit

    Thanks Carolyn!

     

    When I opened the activity monitor, I found 5 processes mdworker at the same time. While 'force quit' them, new ones keep popping up. Somehting wrong here, right?

     

    Screen Shot 2013-10-28 at 9.04.02 AM.png

  • by sageonthehill,

    sageonthehill sageonthehill Oct 28, 2013 6:35 AM in response to sageonthehill
    Level 1 (1 points)
    Oct 28, 2013 6:35 AM in response to sageonthehill

    After more and more hours of frustration I found this in Console after adding and then re-deleting my HDD to the spotlight privacy list.

     

    This doesn't tell me anything and I am still hoping for some help from you guys... Will be hapy to share the crash report in case this leads to anything...

     

     

    10/28/13 8:25:44.830 PM ReportCrash[377]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.

    10/28/13 8:25:50.011 PM mds[38]: (Warning) DiskStore: Got indexer death

    10/28/13 8:25:50.012 PM mds[38]: (Warning) DiskStore: Got indexer death

    10/28/13 8:25:50.296 PM com.apple.launchd[1]: (com.apple.metadata.mds.index[91]) Job appears to have crashed: Bus error: 10

    10/28/13 8:25:50.336 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:25:50.337 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:25:50.337 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:25:50.337 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:25:50.337 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:25:50.337 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:25:50.337 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:25:50.338 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:25:50.339 PM mds_stores[383]: (Error) Permissions: Failed stat on perm journal with error 9

    10/28/13 8:25:51.160 PM ReportCrash[377]: Saved crash report for mds_stores[91] version 800.12 to /Library/Logs/DiagnosticReports/mds_stores_2013-10-28-202551_Homes-MacBook-7.cr ash

    10/28/13 8:25:56.562 PM mds_stores[383]: (Error) SecureStore: Access token 6 changed uid from -1 to 502

    10/28/13 8:26:12.000 PM kernel[0]: disk0s2: I/O error.

    10/28/13 8:26:13.037 PM mds[38]: (Warning) DiskStore: Got indexer death

    10/28/13 8:26:13.037 PM mds[38]: (Warning) DiskStore: Got indexer death

    10/28/13 8:26:13.042 PM com.apple.launchd[1]: (com.apple.metadata.mds.index[383]) Job appears to have crashed: Bus error: 10

    10/28/13 8:26:13.155 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:26:13.155 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:26:13.156 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:26:13.156 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:26:13.156 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:26:13.156 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:26:13.157 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:26:13.157 PM mds[38]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"

    10/28/13 8:26:13.164 PM ReportCrash[377]: Saved crash report for mds_stores[383] version 800.12 to /Library/Logs/DiagnosticReports/mds_stores_2013-10-28-202613_Homes-MacBook-7.cr ash

    10/28/13 8:26:16.499 PM mds_stores[399]: (Error) SecureStore: Access token 6 changed uid from -1 to 502

    10/28/13 8:26:31.000 PM kernel[0]: disk0s2: I/O error.

     

    then this stuff goes on and on...

     

     

  • by sageonthehill,Solvedanswer

    sageonthehill sageonthehill Oct 28, 2013 11:55 PM in response to sageonthehill
    Level 1 (1 points)
    Oct 28, 2013 11:55 PM in response to sageonthehill

    Well, lacking any input and thus alternatives, I just went for the timemachine backup. 3 hours for restoring, now waiting another half an hour for mail import. At least I can work again. Thank you Apple...!

  • by DCIFRTHS,

    DCIFRTHS DCIFRTHS Oct 29, 2013 1:52 AM in response to sageonthehill
    Level 1 (21 points)
    Oct 29, 2013 1:52 AM in response to sageonthehill

    One of myt machines is constantly indexing too. Wish I could find a solution.

  • by sageonthehill,

    sageonthehill sageonthehill Oct 29, 2013 2:19 AM in response to DCIFRTHS
    Level 1 (1 points)
    Oct 29, 2013 2:19 AM in response to DCIFRTHS

    And is this related to Mavericks installation?

     

    You may find a couple of hints in the "more like this box" on the right at the top of this page. However, didn't solve my specific problem...

  • by DCIFRTHS,

    DCIFRTHS DCIFRTHS Oct 29, 2013 2:29 AM in response to sageonthehill
    Level 1 (21 points)
    Oct 29, 2013 2:29 AM in response to sageonthehill

    I have only see this happen after installing Mavericks. Is that what you are asking me?

  • by sageonthehill,

    sageonthehill sageonthehill Oct 29, 2013 3:04 AM in response to DCIFRTHS
    Level 1 (1 points)
    Oct 29, 2013 3:04 AM in response to DCIFRTHS

    Yes, that was my question.

     

    Lots of people report that the indexing itself takes a lot of time (you have probaly seen the threads), but I have not seen others who have this problem of just estimating the indexing time forever...

  • by Kalkas,

    Kalkas Kalkas Oct 29, 2013 12:44 PM in response to sageonthehill
    Level 1 (5 points)
    Oct 29, 2013 12:44 PM in response to sageonthehill

    I have also the same problem: estimating indexing time goes forever. Is there a solution?

  • by Tony T1,

    Tony T1 Tony T1 Oct 29, 2013 12:47 PM in response to Kalkas
    Level 6 (9,249 points)
    Mac OS X
    Oct 29, 2013 12:47 PM in response to Kalkas

    I had this problem and I re-indexed Spotlight on Macintosh HD: http://support.apple.com/kb/ht2409

  • by DCIFRTHS,

    DCIFRTHS DCIFRTHS Oct 29, 2013 3:58 PM in response to sageonthehill
    Level 1 (21 points)
    Oct 29, 2013 3:58 PM in response to sageonthehill

    Oops. My mistake. While it does take a long time for the "estimating" screen, my main problem is the constant reindexing. Sorry for the confusion.

  • by sageonthehill,

    sageonthehill sageonthehill Oct 29, 2013 5:35 PM in response to Tony T1
    Level 1 (1 points)
    Oct 29, 2013 5:35 PM in response to Tony T1

    Tony, I did the same, but the error continued.

Page 1 of 8 last Next