Print 103 comment(s) - last by MrPoletski.. on Aug 14 at 9:22 AM

The latest in a string of problems afflicting the new MacBook Pros, users are now reporting poor hard drive performance, random beeping, and clicking noises reportedly coming from the drives. The issue appears to be with the Seagate 500 GB drives shipping with many of the new MacBooks.  (Source: Apple)
More problems plague Apple's latest laptops, but a fix may be in store

Apple's MacBook Pro laptops certainly have their upsides.  Cut out of a block aluminum, they feature the attractive unibody design and industry leading battery life, while keeping to the ultra-portable 4 lb. and under weight range.  And their Core 2 Duo Intel processors and 9000 series NVIDIA graphics would seemingly make for a good experience, whether you were booting Windows Vista (or Windows 7) or OS X.

However, the newly launched luxury notebooks have not been without problems.  Early on their SATA speeds were found to be capped to 1.5 Gbps -- an update removed the cap and allowed transfer speeds of 3 Gbps.  Additionally, some of the new MacBook Pro laptops have experienced display issues, with many users reporting failing graphics.

Now Apple has another quality headache on its hands.  At least a couple hundred users have reported that Seagate 500 GB hard drives on their new 15" and 17" MacBook Pros have been experiencing poor performance, as well as making random beeping and clicking noises 20 or more times a day.  The Apple Support forum has an 82-page, 1000+ comment thread on the issues.

Describes one user who goes by the screenname Wessto:
I recently purchased a new MBP 15, 3 Ghz, 500 GB 7200 rpm hard drive, build-to-order. The hard drive appears to be a seagate ST9500420ASG. I am experiencing a strange hard drive click followed 80% of the time by a beep. It is definitely not a beep from the speaker. Additionally, it happens at any time, even when the computer is sitting on a perfectly still table. It is exactly the same sound as what is documented at" rel="nofollow

and mine too appears randomly approximately 15-20 times per day. It does not appear to matter if the computer is under light or heavy use and it seems truly random when it occurs. Another user on youtube has also experienced this with their new MBP 15 and sent me a wav file with the same sound mine is making. So far, his experience is that it does NOT occur under bootcamp. This leads me to believe that it is something specific to OSX. Turning off the "put hard drive to sleep when possible" does not seem to make any difference. I have not personally tested bootcamp on my machine to confirm that mine is the same, but the original poster of the youtube video linked above also seems to think it is OSX specific.

Some users are reporting that the beeping is becoming less frequent, possibly due to a firmware update.  Other customers, though, are becoming frustrated.  Stated one MacBook owner, speaking to Apple blog site AppleInsider, "The crazy thing is that you can read comments about AppleCare Engineers stance on this issue: 'Its normal behavior,' (and) 'Apple´s Working on a fix.'  Also, some of them are recommending doing a complete reinstall, when this issue is factory related."

Apple reportedly is working on a full fix for the problem.  Representatives from Apple, according to affected customers, reportedly have told their customers that Apple is "highly aware" of the issue and that finding a fix is one of the company's "highest priorities."  However, they ask that for the time being users "live with" the problems plaguing their pricey purchases.

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

RE: Jason biased?
By crystal clear on 8/9/2009 7:05:28 AM , Rating: 2
Remember Microsoft & the Xbox episode...they denied the existance of the problem ,until one day they took upon themselves a HUGE multi million dollar charge for the defects/repairs/replacements etc.

Hey you cant trust anybody these days.

RE: Jason biased?
By ChristopherO on 8/9/2009 2:17:24 PM , Rating: 2
Multi-billion dollar charge actually. That's an interesting one... I don't know if they actually knew at ship time, or if it was something that only became apparent when consoles had a couple-year burn-in. Realistically, those things were probably QA bench tested for a couple weeks before deeming the hardware good-to-go. I don't think anyone had a problem in the early days, it might have been months of usage before they started failing.

Microsoft ultimately did the right thing. Not sure if it was public pressure. However they did behave semi-correctly. A company shouldn't admit fault until they can prove the problem. It's almost like the lawsuit answer -- "We don't talk about pending litigation". It stinks to be on the receiving-end of that answer, but a firm needs to protect itself until it can figure out what's going on. It's annoying for customers, but better for the shareholders (i.e. almost everyone on the planet with a 401k).

In this case it was frustrating to be a user, because it obviously existed as an issue. I like the fact that they back-refunded everyone who had that problem. In the end they were okay. It's unlikely we'll ever know why they did that. I'm guessing they would have done it anyway, not because they're good human beings, or even public pressure, but millions of people would have never trusted their name again, and they couldn't afford that level of alienation. Companies have to keep their customers, and not "making good" would have ended the Xbox brand.

"We can't expect users to use common sense. That would eliminate the need for all sorts of legislation, committees, oversight and lawyers." -- Christopher Jennings

Copyright 2016 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki