Mds-crash-state?

i was updating my two ipods and i noticed something in the macintosh hd and it had a white file and it was labeled mds-crash-state. when i clicked it said there was no application to open it. when i tried to delete it, it required a password. what is this file?!?!!?!? it sounds horrible!

This file appears if Spotlight crashes at some point; you don't need to keep it on your hard disk. You were asked for a password when you tried to delete it because the hard disk has a flag set which will cause non-root users to be asked for an administrator password if they try to delete something which they aren't the owner of from the disk's top level.
(10019)

Similar Messages

Spotlight reindex, mds crash

Hello,
I was searching a lot of stuff and I didn't found any resonable solution.
It starts about the last update to 10.9.1. (17.12.).
Main problem is like this: every time I open a lid on my AriMac, spotlight is starting reindexation.
I found some lines in console about mds crash report with information in it:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xffffffffffffff08
below include my system raport, maybe sombody can help a bit, or a lot :-)
Hardware Information:
          MacBook Air (13-inch, Mid 2011)
          MacBook Air - model: MacBookAir4,2
          1 1.7 GHz Intel Core i5 CPU: 2 cores
          4 GB RAM
Video Information:
          Intel HD Graphics 3000 - VRAM: 384 MB
Audio Plug-ins:
          BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
          AirPlay: Version: 1.9 - SDK 10.9
          AppleAVBAudio: Version: 2.0.0 - SDK 10.9
          iSightAudio: Version: 7.7.3 - SDK 10.9
Startup Items:
          PACESupport: Path: /Library/StartupItems/PACESupport
          WkSvMacX: Path: /Library/StartupItems/WkSvMacX
System Software:
          OS X 10.9.1 (13B42) - Uptime: 0 days 5:16:30
Disk Information:
          APPLE SSD SM256C disk0 : (251 GB)
                    EFI (disk0s1) <not mounted>: 209.7 MB
                    MacAir SSD (disk0s2) /: 250.14 GB (11.1 GB free)
                    Recovery HD (disk0s3) <not mounted>: 650 MB
USB Information:
          Apple Internal Memory Card Reader
          Apple Inc. FaceTime Camera (Built-in)
          Apple Inc. Apple Internal Keyboard / Trackpad
          Apple Inc. BRCM20702 Hub
                    Apple Inc. Bluetooth USB Host Controller
FireWire Information:
Thunderbolt Information:
          Apple Inc. thunderbolt_bus
Kernel Extensions:
          at.obdev.nke.LittleSnitch          (4052 - SDK 10.8)
          com.AmbrosiaSW.AudioSupport          (4.1.2 - SDK 10.7)
          com.globaldelight.driver.BoomDevice          (1.1 - SDK 10.5)
          com.protech.NoSleep          (1.3.3 - SDK 10.8)
          com.Ondesoft.driver.OndeAudioRecorderDevice          (1.0.0 - OS X 10.7)
          com.Cycling74.driver.Soundflower          (1.5.1)
          com.paceap.kext.pacesupport.snowleopard          (5.8 - SDK 10.6)
          org.pqrs.driver.KeyRemap4MacBook          (9.2.0)
Problem System Launch Daemons:
          [failed] com.apple.AOSNotificationOSX.plist
          [failed] com.apple.softwareupdated.plist
          [failed] com.apple.wdhelper.plist
Problem System Launch Agents:
Launch Daemons:
          [loaded] at.obdev.littlesnitchd.plist
          [loaded] com.adobe.fpsaud.plist
          [loaded] com.adobe.SwitchBoard.plist
          [loaded] com.ambrosiasw.ambrosiaaudiosupporthelper.daemon.plist
          [not loaded] com.barebones.textwrangler.plist
          [loaded] com.bjango.istatmenusdaemon.plist
          [loaded] com.bombich.ccc.plist
          [loaded] com.bresink.system.securityagent.plist
          [loaded] com.dervishsoftware.MailHubInstallerHelper.plist
          [loaded] com.marketcircle.daylite.accessd.plist
          [loaded] com.marketcircle.daylite.attachmentd.plist
          [loaded] com.marketcircle.daylite.backupd.plist
          [loaded] com.marketcircle.daylite.cardcald.plist
          [loaded] com.marketcircle.daylite.dlbackup.plist
          [loaded] com.marketcircle.daylite.dlconfigd.plist
          [loaded] com.marketcircle.daylite.dlserver.plist
          [loaded] com.marketcircle.daylite.portsd.plist
          [loaded] com.marketcircle.daylite.staged.plist
          [loaded] com.marketcircle.daylite.touchd.plist
          [loaded] com.microsoft.office.licensing.helper.plist
          [loaded] com.oracle.java.Helper-Tool.plist
          [loaded] com.paceap.eden.licensed.plist
          [loaded] org.pqrs.KeyRemap4MacBook.load.plist
          [loaded] PACESupport.plist
          [loaded] PPPMonitord.plist
Launch Agents:
          [loaded] at.obdev.LittleSnitchUIAgent.plist
          [not loaded] com.adobe.AAM.Updater-1.0.plist
          [loaded] com.adobe.CS5ServiceManager.plist
          [loaded] com.bjango.istatmenusagent.plist
          [loaded] com.ecamm.iglasses3agent.plist
          [loaded] com.oracle.java.Java-Updater.plist
          [loaded] com.protech.NoSleep.plist
          [loaded] com.wacom.pentablet.plist
          [loaded] edu.vanderbilt.vuwer.plist
          [loaded] org.pqrs.KeyRemap4MacBook.server.plist
          [loaded] SwapperUFi.plist
