Has anybody had any problems with new MacBook Pro after yesterday's firmware update with third party hard drive? I got a MacBook Pro 13" recently, swapped the 320 GB hard drive from my old MacBook. After reinstalling the OS for new hardware drivers, everything was working fine.
After the firmware update yesterday, the machine has started freezing randomly; the spinner comes up sometimes when reading or writing to the drive. The hard drive, a WD Scorpio Blue, supports SATA II. My suspicion is that there are intermittent data errors when using the SATA 3 Gbps interface. It could be an incompatibility between the controller and drive or the ribbon cable isn't good enough for newer SATA.
Does anybody know of a way to force the drive or the controller to use SATA 1.5 Gbps? Can I revert to the old firmware?
FWIW, as I said earlier in this thread, this is the same drive I have and it's been working fine in my mid-2009 MacBook Pro (with SD card slot) and it also worked fine in the MacBook Pro (mid 2008) that preceded it.
If your 13" MBP takes the EFI 1.7 update then your machine isn't one of the ones this thread was set up to discuss. However, it's an interesting data point to include.
I'm curious to know, if more people have tried this drive with equal success.
Josh Rafofsky wrote:
If your 13" MBP takes the EFI 1.7 update then your machine isn't one of the ones this thread was set up to discuss. However, it's an interesting data point to include.
Untrue. EFI 1.7 applies to the mid-2009 13" and 15" MBP, which are the machines impacted by the issue which this thread was meant to discuss.
SATA cable is the first thing I mention, then I told them about EFI 1.6 rollback (even though it's not the way to fix something by crippling it). the problem is they're not willing to admit there is a designing error with the machine (probably there are direct orders in place from the command ship). the genius (nice guy) is waiting to hear from Apple Engineering, maybe I should give them more time.
I’m surprised no one has considered suing apple on this.
Remember what is written on Mac book pro documentation: "how to boost your Mac book pro" and then the instructions on how to replace the hard disk.
I decided to take a chance and upgrade my HDD, despite the obvious problems many people are having. I purchased a WD 320GB 7200rpm Scorpio Black and 4GB of Crucial RAM. I did the EFI 1.7 update when it was pushed, as most did. Had no problems after the update. Got the PU when pushed, as well. I decided to upgrade, wanting more space and a faster drive. Instead of a fresh install, I decided to try a drive cloning using CCC. I first used a external enclosure to format the new drive, then did a clone of my old drive via USB. This has worked like a charm. This thing is blazing fast, now. Still running EFI 1.7. Just thought someone may want to try this.
Model Name: MacBook Pro
Model Identifier: MacBookPro5,5
Processor Name: Intel Core 2 Duo
Processor Speed: 2.26 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MBP55.00AC.B03
SMC Version (system): 1.47f2
Serial Number (system):
Hardware UUID: A684C2F3-DABB-5AF6-B584-64C10C9A78C1
Sudden Motion Sensor:
State: Enabled
Today, I replaced the hard drive cable in my MacBook Pro with the EFI 1.7 issue, and now I can't get the machine to screw up again. I don't want to shoot my mouth off and say this is an absolute fix, but it looks good so far (at least with this small sample of 1).
Previously, I posted two videos showing the issue on my machine; one from way back in late July (
http://vimeo.com/5854152), and another just after Performance Update 1.0 was released in mid October (
http://vimeo.com/7078172). In both of those cases, I used AJA System Test to stress the hard drive while playing a video, causing frequent and reliable displays of the EFI 1.7 issue. Using the same test method, I ran through 15-20 passes of AJA System Test and have not gotten a single failure. I'm going to live with this for a while before calling it good, but this is the first time I've not felt compelled to roll back the firmware immediately after (re)installing the EFI 1.7 firmware.
Though I don't want to claim an absolute solution yet, I would highly suggest anyone experiencing this issue go in to your local Apple Store and see if you can get them to replace your hard drive cable. Barring that, you can do it yourself (if you're comfortable with such things) if you buy the part online (Apple Part #: 922-9034). The best instructions I could find online are for the 13" MacBook Pro (link below). It's a little different on the 15" MBP, but not so much that you'll have any trouble — though definitely have Apple do it for you if you can.
iFixit didn't have the part in stock, so I got my cable from PowerbookMedic for about $30. But I definitely would support iFix It otherwise, if for nothing more than their awesome instructions and product teardowns.
I've just got the same problem, after buying an WD3200BEVT (western digital, blue scorpio).
i'm also able to reproduce the same problem anytime, i want to.
after taking my old 120gb toschiba apple HDD, there is no problem..but i need more space.
My system configuration looks like this:
macbook late 2006
10.6.2
Boot-ROM-Version: MB21.00A5.B07
SMC-Version (System): 1.13f3
IOAHCIBlockStorage:
Version: 1.6.0
Zuletzt geändert: 01.08.09 07:57
Informationen: 1.6.0, Copyright Apple Inc. 2005-2009
Art: Intel
Architekturen: i386, x86_64
64-Bit (Intel): Ja
Ort: /System/Library/Extensions/IOAHCIFamily.kext/Contents/PlugIns/IOAHCIBlockStorag e.kext
Kext-Version: 1.6.0
Lade-Adresse: 0xfd9000
so i haven't got the efi 1.7 ⚠
where's the poblem?
Well... I've just ordered the SATA cable from iFixIt (they had a few in stock for the 13" Pro). I'm slightly concerned as they are are basically used... but fully tested. Hopefully they're fully tested with SATA 3.0.
This thread is being locked as it is getting long and causing some browsers to time out. The thread is being continued in [Firmware update and SATA II hard drive (continued)|http://discussions.apple.com/thread.jspa?threadID=2267098].