Spotlight and Time Machine broken after restore/upgrade

I've found a few similar threads to this but none of those solutions has worked for me.
Two things happened at nearly the same time, so I don't exactly know the source of my problem:
I upgraded my old MacBook Pro (approx. Oct 2010, 2.66GHz I think, 300GB-ish HD) from Lion to Mountain Lion
The hard drive on my old MacBook Pro developed a terminal fault, so I had to buy a new one (8GB, 750GB HD) and restore a month-old Time Machine backup from my external drive.
I can't remember whether my last Time Machine backup to my external drive was before or after I upgraded to Mountain Lion.
Now I'm on OS X 10.8.2 on this new machine and I have two problems that seem to co-exist for a lot of other people too:
Spotlight won't index: this is f***ing infuriating, I love spotlight and I use it all the time. When I first restored from the TM backup I think the old index restored with the backup as I did get a decent number of search results (both in spotlight and in MS Outlook), but new files didn't seem to get recognised. I tried adding my hard drive to the exclusion list and removing it again in an attempt to get it to rebuild the index, but all that did was wipe the old index without building a new one, so now I get no spotlight results whatsoever. I tried this solution and sadly it hasn't worked either. Basically I can't search for anything. Even applications (which I like to launch from spotlight) don't appear. All I get is "estimating indexing time", and it never gets any further.
Time Machine won't back up: the first time I tried to backup my new machine it got a few hundred megabytes in before stalling; then a few hundred kilobytes in the next time I tried; and now it just doesn't get anywhere at all. The external drive I'm trying to backup to is recognised fine, I can see all the other files on it, and Time Machine seems to know that it's there, but the backup gets nowhere.
There are reports of this kinds of crap all over the Apple Support forums, but no definitive answer, especially for 10.8.2.
I could really do with some help on this. I need a backup before I screw another laptop, and I need spotlight to survive day-to-day life.
Thanks,
Craig

Hi Craig - I had the exact same problem - I'm using an old early 2009 MacBook Pro upgraded to 8 Gb Ram, 1 TB internal Hitachi HD, 10.8.2 - tried the fixes suggested - got it to work with these steps- everybodies mileage is different but hopefully it works for you as well.
a) I repaired disk permissions with Onyx (free utility)  and then  started  up with Command-R using Disk Utility to repaired/check the Volume (harddisk checked out fine but the volume needed some minor repairs )- Onyx repair disk permission seems to go deeper -had to reinstall some apps - don't know if this solved it-seems to bring it back to the default state - you might get away with doing all from Disk Utility (but starting up with  Command-R)
b) restart from my internal hd
c) downloaded the 10.8.2 combo update ( not the incremental shell update or whatever you call it which automatically gets installed with software update - combo update installs everything fresh from the .0 version)
d) with  Onyx  I deactivated spotlight and erased the spotlight index
d) restart
e) started TM backup - prep took pretty long 30 minutes but then 450 GB got backed up in 6 hours to my external HD which is fast enough for me
f) activated spotlight and 450 Gb were indexed in 9 hours or so
g) for 2 days everything runs fast and very responsive
best,
Franz