User Launch Agents:
          [loaded] com.adobe.ARM.[...].plist
          [loaded] com.dervishsoftware.MailHubUpdater.plist
          [loaded] com.ecamm.printopia.plist
          [loaded] com.google.keystone.agent.plist
          [loaded] com.macpaw.CleanMyMac.helperTool.plist
          [loaded] com.macpaw.CleanMyMac.trashSizeWatcher.plist
          [loaded] com.macpaw.CleanMyMac.volumeWatcher.plist
          [not loaded] com.marketcircle.daylite.dlbackuppersonal.plist
          [loaded] com.marketcircle.daylite.pidclear.plist
          [loaded] com.valvesoftware.steamclean.plist
          [loaded] com.vladalexa.MagicPrefs.plist
          [loaded] net.infinite-labs.SIMBLEnablerForSandboxedApps.plist
          [not loaded] ws.agile.1PasswordAgent.plist
User Login Items:
          iTunesHelper
          CuteClips3
          Calq
          Cinch
          Skype_2
          PopChar
          Typinator
          DragonDrop
          PastebotSync
          Overflow
          Dropbox
          MagicMenu
          Phone Amego
          LazyMouseBG
          Default Folder X Helper
          Bartender
          BambooCore
3rd Party Preference Panes:
          Default Folder X
          Flash Player
          Flip4Mac WMV
          Launchpad-Control
          LazyMouse
          MacFUSE
          MagicPrefs
          NoSleep
          NTFS-3G
          Pastebot Sync
          Perian
          Printopia
          Spelling
          SteerMouse
          SwitchResX
          PenTablet
Internet Plug-ins::
          WacomNetscape: Version: 2.1.0-1 - SDK 10.8
          Default Browser: Version: 537 - SDK 10.9
          Flip4Mac WMV Plugin: Version: 2.4.2.4
          WacomTabletPlugin: Version: WacomTabletPlugin 2.1.0.2
          AdobeAAMDetect: Version: AdobeAAMDetect 1.0.0.0 - SDK 10.6
          FlashPlayer-10.6: Version: 11.9.900.170 - SDK 10.6
          AdobePDFViewerNPAPI: Version: 11.0.0 - SDK 10.6
          Silverlight: Version: 5.1.20913.0 - SDK 10.6
          Flash Player: Version: 11.9.900.170 - SDK 10.6
          QuickTime Plugin: Version: 7.7.3
          iPhotoPhotocast: Version: 7.0 - SDK 10.8
          SharePointBrowserPlugin: Version: 14.3.9 - SDK 10.6
          AdobePDFViewer: Version: 11.0.0 - SDK 10.6
          GarminGpsControl: Version: 4.0.4.0 Release - SDK 10.6
          JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Outdated! Update
User Internet Plug-ins::
          Google Earth Web Plug-in: Version: 7.1
Bad Fonts:
          None
Old applications:
          Corel Painter Lite:          Version: 1.0.910 - SDK 10.5
                    /Applications/Corel Painter Lite.app
          Data Rescue 3:          Version: 3.2.2 - SDK 10.4
                    /Applications/Data Rescue 3.app
          Garmin HomePort:          Version: 2.1.0 - SDK 10.5
                    /Applications/Garmin HomePort.app
          Garmin Lifetime Map Updater:          Version: 2.2 - SDK 10.5
                    /Applications/Garmin Lifetime Map Updater.app
          Garmin MapManager:          Version: 3.0.1 - SDK 10.5
                    /Applications/Garmin MapManager.app
          Garmin POI Loader:          Version: 2.2.2 - SDK 10.5
                    /Applications/Garmin POI Loader.app
          Garmin WebUpdater:          Version: 2.1.3 - SDK 10.4
                    /Applications/Garmin WebUpdater.app
          Labels & Addresses:          Version: 1.6.2 - SDK 10.4
                    /Applications/Labels & Addresses.app
          Leawo Photo Recovery:          Version: 1.2.0 - SDK 10.5
                    /Applications/Leawo Photo Recovery.app
          MailSteward:          Version: 9.0.7 - SDK 10.5
                    /Applications/MailSteward.app
          Maktura:          Version: 1.5.8 - SDK 10.5
                    /Applications/Maktura.app
          Microsoft Alerts Daemon:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Microsoft Alerts Daemon.app
          Microsoft Chart Converter:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Microsoft Chart Converter.app
          Microsoft Clip Gallery:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Microsoft Clip Gallery.app
          Microsoft Database Daemon:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Microsoft Database Daemon.app
          Microsoft Database Utility:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Microsoft Database Utility.app
          Microsoft Document Connection:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Microsoft Document Connection.app
          Microsoft Excel:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Microsoft Excel.app
          Microsoft Graph:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Microsoft Graph.app
          Microsoft Language Register:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Additional Tools/Microsoft Language Register/Microsoft Language Register.app
          Microsoft Office Reminders:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Microsoft Office Reminders.app
          Microsoft PowerPoint:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Microsoft PowerPoint.app
          Microsoft Upload Center:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Microsoft Upload Center.app
          Microsoft Word:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Microsoft Word.app
          Movie Collector:          Version: 8.1.3 - SDK 10.5
                    /Applications/Movie Collector.app
          Open XML for Excel:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Open XML for Excel.app
          Paint it!:          Version: 1.0.0.132 - SDK 10.5
                    /Applications/Paint it!.app
          Solver:          Version: 1.0 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/Add-Ins/Solver.app
          Spin Doctor:          Version: 1.0 - SDK 10.5
                    /Applications/Toast 11 Titanium/Spin Doctor.app
          SyncServicesAgent:          Version: 14.3.9 - SDK 10.5
                    /Applications/Microsoft Office 2011/Office/SyncServicesAgent.app
          Video Rotate:          Version: 1.0.2 - SDK 10.0
                    /Applications/Video Rotate.app
