Spotlight index lost after each login

Hello people,
I've got a very confusing thing going on with Spotlight on my mac.
After each login, Spotlight looses its index and I can't my files.
I have tried solving this problem with the app IceClean, using "sudo mdutil -i on /", dragging and remvoing something into the privacy tab in Spotlight's preferences and some other tips and tricks I got from this forum, but nothing worked.
The odd thing is, Spotlight finds the files, but only after some time. My guess it's restores the index or re-indexes everything. Yet that doesn't help since it gets deleted after the next login.
I am very confused right now. No solution seems to work I thought maybe you guys know some answer to that problem.
Any tip and help is greatly appreciated.
Best regards
Martin
I am using a Macbook Pro, Snow Leopard v10.6.6 (10J567)

No one?

Similar Messages

  • Trackpad configuration lost after session login

    Hello,
    I've esperienced the following problem. After login, the magic trackpad configuration is lost.
    I have to go to system preferences then trackpad and click twice on one finger -> tap to click.
    Does anyone experienced the same problem ?
    Thanks for help
    Franck
    Config : Imac intel + lion

    Hello,
    I've esperienced the following problem. After login, the magic trackpad configuration is lost.
    I have to go to system preferences then trackpad and click twice on one finger -> tap to click.
    Does anyone experienced the same problem ?
    Thanks for help
    Franck
    Config : Imac intel + lion

  • Podcasts lost after each iTunes restart.

    I have posted this in the general forum but I think I'd repost here since it's better placed. Sorry for the repost.
    Every time I open iTunes, I've lost all my podcasts. They're there, on the hard drive, but iTunes seems to "forget" that has those subscriptions. I have to manually add the folder to recover the podcasts, plus hit "subscribe" again after that to have the podcasts updated.
    This has been happening since 7.3 and now with 8 still happens. I tried to manually add the folder as instructed in some threads but it does not help. Can you guys help?
    thank you

    I finally figured it out myself. My "Podcasts" directory under the iTunes folder had a problem with permissions that would make it read only
    It had actually gotten corrupted, not allowing even the machine administrator to set ownership or change rights. After a few hours of messing with it, a chkdsk /f made the folder disappear so I could clean reinstall and keep my podcasts.
    Anyways, I just thought I'd share in case somebody experiences a similar problem.

  • Password gets lost after each session...ideas?

    Each time I start a new session (logging in or restarting), I am unable to refresh any of my calendars until I retype the pw for the server I am using FOR EACH calendar. This is not what one might call "convenient."
    Can anyone suggest a reason for this or a solution?
    Once the pw has been entered, I can update to my heart's content.

    Had the same problem. Found a solution that seems to work for more than just this problem.
    1. Delete all subscription calendars (that's having the problem) in iCal.
    2. Open keychain access (/applications/utilities/keychain access)
    3. create a new key chain. Give it a name and password
    4. make this new key chain the DEFAULT key chain (right click, select make default).
    5. Logoff or restart computer
    6. Open ical and add the subscriptions back. iCal should prompt you to add passwords to your new keychain.
    This worked for me. Also worked for my mail accounts, and my iChat!
    Good Luck!

  • 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

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

  • I have lost saved logins and passwords and some saved cookie info after each Firefox update

    I have lost various saved logins passwords and saved information in websites after Firefox updates

    You may loose a few things, but you are doing great.
    These can't get your data back, but will help in the future.
    These add-ons can be a great help by backing up and restoring Firefox
    '''[https://addons.mozilla.org/en-US/firefox/addon/febe/ FEBE (Firefox Environment Backup Extension)]''' {web link}
    FEBE allows you to quickly and easily backup your
    Firefox extensions, history, passwords, and more.
    In fact, it goes beyond just backing up -- It will actually rebuild
    your saved files individually into installable .xpi files.
    It will also make backup of files that you choose.
    '''[https://addons.mozilla.org/en-US/firefox/addon/opie/ OPIE]''' {web link}
    Import/Export extension preferences

  • Tried to fix spotlight indexing and lost my entire drive and backup; can you help me find them?

    Hi,
    I am in a complete crisis. If anyone can help me, I'd be very grateful.
    I tried to correct my Spotlight indexing by using a combination of the sudo mdutil -E / , sudo mdutil -i on / , and sudo rm -rf /.Spotlight-V100 commands from the terminal.
    I am not sure what happened, but the computer went into an interminable color-wheel and, when I shut down and rebooted after an hour or two, I found that both my main drive and my backup drive had severe problems.
    DiskUtility volunteered to correct these. I ran it on my main drive and found that my entire directory appears to have been erased.
    Disk Warrior cannot repair.  Nor can TechTool.  Both declare that the directory structure is now beyond repair (which they also say of my former backup clone).
    My main drive now has barely nine files left - and a handful of empty folders:
    file:///Volumes/Eric's HD/Library/Application Support/
    file:///Volumes/Eric's HD/Library/Application Support/CrashReporter/
    file:///Volumes/Eric's HD/Library/Keychains/System.keychain
    file:///Volumes/Eric's HD/Library/Preferences/com.apple.TimeMachine.plist
    file:///Volumes/Eric's HD/Users/ericcolvin/Library/Frameworks/
    file:///Volumes/Eric's HD/Users/ericcolvin/Library/Preferences/com.apple.Terminal.plist
    file:///Volumes/Eric's HD/Users/ericcolvin/Library/Preferences/com.bittorrent.uTorrent.plist
    file:///Volumes/Eric's HD/Users/ericcolvin/Library/Preferences/com.apple.finder.plist
    file:///Volumes/Eric's HD/Users/ericcolvin/Library/Autosave Information/
    file:///Volumes/Eric's HD/System/Library/CoreServices/boot.efi
    file:///Volumes/Eric's HD/System/Library/Caches/com.apple.kext.caches/Startup/
    file:///Volumes/Eric's HD/System/Library/Caches/com.apple.kext.caches/Directories/System/
    file:///Volumes/Eric's HD/System/Library/Caches/com.apple.kext.caches/Directories/System/Library/Exten sions/KextPropertyValues_OSBundleHelper_i386.plist.gz
    file:///Volumes/Eric's HD/System/Library/Caches/com.apple.kext.caches/Directories/System/Library/Exten sions/KextIdentifiers.plist.gz
    file:///Volumes/Eric's HD/System/Library/Caches/com.apple.kext.caches/Directories/System/Library/Exten sions/IOKitPersonalities_i386.ioplist.gz
    file:///Volumes/Eric's HD/System/Library/Caches/com.apple.bootstamps/0E6271FF-3F33-3661-9B4A-38AFF32D4 860/
    file:///Volumes/Eric's HD/Applications/
    file:///Volumes/Eric's HD/net/
    file:///Volumes/Eric's HD/home/
    Though I did not run any file repairs on the back up drive, it has also lost all of its files (it shows just one remaining
    file:///Volumes/Eric's Backup/System/Library/CoreServices/boot.efi - whatever that is).
    FileSalvage is now beavering away, attempting to scavenge some 350Gb of applications, e-mails, photos, iTunes, and movies (most of which it is unable to name). But these will all be unlabelled and randomly organised by extension type. These could take months to sift through and the list is almost certain to be incomplete. I have no other backups of my system apart from a two year old clone.
    Please tell me. Is there anything I can do to get back my lost directory structure?
                           Might there be some use of an Undelete routine that might recover the directory alone and thus allow me to salvage either disk?
                            I don't even know what sort of extension to hunt for in order to attempt such a restore
                           - nor how I might drop it back into its correct spot on the volume.
    All suggestions gratefully received.

    Thanks, guys.
    Yes, FileSalvage seems able to retrieve a vast jumble of unnamed "junk files," a tiny percentage of which are probably highly valuable to me. The problem will be finding them amongst the jumble. It could take weeks. ITunes files and MP3s are more promising, as it seems to have been able to reconstruct the files' names - and even cover art - from their metadata.
    No. TechTool Pro wrote nothing at all. Sadly, though, I had allowed Disk Utility to reduce the number of threads or leaves or something in the volume directory, before I realised the gravity of the situation. It has thus made a very small alteration to my main drive (resulting, no doubt in the creation of those 9 system files and their containing folders). But the back-up drive had nothing further written to it since the apparent deletion of the volume.
    I downloaded a freeware program called TestDisk which claims to analyse drive partitions. The partitions on each of my two physical drives (the internal and the backup clone) were not apparently affected - just the total loss of the volume directory structure on the boot partition in each case. So, would this be the wrong tool for the job?  http://www.cgsecurity.org/wiki/TestDisk  It does claim to be able to "Rebuild NTFS boot sector." I don't really know what that means. Can anyone tell me whether a rebuilt boot sector will enable me to recover a deleted volume directory structure?
    Meanwhile, I am also running a trial version of Stellar Phoenix, which claims to reinstate "lost/deleted volumes."  It claims to have "found 6 lost/deleted volumes" already - after five hours, during which it has scanned about 5% of my 1.5 T external drive. So I suppose it may well take days to finish scanning. Then, I expect it may ask me to buy a serial code in order to proceed.
    Does anyone have experience with Phoenix, or understand the jargon about lost/deleted volumes? Once I've bought the full version, is there a good chance it will actually reconstruct the whole volume as it once was - or is it more likely just to scavenge scores of thousands of nameless file snippets as per FileSalvage?
    I don't have a problem with paying the boffins at Stellar if they are actually able to save me months of sifting through random unnamed files in order to locate the ones I've lost.

  • 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

  • Lost disk space after each reinstall.

    I've had to reinstall leopard on my macbook three times in the last week for different reasons. After each reinstall(erase and install) it appeared that I lost a little more GB to the HDD. I have a 250GB HDD, and I know it actualls reads as 232.87, but without uploading any media and only using the reinstall disks that came with the box, I have only 218 or so GB. Is this normal? I can't find the numbers anywhere; they just don't add up.

    Anthony Turtzo wrote:
    I can't find the numbers anywhere; they just don't add up.
    My guess is that you have added up the sizes of the folders visible in Finder at the root level of the drive (Applications, Library, System, & Users) & compared that total to the total space used on the drive. The two numbers will not match because there are also hidden files & folders at the root level of the drive that Finder does not normally show. The hidden items are necessary for the proper operation of the Mac & in normal use are managed by the system. Since users should not tamper with them directly without good reason & it requires expert knowledge to do so without breaking anything, they have been made invisible in the Finder view.
    It is normal for the drive space used by these items to fluctuate, & for the total to grow somewhat after first installing the OS. Some of the items contain temporary files that are created & destroyed as needed. Some contain usage, crash, & other informational logs that are managed by routines that the system automatically runs periodically to keep their total from becoming too large. Others contain initialization data gathered over time that the system uses to start up or to run processes efficiently.
    Thus, there is no fixed correct number for their total size since that depends on the history & current state of the machine. On my iMac G5, one large hidden folder ("var") currently uses about 1.05 GB of drive space, but consider that only a ballpark number since it may be considerably different on different Macs at different times.
    If you are still concerned about the health of the drive, especially that something is eating up disk space unnecessarily, then run Disk Utility to check it. In the "First Aid" tab select your drive & click the "Verify Disk" button. If this reports no problems then you can be pretty sure there is nothing to worry about.

  • Spotlight indexing very slow after upgrading to 10.7.5

    SInce I have updating to 10.7.5, the spotlight indexing of my hard drive is very slow : only 40% has been performed in two days.
    Does anyone have similar problems after upgrading to 10.7.5 and know how to fix them ?
    Here are some excerpts of log files :
    mdworker(7618) deny file-write-create /opt/local/var/macports/home/Library/Preferences/com.apple.LaunchServices.plist .lockfile
    Process:         mdworker [7618]
    Path:            /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Support/mdworker
    Load Address:    0x10dfb3000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [7616]
    Date/Time:       2012-09-25 06:05:42.300 +0200
    OS Version:      Mac OS X 10.7.5 (11G56)

    You're not the only one. I've been re-indexing on and off for the last four days to no avail. I had to call Apple today and was put through to a senior technical advisor. After doing a data capture for them I was told that they should be able to come back with an answer within the next two days.
    It's worth giving them a call to let them run through the clearing caches process with you if you haven't done that already. Remember that using your machine whilst it's indexing also slows the process down.
    I will let you know when they come back with an answer but I hope by t would hahen both of our machines would have finished re-indexing by then...

  • I have music loaded from cd's. They were intact after each sync. After a iTune upgrade, I lost all the music at sync. Can I restore them from old backup in iCloud ?

    I have music loaded from cd's. They were intact after each sync. After a iTune upgrade, I lost all the music at sync. Can I restore them from old backup in iCloud ?

    Unless you'd signed up to iTunes Match then they won't be in the Cloud, only music purchased from iTunes (if you are in a country where music can be re-downloaded) will be there. Have you not still got it on your computer and/or on a backup which you can use to sync it back to the iPad ?

  • Many logins & passwords were lost after last update

    Automatic login and passwords were lost after the last firefox update. Or should I say would not work until I re-entered them.
    A search found they were still there, plus the new entries I saved.
    Other logins were lost totally, no passwords were lost.
    I did send an immediate report to tech support but heard nothing.
    Is it safe to update the new version or am I having to re-enter my logins and passwords again.
    I have used firefox for many years as my main browser, I mostly only want to use a different browser when I want to open two different email accounts.

    Websites remembering you and automatically log you in is stored in a cookie.
    If a website decides to invalidate such a remember-me cookie after noticing an update (e.g. 6.0.1 to 7.0.1) then you will have to re-enter your credentials to create a new cookie.

  • Blue Screen and data lost after rescue n recovery during F11 operation

    when I start my T61 Laptop, i get complete blue screen with no addition error window. Pl. suggest solution to this problem.
    Moderator edit: problem added to subject line for clarity. 
    Message Edited by Agotthelf on 21-07-2009 10:40 AM

    HI
    Thanx for replying . Now the problem of immedietly solved when i booted my laptop with F8 . But the new problem arises. When I logged in, the system starts fine but when I run rescue n recovery option from thinkvantage button , the laptop restarts and then all errors shown. Like "c_1252.nls" file is missing or corrupted. This is the first messege I got while booting. Then I booted with F11 for rescue n recovery. I recovered file c_1252.nls from backup folder on harddrive. But when i restarted again the new c_0437.nls shown missing and this i got so many times after each n every rescue n recovery options. Then I again rescued all the files in system32 folder and restarted my laptop. Which restarts good uptill it asked for domain password . But when i clicked to enter the password the error messege shown " Diskeeper not present" and subsequently "SQL server is disturbed" like that . But the login successful and when the desktop arises the windows intstaller window shows but no further processing even i waited for 15 min. And above all  I lost all my data saved in one n only drive that the LENEVO provided with OS.  NO partiton. PL. suggest any solution this . Is it possible to recover my data since I didnt make any backup ? 

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

Maybe you are looking for