Skip navigation
This discussion is archived

Time Machine "mds" Error

3307 Views 13 Replies Latest reply: Oct 29, 2008 4:14 PM by Maxwell’s Demon RSS
Maxwell’s Demon Calculating status...
Currently Being Moderated
Oct 29, 2008 11:16 AM
Time Machine has been running for the past several (more than 4) hours trying to complete a backup that should've taken maybe 5-10 minutes. The progress bar in the prefs panel is at the end, and indicates that TM has backed up 2.5 GB of 2.5 GB. However, the bar is still active (the blue color is still "flowing").

Console has been repeating the same error message:

"mds[22]: (Error) Import: importer:0x887400 Importer start failed for 501
(kr:268435459 (ipc/send) invalid destination port)"

I noticed that the error reporting began about a half hour prior to TM
initiating its scheduled backup.

Here's the history:


Oct 29 09:25:24 maxwells-imac /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[3776]: SessionGetInfo(0xffffffff) -> -2147418111
Oct 29 09:25:24 maxwells-imac /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[3776]: GetOurLSSessionIDInit(), returned error 0x80010001, securitySessionID=0x0 attrs=0 uid=501 euid=501. cf Radar 5123589.
Oct 29 09:25:24 maxwells-imac /System/Library/CoreServices/coreservicesd[47]: Client must provide a valid sessionID but passed 0, 0x0/0x0 version=10500000 uid=501 euid=501. cf Radar 5123589.
Oct 29 09:25:24 maxwells-imac /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[3776]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.
Oct 29 09:25:24 maxwells-imac /System/Library/CoreServices/coreservicesd[47]: Client must provide a valid sessionID but passed 0, 0x0/0x0 version=10500000 uid=501 euid=501. cf Radar 5123589.
Oct 29 09:25:24 maxwells-imac /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[3776]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.
Oct 29 09:25:24 maxwells-imac /System/Library/CoreServices/coreservicesd[47]: Client must provide a valid sessionID but passed 0, 0x0/0x0 version=10500000 uid=501 euid=501. cf Radar 5123589.
Oct 29 09:25:24 maxwells-imac /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[3776]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.
Oct 29 09:25:26 maxwells-imac ReportCrash[3777]: Formulating crash report for process mdworker[3776]
Oct 29 09:25:26 maxwells-imac com.apple.launchd[1] (0x10a6c0.mdworker[3776]): Exited abnormally: Abort trap
Oct 29 09:25:26 maxwells-imac com.apple.launchd[1] (0x10a6c0.mdworker): Failed to check-in!
Oct 29 09:25:26 maxwells-imac ReportCrash[3777]: Saved crashreport to /Library/Logs/CrashReporter/mdworker2008-10-29-092524maxwells-imac.crash using uid: 0 gid: 0, euid: 0 egid: 0
Oct 29 09:25:30 maxwells-imac mds[22]: (Error) Import: importer:0x887400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
...
...
...
Oct 29 10:04:50 maxwells-imac mds[22]: (Error) Import: importer:0x887400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Oct 29 10:05:00: --- last message repeated 2 times ---
Oct 29 10:05:00 maxwells-imac /System/Library/CoreServices/backupd[3812]: Starting standard backup
Oct 29 10:05:00 maxwells-imac /System/Library/CoreServices/backupd[3812]: Backing up to: /Volumes/Seagate Barracuda/Backups.backupdb
Oct 29 10:05:01 maxwells-imac /System/Library/CoreServices/backupd[3812]: No pre-backup thinning needed: 4.27 GB requested (including padding), 353.47 GB available
Oct 29 10:05:02 maxwells-imac mds[22]: (Error) Import: importer:0x887400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Oct 29 10:05:32: --- last message repeated 15 times ---
Oct 29 10:05:34 maxwells-imac mds[22]: (Error) Import: importer:0x887400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Oct 29 10:06:04: --- last message repeated 7 times ---
Oct 29 10:06:06 maxwells-imac mds[22]: (Error) Import: importer:0x887400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Oct 29 10:06:36: --- last message repeated 7 times ---
...
...
...
etc.



What does it mean?
iMac (24", 2.8 GHz), Mac OS X (10.5.4)
  • Glenn Carter Level 4 Level 4 (3,360 points)
    Currently Being Moderated
    Oct 29, 2008 11:53 AM (in response to Maxwell’s Demon)
    Max,

    See the first heading in the article below, it explains what may be happing and a suggestion on resolving it.

    *_Spotlight And Time Machine_*
    Forgive the size of the post, but this is what I have discovered regarding Time Machine and Spotlight conflicts. Consider each topic separately. If one topic does not seem to resolve your issue then move on the next.

    *Runaway MDS Process*
    For Spotlight searching to work, it needs to have metadata. Every time a file is created, modified or deleted, the system notifies Spotlight that it needs to update the meta-data store (mds). First, Spotlight (mdworker) seizes the file, determines its’ type, and then assigns an appropriate importer (mdimport).

    While some bits of metadata (modification dates, file type, path name) are easy to gather, most of the interesting data is embedded inside the file. To gather this embedded information Spotlight must use an importer (mdimport), a small plug-in that extracts information from files created by various applications. Each file type has its’ own importer. For instance there are unique Spotlight importers for JPEG, MP3, Word, PDF files and so on.

    It’s the importer’s responsibility to read the data file and construct a dictionary that contains the appropriate metadata. When finished, the dictionary is delivered to Spotlight (mdworker), which then updates the meta-data store (mds). The original file is then released to the system to complete the originally intended action.

    Ordinarily, this process is virtually instantaneous and invisible to the user. At times, however, it can hang, or loop causing Spotlight (mdworker) and the meta-data store (mds) to monopolize the CPU and interfere with other system events like Time Machine backups. The Console logs may report the following over and over again for perhaps hundreds of times.

    +“mds(32): (Error) Import: importer:0x8f8c00 Importer start failed for 503”+

    Eventually, the Time Machine backup may fail with the Console logs reporting

    +“Indexing a file failed” / “Copy stage failed with error: 11”.+

    Or a backup may be completely stalled in midstream, never seaming to end.

    Go to Applications --> Utilities folder and launch Activity Monitor.
    Clicking the “Process Name” column and scrolling down to the “m”s will reveal that one or all of the Spotlight components (mds, mdworker, mdimport) is maxing out your CPU.
    Highlight “mds” and click “Quit Process” in the toolbar.
    In the dialoge box that appears click “Quit”.
    Enter our Admin password and click “OK”

    The stalled backup should now resume and complete. If not, choose “Stop Backing Up” from the Time Machine menu or click the tiny “x” icon in the Time Machine Preferences. When the backup has completely stopped, select “Backup Now” from the Time Machine menu.

    *Waiting for index to be ready (909 > 0)*
    One of the processes Time Machine relies on for accurate backups is the indexing of the backup disk. With this index, Time Machine can quickly search the backup disk for files the user wishes to restore. When a routine backup begins, often the “Preparing…” stage will include a phase that permits Spotlight to update its’ index of the backup disk. Momentarily the Spotlight icon in the menu bar will pulsate and the Console logs will report “Waiting for index to be ready”. Generally, this phase is so quick that the user is unaware that it occurred.

    Unfortunately, this phase can hang thus preventing Time Machine from completing a backup. During this period, the Spotlight icon will continuously pulsate. Clicking on the Spotlight icon will reveal a progress bar with no estimate of the remaining time or it will indicate many hours of indexing still remains. The Console logs will continually report “Waiting for index to be ready”.

    Ordinarily, Spotlight indexing is a good thing. And at times, if an index has become corrupt or untrustworthy, Spotlight will require a period of time to rebuild the index. If it has only been a couple of hours then let the process continue. However, if it has been many hours, and the Spotlight menu progress bar still does not indicate an estimated time of completion, then things have hung. You will need to force Spotlight to clear its’ indexes and re-catalogue all volumes. [http://support.apple.com/kb/HT2409]

    *Force Spotlight to Rebuild Indexes*
    Go to System Preferences --> Time Machine.
    Using the slider on the left, turn OFF Time Machine backups for now.
    Next, click “Show All” in the toolbar.
    Select the Spotlight Preferences.
    Click the Privacy Tab.
    First, drag your Macs’ internal hard disk from the desktop to the Privacy list.
    Wait 10 seconds, then highlight the Macs’ hard disk in the list and click the tiny “-” button at the bottom to remove it from the list.
    Spotlight will initiate a reindex of the hard disk. If you click on the Spotlight menu icon you may see the message:

    +“Spotlight helps you quickly find things on your computer. Spotlight will be available as soon as the contents of your computer have been indexed.”+

    A progress bar will indicate perhaps 10-20 minutes remaining depending upon how much data there is.
    Once completed, drag your Time Machine backup disk into the Privacy list of the Spotlight Preferences.
    Wait 10 seconds, then highlight the Time Machine backup disk in the list and click the tiny “-” button at the bottom to remove it from the list.
    Spotlight will now initiate a reindex of the hard disk.
    Once completed, if you have any other hard disk attached to your Mac that are also being backed using Time Machine, then force a reindex as well using the procedure outlined above.

    Let us know if this resolves your issue.

    Cheers!
    MacBook Pro, Mac OS X (10.5.4), MacBook, PowerBook G4, Time Capsule, AppleTV, AEBS, 2 iPhones
  • Glenn Carter Level 4 Level 4 (3,360 points)
    Currently Being Moderated
    Oct 29, 2008 1:27 PM (in response to Maxwell’s Demon)
    Max,

    If Console is still reporting "mds: importer errors" over and over again, then I would kill the mds process in Activity Monitor anyways and then attempt another backup.

    Glenn
    MacBook Pro, Mac OS X (10.5.4), MacBook, PowerBook G4, Time Capsule, AppleTV, AEBS, 2 iPhones
  • Glenn Carter Level 4 Level 4 (3,360 points)
    Currently Being Moderated
    Oct 29, 2008 2:03 PM (in response to Maxwell’s Demon)
    Try backing up WITHOUT killing the mdworker processes. Just kill the mds process for now. If another backup fails, then go after mdworker.

    If that fails, a simple reboot of your Mac may be sufficient to get Time Machine backups on track.

    Bear in mind that, since it has been some time since your last backup, Time Machine will likely need to do a "deep traversal" requiring a lengthy "Preparing..." session. Let it proceed uninterrupted.

    Glenn
    MacBook Pro, Mac OS X (10.5.4), MacBook, PowerBook G4, Time Capsule, AppleTV, AEBS, 2 iPhones
  • Glenn Carter Level 4 Level 4 (3,360 points)
    Currently Being Moderated
    Oct 29, 2008 2:44 PM (in response to Maxwell’s Demon)
    Great to hear!

    Actually, if it was mds that was interfering with backups, even if it showed little or no CPU usage, then it was indeed Spotlight as any process starting with md is a component, more or less, of Spotlight.

    Once you have performed a few more backups, I suggest re-indexing your Macs internal hard disk.

    *Force Spotlight to Rebuild Indexes*
    Go to System Preferences --> Time Machine.
    Using the slider on the left, turn OFF Time Machine backups for now.
    Next, click “Show All” in the toolbar.
    Select the Spotlight Preferences.
    Click the Privacy Tab.
    First, drag your Macs’ internal hard disk from the desktop to the Privacy list.
    Wait 10 seconds, then highlight the Macs’ hard disk in the list and click the tiny “-” button at the bottom to remove it from the list.
    Spotlight will initiate a reindex of the hard disk. If you click on the Spotlight menu icon you may see the message:

    +“Spotlight helps you quickly find things on your computer. Spotlight will be available as soon as the contents of your computer have been indexed.”+

    A progress bar will indicate perhaps 10-20 minutes remaining depending upon how much data there is.
    Once completed, drag your Time Machine backup disk into the Privacy list of the Spotlight Preferences.
    Wait 10 seconds, then highlight the Time Machine backup disk in the list and click the tiny “-” button at the bottom to remove it from the list.
    Spotlight will now initiate a reindex of the hard disk.
    Once completed, if you have any other hard disk attached to your Mac that are also being backed using Time Machine, then force a reindex as well using the procedure outlined above.

    Let us know if this resolved your issue.

    Cheers!
    MacBook Pro, Mac OS X (10.5.4), MacBook, PowerBook G4, Time Capsule, AppleTV, AEBS, 2 iPhones
  • Glenn Carter Level 4 Level 4 (3,360 points)
    Currently Being Moderated
    Oct 29, 2008 3:19 PM (in response to Maxwell’s Demon)
    If you are now performing successful backups, then Kappy's right, you should perform an Archive and Install - particularly if you are experiencing such serious OS issues. An Archive and Install is the least invasive of the various re-installs you could perform, so I wouldn't worry.

    Here is my procedure for an Archive and Install as it relates to Time Machine.

    *Archive & Install*
    An Archive and Install is the least invasive of the 3 methods. This approach results in a fresh copy of the Mac OS system software while at the same time preserving all current user accounts on your Mac. Additionally, this method will permit Time Machine to continue backing up to the same set of backups it did prior to the installation.

    Procedure:
    Verify that your Mac has uninterrupted AC power.
    Turn “OFF” Time Machine in the Preferences.
    Insert your original Mac OS 10.5 Leopard DVD and reboot while holding down the “C” key.
    At the “Welcome” screen click “Continue”.
    At “Select a Destination” choose your Macs’ hard disk.
    Click “Options” in the lower left.
    Choose “Archive and Install”.
    Ensure that “Preserve Users and Network Settings” is checked.
    Click “OK”.
    Back at the “Select a Destination” screen click “Continue”.
    At “Install Summary” click “Install”.

    Once the installation is complete, use Software Update to bring your Mac up to date.
    Next, Launch Disk Utility, select your Macs’ internal disk on the left, and click “Repair Disk Permissions”.

    During this initial period, Spotlight is going to re-index your Mac’ hard disk. This can take up to several of hours depending upon the volume of data. Allow it to complete before resuming Time Machine backups. You can monitor its’ progress by clicking on the Spotlight icon in the menu bar.

    During the installation a new folder was created at the root level of your hard disk labeled “Previous Systems”. These are all the system files that were just replaced with fresh copies. If you are comfortable, you can delete this folder right away. Otherwise, wait a week or so incase there is something you wish to retrieve, then delete it.

    Finally, turn Time Machine back “ON” in the Preferences. Time Machine should continue to backup to the same set of backups that it did prior to the Archive & Install. However, due to the extensive changes to the systems’ directories, the first backup will require a lengthy session of “Preparing...” as Time Machine performs a “deep traversal”. Allow this to proceed uninterrupted. Naturally, this first backup will be a significant one, perhaps involving several GB of data, so attempting this wirelessly will require time and patience.

    Cheers!

    Message was edited by: Glenn Carter
    MacBook Pro, Mac OS X (10.5.4), MacBook, PowerBook G4, Time Capsule, AppleTV, AEBS, 2 iPhones
  • Glenn Carter Level 4 Level 4 (3,360 points)
    Currently Being Moderated
    Oct 29, 2008 3:55 PM (in response to Maxwell’s Demon)
    "Yes" to your first statement.

    As for Kappy's recommendations (excellent by the way), use both. We just focus on different aspects of the procedure. A combined approach couldn't hurt.

    Regarding, mdworker, it is simply another component of Spotlight. I wasn't being 'adamant', just conservative. Less is more. I prefer the minimalist response if it works. It's now moot if you are going to do the Archive & Install.

    Glenn
    MacBook Pro, Mac OS X (10.5.4), MacBook, PowerBook G4, Time Capsule, AppleTV, AEBS, 2 iPhones

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.