Time Machine:
          Skip System Files: NO
          Mobile backups: ON
          Auto backup: YES
          Volumes being backed up:
                    MacAir SSD: Disk size: 232.96 GB Disk used: 222.62 GB
          Destinations:
                    Air'owy czaso-cofacz [Local] (Last used)
                    Total size: 297.77 GB
                    Total number of backups: 28
                    Oldest backup: 2013-10-21 10:55:03 +0000
                    Last backup: 2013-12-20 14:39:20 +0000
                    Size of backup disk: Too small
                              Backup size 297.77 GB < (Disk used 222.62 GB X 3)
          Time Machine details may not be accurate.
          All volumes being backed up may not be listed.
Top Processes by CPU:
              20%          Console
              18%          WindowServer
              13%          Safari
              10%          com.apple.MailServiceAgent
               9%          MagicPrefs
Top Processes by Memory:
          129 MB          Mail
          50 MB          com.apple.internetaccounts
          45 MB          WindowServer
          41 MB          Finder
          39 MB          com.apple.MailServiceAgent
Virtual Memory Statistics:
          76 MB          Free RAM
          672 MB          Active RAM
          602 MB          Inactive RAM
          1.43 GB          Wired RAM
          18.30 GB          Page-ins
          756 MB          Page-outs
regards
Lukasz S

Kappy wrote:
mds is the metadata server that is used primarily by Spotlight. That file probably appeared because mds crashed. It's possible the file should have been invisible but lost its invisible status, but of this I'm not sure. If you look in the console log for the date and time when that file was created you may find a log entry. If not in the console log perhaps in one of the other logs such as the crash reporter logs.
Kappy,
I searched for mds-crash-state in the console, system, and other logs, and could find no reference to it at all. However, searching for just mds yielded the following on July 10, 2008, in the crashreporter.log:
Thu Jul 10 08:04:30 2008 crashdump[3522]: crashdump started
Thu Jul 10 08:04:33 2008 crashdump[3522]: Started writing crash report to: /Library/Logs/CrashReporter/mds.crash.log
Thu Jul 10 08:04:36 2008 crashdump[3522]: Finished writing crash report to: /Library/Logs/CrashReporter/mds.crash.log
The file called mds-crash-state in my Macintosh HD folder has a creation date of July 10, 2008, 8:04 AM in Get-Info, so the above is almost certainly connected to that event. But there is no indication that it exited abnormally, as far as I can see. There are no more entries on the 10th at all, and no more references in any of the logs to mds, so this appears to be a one-time event? The file I have detected is a "state" file, not a log file, and it is stored in a different location.
As always, thanks for your help.
Drake

Spotlight - MDS - Crashing over and over

A few days ago I did a Spotlight search and it froze. Since then my Mac has been Windows unstable. Mail crashes some times, Excel others times, Console, Activity Monitor, Safari, WebKit, iPhoto - all crash now. MDS is running almost constantly and crashes over and over - never finishes. In fact in Console I currently have 27 mds crash logs, 14 in the last hour. The computer is becoming unusable. Oh, no APE etc...
Steps I have taken:
Repair Permissions, verify disk, repair disk, CCCed to a new disk, REinstalled 10.5.4 combo, rerepaired disk, etc. And before I did all the mutil /E type "stuff".
Net net; mds is running and crashing over and over. This seems to be causing other apps to crash as well. Other oddity - most of the time when an application crashes, it does not quit/shutdown - it just is hung in the Not Responding state. Multiple ReportCrash processes will run but never complete and cannot be quit or forced quit - including sudo kill -9. Then the Not Responding application cannot be killed off either and the system will not shutdown - requires hard stop on power.
If this were a DELL I would understand. But this is a Quad Core G5 Mac running 10.5.4 and 4.5 gigs of Apple RAM.
Note - just while writing this, I have 5 more mds crash logs - of of which refer to a KERNPROTECTIONFAILURE and EXCBADACCESS.
Ideas?

Hi Ashler, I think baltwo is right, and you need to reinstall the OS (Archive & Install) because your Spotlight system is "hosed". If you read about the A&I first and perhaps print or write the steps out (very simple, really), I think you will be pleasantly surprised by how easy Apple has made the process. It's nothing as bad as doing a Windows re-install.
But first, we should try to think of the reason for the problem. Have you been running anything that tries to duplicate or otherwise modify the behaviour of Spotlight? In my experience, I have found that everything from Google Desktop to Microsoft Office 2008 have caused Spotlight/indexing/MDS problems on Macs recently. A Spotlight plugin (like any of the .mdimporter plugins from Office, for example) could cause problems; or perhaps Google Desktop's efforts to duplicate Spotlight's services. Or perhaps any other bit of software.
In any case, BEFORE you do the Archive & Install, be sure to go through your main root Library and also your user home Library, and look for items that might be running and causing problems. Also, use Activity Monitor to show all processes and see if there's an app running at startup or login. Then disable the things that might be the cause. Somehow, try to make sure that whatever has got jammed in your system is not going to get transferred by the Archive & Install and end up doing the same thing again when you are done. Try removing the Privacy Spotlight settings and then running from a fresh newly created user account to see if the problem lies with the System as a whole, or just within your own user home folder.
Let us know how you do. Good luck anyway - your Archive & Install will fix you right up.

Help needed - constant MDS crashing

