Q: Firmware update and SATA II hard drive

Hi,
I don't think it is a firmware update issue.
Of course with 1.7 more people are affected.
The same problem I have with firmware 1.6.
I'm using Opt Drive and have two SSD (Super Talent).
If I use both as RAID 0, I get the same problem.
Ok with 1.7 even installation of MAC OS is not possible.
The installation of OS on the second drive (OptDrive) is working fine with both (1.6 and 1.7).
I guess the length of the cable or the quality is causing the problem.

My recommendation: If some one is going to buy a new Mac book Pro.
He shouldn’t because apple has to do a coupe of Hardware changes.
For sure it is a Hardware problem and not Software.
And for sure apple is well aware about this problem.

You should try with Pacific, an utility able to extract single files from pkg contents.

There is an easy way to verify if it's hardware related (the SATA cable or anything...), or only a software issue:

- Boot on Windows or Linux natively
- Check that you have the SATA operating at 3Gbps (do speed test with an SSD or use a system information software that is good enough to give the correct interface speed).
- Do some heavily disk operation while doing multitasking.

If it's operating correctly on Windows or Linux, then it's clearly not a hardware issue and then you can exclude the SATA cable or any other hardware cause in the list of culprits.
Of course if the issue also occurs on Windows or Linux, than it's probably hardware related.

From what I read on this thread and others, all people who have tested on Windows or Linux have, for now, said that the problem is absent on Windows or Linux. In that case it'd indicate a software issue, and that's clearly what I think it is from what I read as of now.

iFrodo //

You are correct, but I failed to install windows with SAMSUNG 128GB SSD and MTron 64GB SSD using bootcamp and windows installation DVD. Furthermore, when I dumped windows ghost image to those drives, they can boot windows but randomly frozen about 1 minutes. So I think it's a hardware problem.

Message was edited by: anewholic

I tried to install windows /ubuntu several times.
But allwas the same result.
...randomly frozen...

It is a hardware problem for sure...

And apple knows this issue therefore apple do not support any HDD/SSD with full speed.
I have to say this is my first Apple and for sure also my last one

Message was edited by: delmel

Hi folks

I am regarding this thread with a lot of interest.

But I need to tell you, that I have a MacBook Pro 17" (mid-2009) and I really DONT have any of this issues written in this thread.

I am using the latest MacBook Pro 17-inch (mid-2009) with the latest Samsung SSD 256GB, the performance is about 220MB read and 200MB write.

Am I just a lucky guy or does this issue only occurs on the 13-inch and 15-inch MacBook Pro (mid-2009)?

Thanks for providing feedbacks to me.

Yours sincerely

You are a lucky guy and yes it only applies to the 13"/15" MBP as these were the targets for the EFI 1.7 update.

Thank you:-)...

Do you know somebody who has the latest MacBook Pro like I do and had issues with HDD/SSD?

Yours sincerely

I do not.

means that you know somebody who has the same MacBook Pro like I do and he or she has no issues?

sorry about my very interesting question:-)

Maybe I am not sure what your question is? But I can tell you that I personally know two people who have the newest 17" MBP one has a SSD (not sure which one) and the other had the stock HDD that came with it. Neither are having problems with the drives or their machines.

I've been following this thread (along with hundred of others)since it began and I have not seen any complaints or posts about SATA-I or II issues with 17" MBP (SSD or HDD).

nearly 40.000 reads and over 350 replies .. and NO reaction from apple! Great!

Trust me, Apple is responding. All I can say is I have been working with them to resolve this issue.

Message was edited by: nizmoz

I've replaced AppleAHCIPort.kext with the 10.5.6 version and removed /System/Library/Extensions.mkext, didn't solve anything for me.

Did you get an update about the issue from apple? Any information what their engineers are working on?