For whatever reason "mds" is taking up 30-75% of my CPU and causing my HDD to work overtime. Know it has something to do with spotlight, but how to I stop it? Tried resetting PRAM about an hour ago and it stopped; but for whatever reason it has decided to come back in the last few mins.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
"mds" going crazy
- Thread starter DesmoPilot
- Start date
- Sort by reaction score
Is Spotlight showing a time to completion estimate? Did you add any new hard drives or make any recent OS X updates?
Same HD I've had in this thing since I've basically got it, only recent OS X update was was to 10.6.4. Just a few mins ago I was watching a movie when the system beachballed, could expose but not do anything else like force quit. Forced shutdown and restarted, verified the HDD and it said it needed repairs; so I repaired it off of the OS X DVD and it said it was successful. In the process of backing up everything right now; hopefully my HDD isn't dying and it's just a hiccup from 10.6.4. Maybe the fact that this install is a clone from a different HDD may of caused the problem?
Drag the HD to the privacy panel.
Check your fonts again using FontBook.app, make sure there are no errors -- these used to trip up mds.
But it can also be hanging on a new pdf with included font you downloaded.
---
If you want to check out the drive download SMART Utility.app, this will allow you to check the drive
You can look at the Power On Hours, Bad Sectors, current # of errors, etc. If the errors are low you should be OK, if there are a lot of bad sectors ... finish the backup.
Check your fonts again using FontBook.app, make sure there are no errors -- these used to trip up mds.
But it can also be hanging on a new pdf with included font you downloaded.
---
If you want to check out the drive download SMART Utility.app, this will allow you to check the drive
You can look at the Power On Hours, Bad Sectors, current # of errors, etc. If the errors are low you should be OK, if there are a lot of bad sectors ... finish the backup.
My drive ended up with 16,000 hours 100's of bad sectors and 6000 errors and couldn't run any test without ending with an error.
Got a new one.
My drive ended up with 16,000 hours 100's of bad sectors and 6000 errors and couldn't run any test without ending with an error.
Got a new one.
Dang. There any reason to run the long test? Or is the short one sufficient.
If you have no errors (it is a lifetime number) and no bad sectors, likely the drive is OK.
And the drive problem you repaired was from turning off the machine. Which happens.