My Imac G5 has a continuing crash with the "mds" revealing in the Console Crash Reporting that a report is being written every 30 seconds or so. Its making my machine work harder as you can hear the fans speeding up then slowing down and then up & down again.
I'll try and attach a log for the more knowledgeable than me to view and hopefully some answers
and how to rectify.
This first came to my attention when trying to use Time Machine which kept failing and still wont
complete backups.
Alan
Process: mds [4707]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
Identifier: mds
Version: ??? (???)
Code Type: PPC (Native)
Parent Process: launchd [1]
Date/Time: 2008-02-09 09:37:20.277 +1030
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x00000000f0410000
Crashed Thread: 9
Thread 0:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0000cfa0 0x1000 + 49056
5 mds 0x00005580 0x1000 + 17792
Thread 1:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 2:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 3:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 4:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 5:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 6:
0 libSystem.B.dylib 0x959bb3e8 _semwaitsignal + 8
1 libSystem.B.dylib 0x959f7fa0 pthread_condwait + 1580
2 mds 0x000095bc 0x1000 + 34236
3 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 7:
0 libSystem.B.dylib 0x959c1ea0 read$UNIX2003 + 12
1 mds 0x000091b4 0x1000 + 33204
Thread 8:
0 libSystem.B.dylib 0x959f6438 kevent + 12
Thread 9 Crashed:
0 com.apple.Metadata 0x94cfc8fc copyArray + 152
1 com.apple.Metadata 0x94ceba88 copyObject + 1064
2 com.apple.Metadata 0x94cec6b4 copyDictionary + 184
3 com.apple.Metadata 0x94cebb00 copyObject + 1184
4 com.apple.Metadata 0x94ceb5fc MDPlistBytesCopyPlistAtIndexWithCallbacks + 272
5 mds 0x0004ecb4 0x1000 + 318644
6 mds 0x000526bc 0x1000 + 333500
7 com.apple.Metadata 0x94d24580 machmsgdispatch + 372
8 mds 0x00047e74 0x1000 + 290420
9 com.apple.CoreFoundation 0x9067b808 __CFMachPortPerform + 180
10 com.apple.CoreFoundation 0x9069d908 CFRunLoopRunSpecific + 2504
11 mds 0x00059ab8 0x1000 + 363192
12 mds 0x0005987c 0x1000 + 362620
13 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
14 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 10:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 11:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 12:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 13:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.spotlight.index 0x00207f0c _handleExceptions + 208
3 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 14:
0 libSystem.B.dylib 0x959b4a58 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x959f7e9c pthread_condwait + 1320
2 com.apple.spotlight.index 0x00178334 sischeduler_run_waitingtimeout + 188
3 com.apple.spotlight.index 0x0016529c runLoop + 72
4 com.apple.spotlight.index 0x001653b0 setattr_runLoop + 72
5 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 15:
0 libSystem.B.dylib 0x959b49d8 machmsgtrap + 8
1 libSystem.B.dylib 0x959bb8fc mach_msg + 56
2 com.apple.CoreFoundation 0x9069d664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x95d51d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x959f6bf8 pthreadstart + 316
Thread 9 crashed with PPC Thread State 32:
srr0: 0x94cfc8fc srr1: 0x0000d030 dar: 0xf0410000 dsisr: 0x42000000
r0: 0x94cfc8fc r1: 0xf03ce830 r2: 0xa0aef858 r3: 0x0a753de0
r4: 0x09f014e8 r5: 0x00000010 r6: 0x74696e67 r7: 0x00000000
r8: 0x696e6773 r9: 0x00000000 r10: 0x00000000 r11: 0x28048218
r12: 0x0a753df9 r13: 0xa0a0b674 r14: 0x00000000 r15: 0xf048faf8
r16: 0xf048f910 r17: 0x00000028 r18: 0xf048fab0 r19: 0x94d35f28
r20: 0xa0a0c874 r21: 0xf048f6d0 r22: 0xf048f9d8 r23: 0xf03ce870
r24: 0x0035d020 r25: 0x94d35f28 r26: 0x00000000 r27: 0x000303a2
r28: 0x000105e5 r29: 0xf0410004 r30: 0xf048f6d0 r31: 0x94cfc874
cr: 0x24048212 xer: 0x20000000 lr: 0x94cfc8fc ctr: 0x959b5420
vrsave: 0x80000000
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
0x1d47000 - 0x1d48ffc liblangid.dylib ??? (???) <5f078ac1f623f5ce432ea53fc29338c0> /usr/lib/liblangid.dylib
0x1f9f000 - 0x1fa3ff7 libgermantok.dylib ??? (???) <4d20f26bdd859d4ee54109a0d4cd699c> /usr/lib/libgermantok.dylib
0x3ead000 - 0x3fd2ffb libmecab.1.0.0.dylib ??? (???) <cd875e74974e4ec3a0b13eeeb236fa53> /usr/lib/libmecab.1.0.0.dylib
0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
0x90545000 - 0x90613ff7 com.apple.CoreServices.OSServices 210.2 (210.2) <bad4943629f870d305f2bc7c6dfffe2d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x90634000 - 0x90759ff3 com.apple.CoreFoundation 6.5 (476) <9073c2bfdf6842562c8b7f0308109c02> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x90b51000 - 0x90b6cff3 com.apple.DirectoryService.Framework 3.5 (3.5) <3246a5d1c6a3d678798a90e8c5cd3677> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x90b71000 - 0x90b76ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x9139d000 - 0x9169dff3 com.apple.CoreServices.CarbonCore 783 (783) <fd2acaf23e95472f78b8a077fa039986> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x91853000 - 0x91a34ffb com.apple.security 5.0.1 (32736) <15632bf9bbdb223194b3d79a2e48e02d> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x91a35000 - 0x91a43fff libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
0x91b69000 - 0x91bfbfff com.apple.framework.IOKit 1.5.1 (???) <591b8b0cc4261db98a6e72e38eef5f9a> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x91d76000 - 0x91dfbfff libsqlite3.0.dylib ??? (???) <7b379cb4220346e99c32c427d4539496> /usr/lib/libsqlite3.0.dylib
0x91dfc000 - 0x91e23fff libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
0x9297f000 - 0x9298affb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x92a84000 - 0x92afeffd com.apple.CFNetwork 220 (221) <00b882d3d3325526b78ded74880759fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x93f0f000 - 0x93f3aff7 libauto.dylib ??? (???) <c1f2bd227817ad7c7bf29ec74729ac7c> /usr/lib/libauto.dylib
0x940ac000 - 0x9418ffeb libobjc.A.dylib ??? (???) <4a90e315bd1718c3f5ae09ee6c23e36c> /usr/lib/libobjc.A.dylib
0x94190000 - 0x941c5fff com.apple.AE 402 (402) <a4b92c8ac89cc774b85fb44c48b9d882> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x94246000 - 0x942c1fff com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x943f1000 - 0x944dafff libxml2.2.dylib ??? (???) <6f383df1e1e775be0158ba947784ae13> /usr/lib/libxml2.2.dylib
0x949f8000 - 0x94a07fff com.apple.DSObjCWrappers.Framework 1.2 (1.2) <2411674c821a8907449ac741ce6a40c3> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x94cea000 - 0x94d35ffb com.apple.Metadata 10.5.0 (398) <b6bb1fd5a7a9135f546b2d8cbd65eafc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x94fcd000 - 0x950c3ffc libiconv.2.dylib ??? (???) <05ae1fcc97404173b2f9caef8f8be797> /usr/lib/libiconv.2.dylib
0x950c4000 - 0x9520cff3 libicucore.A.dylib ??? (???) <250daed2fb2e6bf114480e2e4da0728b> /usr/lib/libicucore.A.dylib
0x95210000 - 0x95210ffa com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x957ce000 - 0x957e6ffb com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x9582e000 - 0x95866fff com.apple.SystemConfiguration 1.9.0 (1.9.0) <d925dde7699e6231c88a41b0254a7591> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x959b3000 - 0x95b4cfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
0x95bad000 - 0x95bb5fff libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
0x95d48000 - 0x95f8cffb com.apple.Foundation 6.5.1 (677.1) <4152239382fb0f48abbcbf35bd04afa6> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x963ca000 - 0x963d3fff com.apple.DiskArbitration 2.2 (2.2) <9c8f8ade43fa25b32109ef9dcc0cb5d5> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x96754000 - 0x967eaff7 com.apple.LaunchServices 286 (286) <a3a0b2af862e9a8945072f8cb523678f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x96874000 - 0x968dbffb libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
0xfffec000 - 0xfffeffff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

