Last month I bought a brand new MBP 13. I brought my new machine home and ran software update as a matter of course. The EFI firmware update was one of the updates that was pushed to me, and I clicked ok (how I wish I had been aware of this thread at the time!) Everything seemed fine at first. The next day I pulled my 320 gig WD Scorpio drive out of my previous MBP (mid 2007) and installed it in the new machine, doing an archive and install on the OS.
Since installing the new (old) drive, I have been having all of the problems described here: intermittent beachballs which take the system away for from a few seconds to several minutes, and which seem to appear for no apparent reason. Usually, if you wait long enough, the system suddenly "wakes up" and catches up with what it was doing. Once I see the first beachball, the occurrences become more and more frequent, often resulting in the whole thing freezing hard, leaving no way out short of a hard reset.
I have verified that there is no particular CPU activity during these episodes that would warrant this behavior (I've been keeping Activity Monitor up on my second display), so its not as if the CPU is maxed out. The system just... stops and waits.
Also, on several occasions, reboots have been verrrry long in coming (5-20 minutes) and on two occasions I have just gotten the flashing grey folder. Usually, however, the system seems to boot normally.
What is so frustrating is that there seems to be no rhyme or reason to the behavior. My system can work for hours at a time without a problem. It is not clear what triggers the issue, although certain things
appear to precipitate the onset of beachball mania, among them use of Parallels, and possibly iDisk synchronizing. Once beachballs begin appearing, it makes no difference how many apps I am running, and as I mentioned there is no correlation between CPU activity and system behavior that I can see.
I have checked out my HD using Disk Utility repeatedly, and it always reports that the disk is OK. I've done hardware tests on the RAM and it checks out.
I write all this not because I have anything particular to add to the gloom, but to add my voice to the chorus in the hopes that Apple will take this issue seriously. My machine is useless for the public presentations that I do because I can't trust it. Apple, I hope you are listening!