Originally Posted by ValSalva
I purchased a 15" MacBook Pro 3.06GHz, 500GB 7200 RPM, 4GB of RAM on the day of WWDC and it arrived on June 16th. I've had no problems with beeping, clicking, or system hangups. It has worked perfectly from day one.
It's not clear how common this problem is yet. Clearly the majority of June MacBook Pros with 7200 RPM drives do NOT have this problem or the coverage and complaints about it would be much more extensive. Heck, the SATA 1 issue, though present in all new MBP's, hardly affected anyone materially and it was widely discussed.
Just a guess: this is a Seagate issue. Seagate is about as customer unfriendly as NVIDIA. For the customers that are affected Apple will probably end up eating the cost to replace the defective hard drives.
This is something that keeps getting misrepresented from the Apple forum. It's not 7200 RPM drives. People have been using 320 GB 7200 RPM drives for over a year now without any problem. It's specifically the 500 GB 7200 RPM ST9500420ASG
drive made by Seagate (obviously, as only Seagate is making 500 GB 7200 RPM drives at this point).
I don't know how many people have the drive to say how overwhelming the issue should be. It's not a standard configuration, it's a CTO, and only available in the higher end models. Within the first two weeks of availability, there were literally hundreds of complaints of the issue on the Apple forums. Given the short availability, and the fact that it was a high end CTO only option, I'd say that it's a fairly pervasive problem.
However, I'm glad to hear you have the same drive without any problem. That would suggest, if you're correct, that there were bad drives and good drives. It's just a matter of getting a replacement. As I said, replacing mine with a Seagate 500 GB 7200 RPM purchased from NewEgg fixed the issue for me.
Go to the forums and look for the video links. A user recorded a game of Halo which beautifully illustrates the problem. The game will freeze for a second every time the drive beeps. This happens consistently. The problem is, at the moment, Apple calls this behavior "normal." Pardon my French, but what a fucking joke. Normal?