Barry,
Thanks for your reply.
As it stands at the moment I have removed the "mds" file to the trash and every thing has now calmed down - no more crashes - and what's more I can now back-up using Time Machine something I was unable to do before.
This "mds" file is Unix Executable, so do you know what it does and if its removed will there be any
problems.
Perhaps some else might know this answer
Alan

Cisco m9100 MDS cpu state discrepencies

Hi.
I have weird issues with my m9100 MDS's cpu. After CISCOWorks complains that thoses equipement were peaking at 100% every minutes or so, I went on the equipements and try'd a few "show system ressources". Here is the result (remark the cpu states in bold);
FC-BLAMTL04-1# show system resources
Load average:   1 minute: 0.02   5 minutes: 0.14   15 minutes: 0.16
Processes   :   182 total, 1 running
CPU states :   25.0% user,   75.0% kernel,   0.0% idle
Memory usage:    516136K total,    450816K used,     65320K free
                   6340K buffers, 247552K cache
FC-BLAMTL04-1# show system resources
Load average:   1 minute: 0.02   5 minutes: 0.13   15 minutes: 0.16
Processes   :   182 total, 1 running
CPU states :   50.0% user,   50.0% kernel,   0.0% idle
Memory usage:    516136K total,    450816K used,     65320K free
                   6340K buffers, 247552K cache
FC-BLAMTL04-1# show system resources
Load average:   1 minute: 0.02   5 minutes: 0.13   15 minutes: 0.16
Processes   :   182 total, 1 running
CPU states :   340282346638528859811704183484516925440.0% user,   340282346638528859811704183484516925440.0% kernel,   340282346638528859811704183484516925440.0% idle
Memory usage:    516136K total,    450624K used,     65512K free
                   6340K buffers, 247552K cache
FC-BLAMTL04-1# show system resources
Load average:   1 minute: 0.02   5 minutes: 0.13   15 minutes: 0.16
Processes   :   182 total, 1 running
CPU states :   340282346638528859811704183484516925440.0% user,   340282346638528859811704183484516925440.0% kernel,   340282346638528859811704183484516925440.0% idle
Memory usage:    516136K total,    450624K used,     65512K free
                   6340K buffers, 247552K cache
FC-BLAMTL04-1# show system resources
Load average:   1 minute: 0.01   5 minutes: 0.12   15 minutes: 0.16
Processes   :   182 total, 1 running
CPU states :   33.3% user,   66.7% kernel,   0.0% idle
Memory usage:    516136K total,    450816K used,     65320K free
                   6340K buffers, 247552K cache
