Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'More symptoms to this "cache" bug' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
More symptoms to this "cache" bug
Authored by: rdstokes on Oct 13, '05 10:29:49PM

This solution helped me today so I thought I'd provide more symptoms to the bug. We're running a PPC Duel G5 on MacOS 10.3.9 in a graphics environment.

The problem occurred after a nice clean restart of the computer. The computer had just gone through monthly maintenance so drive corruption, permissions, launch services, etc. were all in working order. When the computer booted, the Finder would launch, the Dock worked correctly, and the computer ran for about 45 seconds. Then, the fans would race for 10 seconds followed by a spinning ball. If you clicked on a menu, the menu title would darken, but would not pull down. You could switch between open applications but could not execute any commands.

I had two other operating systems on different volumes. If I booted from either of them, the same symptoms occurred. However, if I boot from another volume and immediately trash the volume with the cache, the problem would not occur. In theory, booting from another volume should not result in the same symptoms. Can anyone tell me why it does?

The way I found this post was because I immediately opened a Terminal window after boot and ran the top command. Once the fans raced, I noticed that the unix process "coreservic" was hitting 98%, 99%, 100%, or 101%. A simple search on coreservic or coreservicesd got me to this thread and helped me resolve my customer's issue.

Just to recap, here's the solution:
Boot into single user mode (hold Apple-S keys while you turn on machine) and type:

root# cd /
root# mv /Library/Caches /_Library_Caches
root# reboot



[ Reply to This | # ]
More symptoms to this "cache" bug
Authored by: ioshy on Nov 29, '10 09:34:39AM

Worked like a charm for me.
I did that because both "mdworker" and "coreservicesd" were crashing repeatdly on my Mac Pro Dual Core Intel Xeon running Mac OSX 10.5.8

Thanks for the hint !



[ Reply to This | # ]