Hi,
My MacBook Pro is driving me crazy lately. Often it starts beachballing when doing even the slightest thing - opening/switching tabs in Safari, switching apps... But even more annoying and understandable to me is that it also goes mad when resuming from sleep. I open up the lid and hell breaks loose. Typing in and checking my password can take up to a minute and after, my system can be unusable for up to ten(!) minutes, again beachballing, beachballing, beachballing. Whenever I see this bloody animation, at the same time I'm tortured by that continuous rrrrrrrrrrrrttgrrrrrggggtttttt sound of the hard drive. I have 4GB of RAM and the described behavior even occurs when no heavy apps (e.g. Parallels) are open. Process Monitor doesn't indicate I'm low on memory either. The drive is an Hitachi HTS545050B9SA02 placed by Apple. I tried to find some software to tell me what actual process is causing this extensive hard disk activity, but didn't succeed. Finally, a permissions repair didn't do much.
It's ridiculous that it's faster to restart OS X than to have it have it resume. Suggestions please?
My MacBook Pro is driving me crazy lately. Often it starts beachballing when doing even the slightest thing - opening/switching tabs in Safari, switching apps... But even more annoying and understandable to me is that it also goes mad when resuming from sleep. I open up the lid and hell breaks loose. Typing in and checking my password can take up to a minute and after, my system can be unusable for up to ten(!) minutes, again beachballing, beachballing, beachballing. Whenever I see this bloody animation, at the same time I'm tortured by that continuous rrrrrrrrrrrrttgrrrrrggggtttttt sound of the hard drive. I have 4GB of RAM and the described behavior even occurs when no heavy apps (e.g. Parallels) are open. Process Monitor doesn't indicate I'm low on memory either. The drive is an Hitachi HTS545050B9SA02 placed by Apple. I tried to find some software to tell me what actual process is causing this extensive hard disk activity, but didn't succeed. Finally, a permissions repair didn't do much.
It's ridiculous that it's faster to restart OS X than to have it have it resume. Suggestions please?