It appear, sometime, for an unknown reason, CPU peaks to a weird % number (I thought a % couldn't get higher than 100).
Also, trying a "show process" (to get the running processes) command dosen't work. I am only able to "show processes"
Did someone experience same kind of discrepencies? I am running m9100-s2ek9-mz.4.1.1b.bin image.
Thank you.

Seen a lot of incorrect CPU utilization values due to bug CSCte81951. Note the new spelling of the command to see the cpu history etc.
From bug info:
"show system resources" shows high cpu usage even when there is not much activity on the switch.
In the specific case reported the cpu util (user+kernel) was always 100%.
No workarounds. Use "show processes cpu history" or "show processes cpu" for
cpu util. Fixed in 4.2(4) and 5.0(1a).

Imovie crashes - States that its "Building a Project"?

I recently had problems with imovie crashing stating that it had "encountered a problem and quit unexpectedly". So after doing some research I deleted the Imovie plist files off of my library. It seemed to work for awhile, but now when I try to use imovie - a caption comes up stating that its "Building a project" and imovie freezes up. I'm not evening starting a new project so IDK why it would state that I am.
Any help would be greatly appreciated.

With 4 +1 other members who recognise this issue, some sort of reply would be interesting.
My new 2012 27' fusion, 24G ram, 680MX is having big problems with iMovie. Switching between Projects takes minutes, which totally interupts the process of filing clips. Deleting clips from event browser is slower than comfortable.

Spotlight (mds) crashes after running TimeMachine

Hi!
As other posted in this forum I faced several freeze ups after running TimeMachine. I had a closer look into the console logs and found the process "mds" (meta data search aka Spotlight) crashes after every backup performed by TimeMachine:
===== cut =====
Process: mds [22]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
Identifier: mds
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1]
Date/Time: 2007-11-19 19:48:46.771 +0100
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x000000000000047c
Crashed Thread: 5
===== cut =====
It's always thread no. 5. My next try will be to disable Spotlight, but has anybody the same problem?
Mattes

I googled some posts in the net, e. g. <http://automators.net/news/macosxhints-com/10-5-disable-spotlight-completely/> about disabling Spotlight, but tried a less intrusive way: First by dragging the backup volume in the Privacy tab (Spotlight system preferences), but the mounted network share wasn't selectable. So my second try was running "sudo mdutil -i off <volume>".
Sorry guys, I should have mentioned that my TimeMachine backup is located on an AEBS-attached USB drive (TM's unsupported network device) and Spotlight seems to have problems with this volume (not the mounted sparse image) ...
Mattes
Message was edited by: Matthias Arndt

Dreamweaver CS5 25% CPU, crash state, CSS Styles window stops updating

Hi, has anyone else found their app in the state where it starts using 25% CPU continually, with the exe not closing after the app window closes? When this happens, right before, I'll notice that when I select an element in the design or code windows, or the breadcrumbs style selector at the bottom of these two windows, the CSS Styles window will not update to show the current selection's properties.
For me, I've encountered this after being in Inspect mode, and then some how maybe I alt-tab or click in another window without having first selected an item with the Inspector. At least, I think this is when it happens. I'll be in th emiddle of something in DW like modifying a CSS property, then realize I need to go look in Illustrator or something to see how big an image was, then come back and stuff stops working properly. But not always! Seems to happen to me with my style of working about once per hour, really annoying. Can't wait for CS6!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

darn, I put this in the wrong forum. Is it possible to move it?

Lightroom 1.1 crash/making timely backups?

Today I was minding my own business working in my newly upgraded version of LR 1.1 when suddenly with no warning my computer crashed. No indication that anything was wrong, just suddenly a blink and a black screen. I was running no other apps at the time, and no other device that was attached either to the same surge protector or the same outlet was affected, all of which makes me suspect that LR was somehow the source of the crash. This is especially so because I did some routine computer maintenance as recently as the day before yesterday (repaired permissions and ran disk warrior to rebuild the drive). The only thing that's been doing strange things is LR (as some of you know from recent postings on various forums...).
Some background: I am running a dual 2 GHz G5 PowerPC with 3.5 GB of RAM, on system OS10.4.10. I was working in a LR folder with about 6000+ images in it at the time of the crash.
After the crash I went to restart my computer and also LR, and LR gave me a dialog box that said my catalog was corrupted and couldn't be used. I filed a bug report with Adobe and got a helpful note from a Lightroom QE fellow (not sure what QE stands for) with whom I'm corresponding. I'm hoping they can help me repair the catalog, but no word on that yet. The same dialog box said that if I'd made a recent backup I could move it into the LR folder. The last time I closed LR (and hence made an automatic backup) was very late last night. This means that if I go forward and use the backup, all my work today (about 6 hours worth of work) will be lost. For the time being I have moved the backup into place, but am waiting to hear about the repair before I keep going with working on any new material. And of course, I am on a deadline for the project that is effected by all this (aarrrrgggh).
I was wondering if anyone out there has experienced this kind of thing and what you did at this point? Also, how does one go about periodically backing up LR without shutting the program down altogether (a rather disruptive and inconvenient option)? I feel like I should be backing up at least every half hour (I don't want to risk losing more work that that), and didn't realize my work would not be backed up automatically in a situation like this.
I recently undertook a major software and workflow upgrade, and almost didn't go the LR route because I was afraid that LR at version 1.0 was not that stable, nor did it have the DAM features fully developed (the other option would have been ImageIngester Pro/Bridge/iView a la Peter Krogh's system). I decided to go with LR anyway because I felt the DAM issues would be addressed soon, and since I don't have a real DAM system up and running yet anyway, it wouldn't hurt me to wait to start on that. I also chose LR because I am concerned about the future of iView in the hands of the new Microsoft owners. To get LR up and running I bought the D-65 LR workflow download and also used the Chris Orwig tutorials on Lynda.com.
Now I'm beginning to regret my choice because of the stability issues, and it sucks that I might end up losing most of a day's work when I'm on a deadline because LR might have pushed my computer hard enough to elicit a latent hardware failure (this was the suggestion of the Lightroom QE, which seems like a real possibility).
Any feedback, comments or insights on this would be most welcome. This has been a most frustrating week with regards to technology. All I want to do is sit down and do my work, but I seem to be running into glitch after glitch.
Best,
Paula Lerner
Afghanistan Radio Interview:
http://tinyurl.com/35uf5g
http://www.lernerphoto.com
Paula Lerner Photography * Boston * 617-489-6747
[email protected]

Jeff and others:
Many thanks for the feedback, its much appreciated.
Jeff, I understand why you and others say LR didn't cause the crash. It was Dan Tull (who has been very helpful) who suggested that LR might have been pushing my computer hard enough to cause a latent hardware failure, which does make sense to me.
To answer a few questions: The machine is a little over three years old. I have everything backed up on external drives (including LR itself -- I took the D-65 suggestion to get a dedicated drive and backup for LR). It has been hot in Boston of late and my computer has been doing funny things all week, but mostly related to LR (see other posts I've made on this forum, PhotoDigital and APAdigital if you're interested). One odd thing: I have LR sitting in a drive labeled Lightroom_Library, which houses the Backups folder, the Previews.lrdata file, and the lrcat file. I only got LR up and running last week, so I've been relying on the Backups folder to backup for the time being. I have been meaning to do some kind of drop and drag onto the secondary hard drive (Lightroom Library_BK) to do a backup of everything, but haven't done it yet because I wasn't sure how to do it correctly (needed to do more research, haven't gotten that far yet -- thought I might need to set paths properly...?). There wasn't anything on my secondary drive except some test lrdb files and lrcat files (I think). Now the only thing on the secondary drive is a text doc called mds-crash-state with the time of the crash shown as its date modified. At some point I designated that drive as some kind of backup for LR (again, hadn't sorted out the details yet). What's up with this doc on that drive? It must have been created at the time of the crash (hence my suspicions about LR).
Last night I noticed the computer fan was making loud noises (like it was a plane engine about to take off) so I shut it down to let it cool off (its been hot in Boston). Today one of my 8 external drives where I house my digital files would not mount, but I had some other problems with it earlier this week (I reformatted it and recopied the data it normally holds onto it). Jeff, is this what you mean about symptoms that my drive could be going?
Thanks again,
Paula Lerner
http://www.lernerphoto.com
[email protected]