Similar Messages

  • Time Machine Backups after recent upgrade to Mountain Lion

    Basically to keep a long story short - i need to take my computer in for repair tomorrow. I recently did an upgrade to Mountain Lion a day or two ago. I haven't done a Time Machine backup until today (a couple days after i upgraded to Mountain Lion) because i wanted to make sure that my previous TM backup (Snow Leopard 10.6.8) was the most up to date and best update that i could revert back to if i had any issues with Mountain Lion, or any application compatibility, etc etc.
    I don't have any broken applications and it seems like Mountain Lion is running better than Snow Leopard. However, as i said - i'm taking my computer in for repair tomorrow, i would like to know that i have the most up to date Time Machine backup with the new Mountain Lion so that when i restore it back from my Time Machine backup after i get it back from repair, i won't have any issues with the migration, which could potentially lead me into more technicalities.
    I have a 500GB Harddrive, with about 70GB left of free space....I did the initial backup prior to upgrading to Mountain Lion, and it upgraded 400+GB of info, now, since Mountain Lion - the first backup with Mountain Lion initially said 46GB - then it went down to 14GB by the time it was all said and done....so what exactly did it back up?
    Did it back up all the necessary files to keep Mountain Lion running smoothly when i restore it back to the way it was after i get it back? Did it not back everything up that it needs to? Is it safe to erase my internal drive and do a clean installation so i can take it in, and not worry about not being able to migrate things back over or applications not working correctly?
    When i get it back, i presume it will come with Mountain Lion back on it and i can just boot up into the Recovery Disk and restore it from a Time Machine backup that way, correct?
    Thanks for the help.
    - Jason

    I received the same error and experienced the same issue that you have described but after performing a Time Capsule soft reset and then toggling the TM Off and then back On I was able issue a backup now and see my previous backups.
    Here is the link to where I posted my fix; https://discussions.apple.com/message/19069543#19069543. Someone else had success using a different method. The only comment / complaint that I have since the ML OS X upgrade is that TM now takes at least 20 to 30 seconds before I can click/select a backup.
    I hope this helps.

  • Time Machine Bug after Restore

    Hi all,
    I've been learning Time Machine and will share two possible bugs if it is helpful.  I am working on a 2011 MacBook Pro, upgraded to Mountain Lion some months back, with 50 GB data on SSD being backed up to and restored from a LaCie SSD 80 GB partition so the speed is very nice: 14 minutes for initial backup and 7 minutes for a Reboot + Command + R restore.
    Bug #1.  Both (initial) backup and restores begin with large 60 minute estimated times in Time Machine Prefs Progress Bar but, once it gets going, finishes in 14 and 7 minutes respectively.  If symptom is due to some quadratic journal searching algorithm, it may explain why APL-CARE warned me about potential 16 hour restores and could be a bug.  If it is due to Time Machine just counting what has been transferred so far, then maybe not a bug (but maybe a possible enhancement request).
    Bug #2.  It appears that the first time Time Machine runs after a Cmd+R restore, it tries to rebuild an entire journal or record of what it has and, if you interrupt this initial backup, you break Time Machine.  The next time you try to backup, Time Machine thinks Everything needs to be backed up (even though your disk is identical to what it just restored), and it Fails in my case with message "Time Machine couldn't complete the back to [my LaCie drive because my 50 GB of data is already there and it thinks it needs a full 50 GB more]" in so many words.  APL-CARE (and its expert advisor) tried to call this a feature and sent me to your article HT3275 but that seems like a different issue.  Since I did not believe Time Machine was so stupid, I ran the sequence again and carefully avoided interrupting Time Machine during its initial backup following my Cmd+R restore and, indeed, it took about 8 minutes to backup 4.5 MB (and rebuild whatever it does that first time).  So this feels like a straight-up bug, Time Machine should scare me with a popup if I interrupt it while it is rebuilding its critical list for the first time after a restore.  If APL-CARE were correct, it would mean everyone loses all history after a restore, everyone needs to Erase their backup disk and start from scratch, and methinks that too would be a bug.
    Hopefully this is helpful, Time Machine is otherwise very cool and I love the Star Trek GUI. 
    Regards,
    Dave.

    And this is an ERROR in time machine.  I just did a test restore again, went quickly, then Time Machine is GONE, GONE, gone trying to restore 5MB, waiting over an hour when a fresh backup takes about 15 minutes.
    So only solution is DESTROY all my backups, then start over.  Really dumb, and this page has no option to change my post back to a question, also really dumb.
    I am going to swear now:  cr*p.  OK.  Fix your **** software please.  I'll deal with workarounds till then.
    -dave

  • Time Machine error after restoring all data

    Sorry, I've tried to run through various trouble shooting guides on Time Machine (notably here http://pondini.org/TM/C4.html etc) but haven't been able to work out a solution.
    I just had my iMac harddrive replaced and earlier did a full restore of the harddrive from my Time Machine backup drive.
    Time Machine, rather than deleting the old backups on the disk, is now giving me the error message
    "This backup is too large for the backup disk. The backup requires 564.63 GB but only 521.89 GB are available."
    I backed up to Snow Leopard 10.6.8. I just upgraded to Mountain Lion 10.8.3 because there were a couple of comments online that suggested that might help resolve the problem (unfortunately it didn't)
    It seems from articles I've read that this is a known issue that occassonally happens when a full restore happens and Time Machine can't associate the new harddrive with the old backups.
    One solution seems to be to use disk utility to reformat the external harddrive and start again, but that seems slightly like using a sledgehammer to smash a nut. Is there a less dramatic solution? Is there a easy way to just associate the two drives with one another again?
    Many thanks in advance for any help you can offer, and apologies if I've missed a relevant/ helpful thread somewhere else on the board.

    "Reconnecting" to your backups

  • Time machine broken after 10.9.5 update

    Time machine will not run after installing 10.9.5.   TM was successful 10.9.4 20 minutes before I updated.  When TM does a backup, the dialog says  "711GB free of 1TB" and "backing up X of 6GB".  After a while it says "time machine unexpectedly ran out of disk space" and quits.  This happened twice.  The third time TM tried to backup, it took 30 minutes to get to "backing up 90K of 6GB", so I gave up.
    Anybody else having issues like this?

    Hey northsidemike,
    Thanks for the question and detailed information. I understand that you are experiencing issues creating a Time Machine backup after updating to OS X 10.9.5. The following resource includes multiple links for troubleshooting Time Machine issues. I’ve included a few that are related to your issue:
    OS X Mavericks: Time Machine problems
    http://support.apple.com/kb/PH14187
    Time Machine is slow or seems stuck
    If your Time Machine backup disk runs out of space
    If Time Machine is slow
    If Time Machine remains in the “preparing” stage
    Thanks,
    Matt M.

  • Time Machine broken after 10.6 server upgrade

    I recently upgraded our Mac Pro running 10.5 Leopard server to 10.6 Snow Leopard server, I just popped the disk in and ran the installer. The upgrade seemed to go fine, this is just a file server, and everything seems to function just as it had in OS 10.5, except for Time Machine. TM did not pickup where it left off with the internal TM drive for the server (not entirely unexpected). With no luck I've tried:
    Erasing and repartitioning the drive (after turning TM off and deleting the preference file)
    Removing the drive and erasing and partitioning on another computer, then trying TM through a USB connection (after turning TM off and deleting the preference file)
    Below is the common error dialog and part of a log file. If I were to remove the folder/file listed in the log next time it would just be another file. What is consistent is that it doesn't seem to like what's in the Shared Items folder (the sharepoints users attach to).
    Can anyone tell me how I might fix this?
    --- Sample Log Exerpt ---
    com.apple.backupd[23587]  Error: (-41) SrcErr:NO Copying /Shared Items/OpenJobs/∂ Jamie's Jobs/misc./Flash/Ex_Files_FlashCS3_BTB/Exercise Files/Chapter 09/03/final/classes/com/lynda/audio/mp3/Mp3Player.as to /Volumes/Server_TM/Backups.backupdb/travelxserve/2011-06-07-091921.inProgress/D 895F019-A328-45B1-A7D4-836231E1A817/ServerHD/Shared Items/OpenJobs/∂ Jamie's Jobs/misc./Flash/Ex_Files_FlashCS3_BTB/Exercise Files/Chapter 09/03/final/classes/com/lynda/audio/mp3
    com.apple.backupd[23587]  Copied 238 files (116.7 MB) from volume ServerHD.
    com.apple.backupd[23587]  Copy stage failed with error:11
    servermgrd[81]  servermgr_backup: TimeMachinePostBackupHook called.
    servermgrd[81]  servermgr_backup: TimeMachinePostBackupHook done.
    com.apple.backupd[23587]  Backup failed with error: 11

    valoo wrote:
    I deleted the newly created sparsebundle. I also realized that the computer name had been changed and I changed it back to the original one. Here's the new problem. The TM says that I only have 127 GB and the amount of space needed to back up the disk is 140GB. I don't understand. It almost seems like it is trying to duplicate the entire backup. And this time around, I don't even see any new sparsebundle. I am stuck here.
    Something caused TM to decide to start a new "sequence" of backups, as if you'd gotten a new Mac. That means a new, full backup to start with. The only thing that seems to have worked for some folks is a Restart. So if you haven't done one since the latest changes and failed backup attempt, it's worth a try.
    If it still wants to do a full backup, you can't prevent it.
    Depending on how much space you have on the TM drive/partition, your only choice may be to delete the "old" sparse bundle and let TM start over.
    You may be able to delete some of the older backups to make room for the new, full backup, but that's tedious and time-consuming (see item #12 of the Frequently Asked Questions *User Tip.)*
    But that still leaves two problems: you'll have to manually "compact" the sparse bundle via Terminal to shrink it; and you'll have to continue to delete old backups this way (and manually compact them) to make room for new ones. Since TM is treating them as if they were from a different Mac, it won't delete them automatically, but will delete the oldest backups from the new set instead.

  • Time machine freezes after restore using migration assistant

    after an erase/install done in an Apple Store, I restored my Mac Book from the Time Machine using the migration agent.
    To do this I created a temporary admin account and performed the Restore of all users and contents in the backup.
    Now logged in as my old user ID the time machine backup starts and identifies that the entire MacBook content needs to be backed up.
    TM Backup runs through the prepairing stage and reaches the "Baccking up 'xxx' MB from 'yyy' GB" message.
    Then it gets stuck after 120 MB has been backed up. I did run the backup for 2 entire nights in the 2nd night it got stuck after 0 kB had been backed up.
    What to I need to do to get TM running again?

    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console 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 Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the search box.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • Time machine issues after HD upgrade

    I replaced and upgraded my internal HD today in my MacBook Pro (OSX 10.6.5). I restored OSX from my time machine backup to this new drive.
    However, when I next tried to run Time Machine, it tried to back everything up on the new drive, which is about 150Gb of data. Is there any way to avoid doing this and just have time machine back up the files that have actually changed since the last backup? It seems a senseless waste of space on my backup HD to have essentially two copies of everything on my HD...

    For Time Machine it is essentially a completely changed version of your old HDD, so it does backup the changes. Only that everything changed.
    One solution is to let it back it all up and let it delete older backups when it needs more space and the other is to delete the existing backup and save some disk space...

  • Time Machine Problem after restore

    I had a hard drive crash, and after repair, I restored from a time machine back.  Everything seemed fine, although a few sets of photos were missing from iPhoto.  After things seemed to be fine I have started doing time machine backups again. 
    My problem is that they take a very long time to complete.  I expected the first one or two to take a long time, but not since then.  I have given it weeks to make sure that it has had enough time.
    Every single time the verifcation stage shows 10s of thousands of files.  Even if I have not made any changes.  In my console log I see:
    6/7/12 11:17:34 AM
    com.apple.backupd[61578]
    Node requires deep traversal:/Users/dersh/Pictures/iPhoto Library reason:contains changes|must scan subdirs|fsevent|missed reservation|
    For every single backup.  It seems like it is not actually fixing this.  From googling around, I expect that this should take a long time the first time or two, but then should finish.  It then says that it is backing up about 600 meg.  The exect number seems to change with each backup, depending on what I am doing, and what changes I have made.  But even if I do nothing, it still is in that range.  It then appears to complete, although it takes a long time.  I would guess that since it is doing the deep traverse it then has to match up a bunch of files, so doing the actual backup takes much longer then it should.  For example it might sit for a good few minutes at "backing Up:  105.2 MB of 580.2 MB" Then it moves on to 107.6.  Finally, the cleanup takes a very long time.  So overall each backup is taking 10s of minutes.  Even if I am not doing anything with the computer. 
    I am using a firewire drive directly connected to the computer.  I have done a repair of the external time machine drive, and have done a verify of the internal drive, with no issues.
    I see that I have plenty of space on the external drive. 
    So, it seems like what is happening is that it doesn't "know" that it has done a succesful backup of iPhoto, each time so it does a deep traverse  and then backsup something like 600 meg of data from there.  How can I get it to "understand" that it has done this?  Can I force it to do it once correctly, so that it will take?
    Any other suggestions?

    UPDATE
    Happen to have a QNAP NAS from work at the house which has Time Machine support and can select and initiate a backup there, no problem!
    So, it's something about the Mac Mini or drive? I didn't do anything to the Mac Mini in the process other than removing the USB drive and plugging it back in.
    As far as the drive, I dumped it and re-partitioned it with two partitions one for the Mini and one for the iMac. The Mac Mini is backing up to it locally, no problem.

  • Time Machine problem after restoring to a new HD (after my original HD failed)

    I am running Lion 10.7.5 on a MacBook Pro Late '11
    My HD was getting SMART errors, so I did a complete back up using Time Machine using a WD My Passport 1TB external, and then sent my MBP to Apple for HD replacement (under my Applecare plan).
    I collected it yesterday and restored my system using Time Machine (using the data from my external HD) and everything was restored perfectly, which was great,
    However, I'm now encountering a problem after plugging my external HD back into my MBP on the new system. Rather than Time Machine doing a swift 'top up' back up, it appears that TM is attempting to do a full back up. (I have 300GB and it took nearly 24hours to backup on the faulty drive) Is this normal after installing a new HD? Bearing in mind the Time Machine data is still on my external drive?
    It's also appearing to be taking FOREVER to do this entire back up again. It is stuck on 'preparing back up' and when I do get some movement, it's doing a couple of KB's at a time and with no genuine back up progress.
    Fundamentally, I just want to just top up my Time Machine back up without having do a complete back up, again. (which doesn't actually seem possible, viable at the min)
    Any help / support would be much appreciated

    AFAIK, it'll do that since the HD has a different UUID and the old TM backup won't recognize it. See Pondini's TM FAQs, for starters.

  • Does Time Machine reset after restore?

    Hello,
    Suppose I have Time Machine backups for the last 6 months on an external hard drive. Suppose I restore my entire system to 3 months ago using TM. Will Time Machine still keep all the backups that were made AFTER that date,  Or will TM treat that date that I restored to as the most "current" date, and delete all the backups created after it? What happens when TM starts to run again after restoring? I ask because I don't want to do anything that might cause any of my backups to be inadvertently deleted.
    Best,
    James

    It will keep the more recent snapshots.

  • Spotlight and Time Machine

    According to my console log file, Spotlight is having trouble with my Time Machine volume
    Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in openindexfile:ftruncate error: 22, size: 32768, live.0.indexIds
    Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8/li ve.0.; needs recovery
    Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
    Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
    Jul 1 18:48:25 StevesiMac mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8)(E rror) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/9A15E9F6-D06F-4FB8-9841-7691A1A7A2A8
    The net result is that the drive always shows as busy. I can't eject it and I get the "Failed to create backup index" error message.
    Does anyone know of a fix for this. If I used a utility such as Spotless to turn indexing off on the TM volume, will it also disable my ability to use TM to restore a file since the drive is no longer indexed?
    Thanks
    BTW, just happened in 10.5.4, but first noticed the symptoms is 10.5.3.
    Thanks
    Steve

    there is no need to have TM drive indexed. it will only confuse both TM and spotlight and is likely to cause problems of the kind you are having. add it to spotlight's privacy pane. that will have no effect on using spotlight from inside TM interface to search backups.

  • Error-1 time machine backups after lion upgrade

    I upgraded to Lion on both my computers. My iMac Time Machine Backups are fine - it's connected by firewire to an external hard drive.
    BUT my Macbook Tim Machine Backups are wireless using our Time Capsule and the backups are stored on the Time Capsule.
    Since upgrading, The backups fail & I get this error: The backup disk image “/Volumes/Brunnertime/LittleOne (2).sparsebundle” could not be accessed (error -1).
    Just like so many other unhappy Lion users.
    One positive abberation - Last night, I went into Time Machine Preferences, re-selected the appropriate backup disk (our Time Capsule), entered the password, started a backup and VOILA it backed up fine. All night long, it did hourly backups.
    This morning? Once again, the backups are FAILING with that same error - The backup disk image “/Volumes/Brunnertime/LittleOne (2).sparsebundle” could not be accessed (error -1).
    Plus, now there are NO backups on the disk. Huh?
    At this point we are disgusted that both Lion and iCloud (that's another longer story) were released before they should have been. Too many bugs.

    Hey, finally I found a permanent fix for this issue. I read about it at another Apple Discussions Forum, but right now I don't remember where.
    It worked for me at least. In my case it seems that some Western Digital (WD) software was causing the issue. I just uninstalled WDSmartWare from my iMac using that application's own uninstaller, rebooted my Mac and, finally, after months of calling Apple Support with no luck, it all started to work normally again, so check if you have some WD software running on your Mac. In my case I didn't even need that WD software, as I had it because I used to back up to a WD Drive which I don't use anymore since I bought my Time Capsule.
    Feel free to reply if you require any further assistance.
    Good Luck.

  • Time Machine Backup After HDD Upgrade

    I recently updated my drive on my MBP with a larger size where I successfully cloned the system from the old drive over the new one with Carbon Copy Cloner to safe me the hassle of the migration. The task was flawless and transparent to the system and me--as a user, except for Time Machine.
    I've maintained a regular backup with Time Machine on a 500gb external drive, instead of transparently picking the backup where it left off, Time Machine is attempting to redo the backup as a complete new set for the new drive where I no longer have enough space?
    So the question is:
    - Is this behavior by design?
    - Is it possible to trick Time Machine to continue backing up without starting over? So the 6 months old worth of backup data is intact since this is the same set of data?
    Thank you.

    wiriawan wrote:
    I recently updated my drive on my MBP with a larger size where I successfully cloned the system from the old drive over the new one with Carbon Copy Cloner to safe me the hassle of the migration. The task was flawless and transparent to the system and me--as a user, except for Time Machine.
    I've maintained a regular backup with Time Machine on a 500gb external drive, instead of transparently picking the backup where it left off, Time Machine is attempting to redo the backup as a complete new set for the new drive where I no longer have enough space?
    So the question is:
    - Is this behavior by design?
    yes.
    - Is it possible to trick Time Machine to continue backing up without starting over?
    no. TM will do a full backup after hard drive cloning. there is no way around that. you have to either delete some old backups (this can be done from TM interface) or reformat the TM drive and start backups from scratch or use a different backup drive.
    So the 6 months old worth of backup data is intact since this is the same set of data?
    Thank you.

  • Spotlight and finder not working after Yosemite upgrade

    Hi,
    I just upgrade to 10.10.1 from 10.8 on a Mid 2012 Retina macbook pro, 2.7Ghz i7, 16GB RAM, 750GB SSD drive.
    Since upgrading spotlight and finder have stopped working.  When I first upgraded I noticed it worked very briefly and found some of my applications, but now nothing.  The only thing it does is find the definition of the word I am searching for,
    I have
    gone in to sys pref > spotlight added and remove all folders and rebooted the machine
    gone in to sys pref > spotlight > privacy tab and ensured no folders are in that pane
    gone in to sys pref > spotlight > privacy tab and added "documents folder" closed sys prefs rebooted and then removed "documents" folder to try and trigger a re index
    gone to terminal and typed "sudo mdutil -E /" which should erase and rebuild the index but i get the error back "Error: Index is already changing state.  Please try again in a moment"
    gone to terminal and typed "sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist" and then typed "sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist"
    go to disk utility and verified my disk which comes back as showing no errors
    logged in as another user but spotlight and finder still not working
    Any other ideas my laptop is useless for work if I can't find anything,
    Thanks

    unfortunately I this is still not working, thanks for the link Eric i tried those options, but still the problem remains.
    I can clear the cache and re index my mac, and while the system is re indexing spotlight works and I can find material during the reindex.  This is obviously limited to the files that have been indexed at the point of using spotlight.
    Once indexing has finished if I go to spotlight and try to search for anything, there are no results only the dictionary appears.
    At the moment I have to delete the index cache every morning to trigger a re index so I can work, this is terrible and the worst upgrade experience I have had with any OS mac or windows

Maybe you are looking for