Interesting...
I connected the the 1TB drive externally, formatted (HFS+ / GUID), then inserted it internally. This time, I could boot into lion!
However, it's acting dodgy. Safari quits automatically. The 1TB drive didn't show during boot and came up with a 'disk was not initialized' error. Disk utility see's it, then I get the beach ball and Disk utility shuts down....
Do you think this means that it's a SATA3 issue or an issue with the caddy combined with the HDD?
If the optical drive worked/works fine then the port should be fine. That leaves the caddy. These things are cheap, it's not unlikely for someone to get one that's defective.
Not if you use a WD HDD:Just be aware that if you put your HDD in the optibay you'll lose the SMS protection.
No. See also:To correct one of the posts above regarding speed...
SATA-I = 1.5Gb/sec = 187.5MB/sec
SATA-II = 3Gb/sec = 375MB/sec
SATA-III = 6Gb/sec = 750MB/sec
Bits / 8 = bytes![]()
Interesting... I've tested both Caddies with the 500gb drive internally and they work perfectly. I'm using one of them now with the SATA2 500GB drive. The caddies look a bit like this one http://www.ebay.co.uk/itm/2ND-SATA-...-MacBook-Pro-Unibody-SuperDrive-/320755696041
Does that rule it out or could the 1TB thing cause a difference. I'm happy to buy another caddy if one is different to test.
Could it be anything else?
Interesting... I've tested both Caddies with the 500gb drive internally and they work perfectly. I'm using one of them now with the SATA2 500GB drive. The caddies look a bit like this one http://www.ebay.co.uk/itm/2ND-SATA-...-MacBook-Pro-Unibody-SuperDrive-/320755696041
Does that rule it out or could the 1TB thing cause a difference. I'm happy to buy another caddy if one is different to test.
Could it be anything else?
Newishmacguy,
The main bay has the 750gb 7200 rpm XT. Boots cold to ready to go in 37 sec. The 1TB 5400 rpm in the optibay was cloned off the 750gb with Carbon Copy. It boots in 28sec from the optibay. My opinion is it loads applications faster and obviously boots faster.
This is what I ordered, it really looks to be virtually identical.
http://www.amazon.com/gp/product/B00AUA2XGO/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1
Do you know if the 500GB drive you tested is SATA-II or -III? I'm just thinking if one is SATA-II and the other is SATA-III then that doesn't rule out the caddy or cable if the drive is trying to negotiate SATA-III and is failing, causing the drive to not show up at all. Size shouldn't have any bearing on whether or not the drive works in the optibay.
Do you have a friend or someone local that would be able to help out and test the 1TB+caddy in their MBP?
Other users have reported no problems with using 1TB drives with the optibay in 2011 MBPs, most seem to recommend WD drives but they seem to have had luck with other brands.
There's only so many things that it can be.Other than size, what's different between the 500GB and 1TB drives?
Do you have a friend or someone local that would be able to help out and test the 1TB+caddy in their MBP?
Other users have reported no problems with using 1TB drives with the optibay in 2011 MBPs, most seem to recommend WD drives but they seem to have had luck with other brands.
There's only so many things that it can be.Other than size, what's different between the 500GB and 1TB drives?
Anyone got a 1TB drive working in their optibay?
I have an early 2011 MBP with a SSD (main drive) + HDD (optibay) combo.
I was using a 500GB HDD in the optibay successfully but once I inserted a 1TB drive (7K1000) which caused all sorts of drama including:
- getting stuck at grey screen on boot; and
- disabling keyboard and mouse after booting to Recovery / or USB drive.
When I remove the 1TB drive from the optibay and insert the 500gb drive again, everything works sweet. But place the 1TB drive in there and whamoo, drama ensues.
Have I bought the wrong drive? I just wanted the extra space. Is the 7K1000 causing drama because it's SATAIII in a SATAII optibay (early 2011 mbp)?
Cheers
PS. my SSD is a samsung 830. When I put my SSD in the optibay and the 1TB in the main drive, I got stuck at a grey screen also, but this time it was as if there were 0 drives :/
When I switched the drives back (SSD in main, HDD in opti), it was all good again... weird..
P.P.S There's nothing wrong with the 1TB drive when I use it externally. I can plug it into my seagate thunderbolt adapter and it runs perfectly. In fact, I've used the 1TB drive for 24 flawless hours before deciding to move it inside the MBP.
Thanks NewishMacGuy
I've decided to go with option 2 - however, this option isn't working because of the reasons in my initial post. The 1TB HDD is causing the optibay to act strangely...
I'm going to try a fresh install on it to see if that works.
Interesting. Perhaps the early 2011 MBPs don't like Hitachi 1TB drives...
Most of the people I've come across seem to be using 1TB WD drives.
It's really quite a bizarre malfunction
Interesting...
I connected the the 1TB drive externally, formatted (HFS+ / GUID), then inserted it internally. This time, I could boot into lion!
However, it's acting dodgy. Safari quits automatically. The 1TB drive didn't show during boot and came up with a 'disk was not initialized' error. Disk utility see's it, then I get the beach ball and Disk utility shuts down....
Do you think this means that it's a SATA3 issue or an issue with the caddy combined with the HDD?
Hi, I used to have the same problem when using an 1TB-7200rpm-SATA3 Hitachi drive in my late MBP 2011 15"
I plugged it to the main bay and it was recognized at 6Gbps. But it ran very unstable as sometimes the whole drive hang for 20-30s (I/O error in the system log).
It turned out the root cause was neither my MBP, nor the SATA cable, but the Drive itself. When running at full SATA 3 speed, it will be very unstable like. I contacted Hitachi support and ask them for the tool which can modify the drive so that it will run at SATA 2 only. When I got the tool, I used it to force the drive running at SATA 2 speed only. And the drive is now running happily in my machine in the main bay at SATA 2 speed, along with my SSD running at SATA 3 in the optibay.
Hope this information could help you who is having trouble with this infamous drive.
Very, very interesting. What's the tool?
Is it a firmware update or something?
I'm going to try this.
Newishmacguy,
The main bay has the 750gb 7200 rpm XT. Boots cold to ready to go in 37 sec. The 1TB 5400 rpm in the optibay was cloned off the 750gb with Carbon Copy. It boots in 28sec from the optibay. My opinion is it loads applications faster and obviously boots faster.
That doesn't make much sense.
Have you ran Blackmagic against both drives to see which actually provide more throughput?
I've replaced 5400RPM drives with 7200RPM drives in laptops numerous times, including using XT drives in place of the original 5400RPM drives, and at no time was the old 5400RPM drive faster in any way.
We are talking about the new Seagate 5400rpm 1TB Hybrid against the old Seagate 7200rpm 750GB Hybrid, not just a stock 5400rpm drive vs. 7200rpm.
Even so, bigger but slower spinning drives can theoretically be just as fast as or possibly faster than smaller and faster spinning drives due to platter density. I'm no expert, but would imagine that if the platters on the 5400rpm drive are more than 1.333 times as dense as those of the 7200rpm drive, the slower spinning drive will be faster. Then there's also the question of caching size and efficacy.
___
My bad, missed that he said it was the hybrid earlier in this thread.
That said, Seagate specs show it's still slower than a 7200RPM hybrid in terms of latency and reviews comparing the 3rd-gen 5400RPM drives to the 2nd-gen 7200RPM drives agree, the newer drives are slower once you hit the platters.
Since data isn't written in whole and sequentially on the drive you still have to deal with seek times, which will be slower on slower-spinning drives. That's just physics. I understand your thinking about density, but the data is still spread all across the platters and the heads still have to get to it.
I'm not much of a fan of the hybrid drives. Marketing spin makes some promises that are never lived up to with them, mainly due to the limited amount of flash that they have on them, and maybe/possibly poor algorithms when generating and making operations against the drive's heat map. The latter would've most likely been fixed by now, so I doubt it's that. It's most likely the limited amount of flash on them.