I was having the same issues with a 13" Unibody MB, and have a possible fix here. I've been running for four days now with no crashes or never ending beachballs.
Below is an advice from OliverF at Apple Support Discussions The utility mentioned just checks the drive you have now. You could still be having difficulties with other drives. A speed test does not say much regarding the state of the drive.
"The most objective way (to test drives) is to download SMART utilities:
http://www.volitans-software.com/
Then click on "Attributes" "Show all".
Line "ID 199: UDMA CRC Error Count should be 0, if you see other or increasing numbers there you are experiencing the issue.
Basicaly what happens is that if there is a critical frequency of CRC errors, the beachball will start popping up as the operating system is trying to recover from the SATA bus errors."
Is this problem only affecting SATA 3.0 drives or also the SATA 1.5's?
only those 09, macbook pros patched with 1.7 efi firmware.
I have the 250gb hitachi drive without 1.7 firmwareI've run the AJA Disk Read/Write test. Would you run this test so we can compare results? I have Firmware 1.7 installed and the access to the HD is terrible slow. I got an MBP with the stock HDD 250gb.
You can download the application from http://www.aja.com/ajashare/AJA_System_Test_v601.zip
Use these settings:
Test: Disk Read/Write
File Size: 1.0GB
Video Frame Size: 720x486 8-bit
Disable file system cache: checked
My results were,
Write 76.4MB/s
Read 4.7MB/s
I've noticed that the write speed is constant through the whole test, while the read speed is up to 80MB/s for 125 frames and then goes down to 1-2MB/s for another 125 frames and then goes back to 80MB/s.
It would be great if someone with Firmware pre-1.7 can run this test too so we can see the difference.
thanks
Adding to p3ncil, it appears to only be affecting 13" and 15" as those are the machine the update was pushed to.
And it appears that it can affect any 13" or 15" MBP that has this EFI 1.7 update, regardless (irregardless for some) if it is SATA-I (1.5) or SATA-II (3.0).
Ah ok, I just wanted to make sure since I have seen some posts on different forums that suggested their issue went away when they switched to a SATA-I drive. But based on your feedback it doesn't seem like it would work for all.