Spotlight problem after Tiger to Leopard Upgrade

Since I upgraded my Macbook Pro 15" from Tiger to Leopard, Spotlight never worked. Initially I didn't mind too much but now I want to get it work.
I tried all suggestions I found in this forum (see list below) to no avail.
It seems Mac OS cannot index the system disk.
Any Terminal command like mdutil or mdimport have no effect and return no info. As a check, I ran the same utilities on my iMac (same Leopard version, but native) and they do in fact work as expected, as well as Spotlight. Another example: mdfind works on my iMac but return nothing on my MBP.
If I try the regular way, when I write my search string in the Spotlight window I just get nothing on my MBP.
I tried the OnyX features for Spotlight:
- Maintenance/Rebuild/Spotlight Index seems to do something, but in fact it does nothing useful
- Parameters/Spotlight/Options: Enable Indexing the Startup-Disk makes an attempt to enable it and switches immediately back to disabled. No way to keep the option checked. Also removed the Font cache from OnyX as suggested in some post - null.
Some attempts I made:
- used Disk Utility to check the disk (no repair needed)
- used Disk Utility to repair permissions: there are many that are always repaired... this makes me feel the problem might in fact be in the permission area. But after many repair the result is always null.
- added the start-up disk to the Privacy area in Spotlight Prefs, and later on removed - null
- trashed com.apple.spotlight.plist pref user prefs - a new one was created but no effect
- removed /.Spotlight-V100 from terminal - a new one was created but no effect
- used mdutil -E and -i on and off - I always get the message "/: Indexing and searching disabled"
- mdimport -L or -A or -X return nothing (on my iMac they return the list of plugins, schema etc.)
- rebooted many times also in safe mode - null
- the problem exists also for the other user on the same MBP
- tried OnyX as described above.
No effect!!
Now my question is: what can I try next ?
I'm sure there is some parameter somewhere (some .plist ?) that can re-enable Spotlight. But which one and where ?
Thanks in advance
Piero

Take a look at Spotless
http://www.fixamac.net/software/spot2/index.php
It deals mainly with Spotlight indexes, but it also contains some diagnostics - its description includes the following:
Spotless will automatically find and delete the "mds-crash-state" file from selected volumes. The file may be created if the Metadata Server crashed or was unexpectedly closed during the indexing process. The presence of this file can prevent Spotlight from indexing the volume in the future.
Spotless allows you to see exact size of the index directory on each volume.
Spotless also includes an on/off switch for Spotlight.
------------------

"invalid volume directory count" troubleshooting help sought

Yep, I'm still on 10.5.8. I am about to go to Snow Leopard (since I know my machine can handle that) and was sorting thru files before the upgrade. I came across mds-crash-state file that prompted me to 'verify disk' (in DU) and then got the "invalid volume directory count" error message.
I think I realize that a repair disk from the install disk is perhaps a best option, but am wondering if I can do this, or even fix original issue, from the install disk on upgrade?
I do already have full backup and secondary backup of all files on this disk (main HD).
I feel another option to fix things, that seems like good time to consider this, is to move all my data on my main HD to new internal drive when I do the upgrade to 10.6.x.
Anyway, besides looking for input on my current options (a - fix this upon upgrade and/or b) move to new main HD during upgrade), I'm wondering if I need to consider doing the 'respair disk' option immediately. I'm no more than a week from upgrading, and other than slow acting computer at times, I haven't experienced any worrisome issues with this computer in recent days.

Do not attempt to "Upgrade in Place" without repairing the Hard Drive. The new install brings in over 250,000 new files. That will NOT make things better.
To ( Repair Disk) from the Installer/Utilities DVD:
Boot from the Installer/Utilities DVD, but do not Install. Answer only the "what language" question, if presented, and wait a quarter minute for the MenuBar to be drawn. Choose Disk Utility from the Utilities menu or the Installer Menu.
At this point, your are using the DVD as your System, so the internal Hard drive is fully available for a deep repair.

Random file on hard drive, please help me find out what it is

Hi all,
I have had this file sitting on my hard drive, when you click and open from hard drive icon there is a file sitting there called mds-crash-state. If i try to delete it it says enter my user password, so ididnt thinking it could be important. Anyone able to shed some light on this and if i can actually delete it without killing my machine?

Go and trash it. The 'mds-crash-state' file may be created if the Metadata Server crashed or was unexpectedly closed during the indexing process. The presence of this file can prevent Spotlight from indexing the volume in the future.
-Bmer
Mac Owners Support Group
Join Us @ MacOSG.com
ITMS: MacOSG Podcast
 An Apple User Group 

Repair disk i done today changed stuff?

hey guys well i had alot of kernel panics on my mac and well i got the idea to go and do a repair disk via boot mode so i did it today morning and it found a serious problem and it fixed it succefully, i havent seen any kernel panic screen so far but iv spoted 2 changes. 1. i see an unknown file in my Harddrive root and its called "mds-crash-state" and second thing is, all the dashboard widgets i had installed have been removed so right now i have the 4 default widgests that come with tiger(calendar, calculator etc..) so i would like to know what to do with that file created in my harddrive root called "mds-crash-state" and i also have another folder there named "DamagedFiles" in the harddrive root that obviously i didnt create, it has 2 tmp files and is around few KBs. one tmp file's name is "000cc938 Temp File" and the other "000cc939 Temp File 1"
so help me out on this one thx alot indeed

Don't know, never had a file suddenly, unexpectedly show up at that location, unless I arranged for it to be there. And you had at least two suddenly appear there? In OS X, if a file that's deletable appears, it appears already in my trash. As a matter of fact, there was a "Recovered" file in my trash this a.m., but I just emptied the trash as I usually do when it appears, as that file can be deleted. If it's not in the trash, the applications folder, the documents folder, or on the desktop, then I'm not sure where it came from. If it can't be opened, does File -> Get Info provide any info about it? It sounds like something you don't need, but I just never had anything show up at that location before. Sorry I can't be any more help with it.
edit-
geez, you guys are quick, three posts while I was composing!
Message was edited by: myhighway

Spotlight died on me

I like the new Spotlight, I even threw out Quicksilver. The trouble is that Spotlight has just died on me. The icon is still there but it does nothing. Does anybody know how to restart it without restarting the whole OS?

hi Ziv,
thanks for the suggestion, but as I mentioned above, this doesn't work. Also simply stopping and restarting Spotlight via Terminal commands returned the result "indexing failed".
So for myself (and defacto everyone else in this thread with the "sleeping spotlight" issue), I decided to go hunt Google and see what I could find. So...
I was able to solve the problem with the following steps (this worked for me - no guarantee it will work for you... see my disclaimer at the end of all this):
1) Take hard drive OUT of Privacy panel (if you've put it in there)
2) open terminal and turn off spotlight indexing for boot volume with the command
sudo mdutil -i off /
3) Then I tried deleting the .Spotlight-v100 file in terminal using the sudo rm commands and despite getting a "confirmation" (terminal isn't very "confirmation friendly") the file wasn't deleted. So - i used terminal to turn ON showing ALL files in the Finder to see if it was really deleted or not.
defaults write com.apple.Finder AppleShowAllFiles YES
Then I restarted the Finder (by holding down the Option key and click-holding the Finder's icon in the dock and selecting "Restart" from the contextual menu. Finder disappears, reloads and your desktop is back.)
4) I opened my hard drive icon and there was the .Spotlight-V100 file and a few others that I deleted from the root level of my drive:
.Spotlight-V100
mds-crash-state (note - this file may mean you have corrupt files - run a viable drive repair utility on your disk soon if you see this file)
and a file named something like "never_index" (I can't recall the exact name, but it's a file added when you add your drive to the Privacy tab on Spotlight preference panel and is in the same directory as the .Spotlight-V100 file, which should be the root of your hard drive.. it's pretty obvious when/if you see it -- for some reason, this never deleted and was preventing spotlight from indexing my drive..)
BE CAREFUL WHAT YOU DELETE BEYOND THIS - Whimsically throwing files into your trash to watch them disappear can result in lobotomizing your Mac.
5) I then turned back off the Show All Items option for Finder so I didn't have to look at all those extra ugly files I'm not supposed to be looking at under normal circumstances, thereby minimizing the chance that I might lobotomize my PowerBook:
defaults write com.apple.Finder AppleShowAllFiles NO
6) Another finder restart
7) Turned back on spotlight indexing in Terminal:
sudo mdutil -i on /
and presto, Spotlight instantly started reindexing my drive and has worked for the past 6 days since I did this.
** Please note - This worked for me and I did this on my own mac for my own benefit and was willing to risk having to (at worse) reformat my drive if I really screwed something up because all of my data is BACKED UP - I'm not an expert but I did my research first with a handy online tool called "Google" -- if you're not familiar with Terminal and screw something up, it's your own fault for playing around before knowing what you're doing. I don't guarantee it will work for you ** =)

Strange File at "/" root level

What is "mds-crash-state?"
It's a file located at my root level next to:
/Applications
mds-crash-state
/Library
/System
/Users

Looks like it is a result of the Spotlight indexing crash. Safe to delete.

Mds-crash-state?

Similar Messages

Maybe you are looking for