I'm considering buying a new MacBook Pro after today's refresh, and I am wondering if OS X handles simply pulling a drive out of one MacBook Pro and putting it in another. I know that in the Windows world this is — most of the time — possible, but I have never tried it with OS X. Does the OS handle the sudden change in hardware, or does it 'sh*t bricks' and abort mission? In theory you'd think it could handle it, but anyone with definite experience would be good.
MacBook – Moving Drives Between Macs
hard drivemacmacbook promigration
Related Solutions
I went through a lot of the same questions you were asking and had to search high and low to find my answers.
First of all, this is my setup:
MacBook Pro Mid 2009
Optibay: SSD
HD Bay: Original Mechanical HD
8GB RAM
OS X Boot Disk: SSD
Windows Boot Disk: Original Mechanical HD
SSD: Mac OS X
Original Mechanical HD: Windows 7 Partition / Mac OS Extended (Journaled)
Ok, so here is the reasons for the described setup. I, like you, put the SSD in the Optibay because of the motion sensor issue. The Optibay doesn't have a motion sensor and the Original Mechanical HD isn't motion sensor equipped. So I put the SSD in the Optibay and boot into OS X.
The next issue I faced was the fact that Mac's can freeze when trying to do hibernate with an SSD in the Optibay. So I disabled Hibernate. This had a few nice perks, such as faster sleep and resume and the gaining back of 8 GB of SSD space that was wasted by the Hibernate RAM Image that Hibernate will make before your machine runs out of battery. Now obviously, this means that if I was working on something important and my battery dies, then I will have lost it forever. So this is a risk you will have to be willing to take but it is up to you. Personally I only do really important work while the charger is plugged in because of the fact that I am doing that work for 8 hours straight.
Update
Now some searching on the issue recently showed me that as of 10.8.1, this issue of freezing when waking from sleep had been fixed. I have not tested this personally on my machine because of the fact that I am used to having hibernation disabled. I don't like or need hibernation personally and I like the extra space I get from disabling it. Now the article says that it has been fixed but it does not state anything about Optibays, it only states its fixed for the SSDs in the Original HD Bay. I would recommend testing it out though, leaving Hibernation turned on, sleeping your machine while NOT doing any important work, and seeing if it wakes, doing it multiple times, just to be sure. If it does freeze or cause issues, then I would recommend disabling Hibernation.
End Update
You can disable Hibernation with the following command:
# Check Current Hibernation Status
$ sudo pmset -g | grep hibernatemode
hibernatemode 3
# 3 is the default mode, we want to change this to 0 to disable disk writes.
# Disable Hibernation
$ sudo pmset -a hibernatemode 0
# Now we can remove the old sleep image
$ sudo rm /var/vm/sleepimage
Now as for Windows, since I had Windows Installed on a 50 GB partition of the Original Mechanical HD, I just left it there. Installing Windows is a pain the butt and I didn't want to do it again. Also, I am rarely ever on Windows, I only use it to play some games and to do some Windows Development on every once in a while. Also, by keeping it there, you keep windows from having any possible issues with booting from the Optibay (though when I had the Original Mechanical HD in the Optibay as a test, it booted just fine).
Since I use the SSD for pure Apple Stuff, I took the original Mac OS X partition that was on my Original Mechanical HD and just reformatted it to extra space for my Mac. I download and store all my heavy giant waste of space extra files on that partition so I don't take up space on my precious and fast SSD in the Optibay. You could also partition it in a format that both Mac OS X and Windows 7 can access, such as ExFAT, so that they both play nice with the space and you have extra storage that both can share. Very convenient.
Now after you get all your pieces in place, be sure to go to System Preferences > Start Up Disk and set your SSD as the startup disk. If you don't, it might delay your boot time because it thinks it has to look for the disk in the Original HD Bay.
Another tip that you will see all over the place is to enabling TRIM on your SSD. You only need to do that though if your SSD DOES NOT already do it for you. My SSD did not require me to enable TRIM, so I didn't. Enabling it when you don't have to can sometimes slow down performance slightly but it will not hurt anything. Just check your manufacturers website or do a google search on your drive to see if its necessary.
Another thing you see all over the place is people recommending software for doing a copy over to your new SSD. Copying over your SSD is usually no problem, but issues can occur sometimes, especially if you copy over your windows partition as well. I, like many others, will recommend just doing a clean install and copying your data over and reinstalling your programs. Now obviously this could be a huge pain in the butt but it is completely worth it. It will usually allow you to take stock of whats on your drive, and help you trim the fat from your file system and reorganize yourself. I have done both, complete copy and clean install and copy and can say that my machine seemed slightly snappier with the clean install. My boot time dropped by a second or 2 as well.
Doing all of this and taking the precautions with Hibernation, my computer has never been faster. It boots in 6 seconds!
I highly recommend an Optibay if you can, it can make all the difference. I hope that this long answer helps you out and answers your questions about storing your SSD in your Optibay. Personally it was the best choice for my computer and my needs.
So there are a bunch of comments about the merit of the question which it seems you e taken the time to look at and assess. I'll jump right in to starting the discussion on upgrading.
Firstly, to be clear you're looking at a new early 2015 13" MBP (I assume you're not interested in a 15", which can support quad core processors and add a whole new layer to the discussion).
Apple's tech specs can be hard to track down, but it looks to me like you got the same processors I did. The i7 supports a turbo up to 3.1 GHz and 4 MB of cache, with the i5s boasting 2.1 and 2.7 GHz processors and 3 MB of cache. You're right in that the i7 supports VT-d, but you'll need some fairly heavy duty software to take advantage of it. The answer about VT-d is that it really depends what sort of virtualization software you're using, my guess being that unless you want to use expensive commercial software, Oracle's VirtualBox will be the first to support that (though I have no reason to expect this, or know when).
This brings us to the next level: is the i7 worth it over the i5 (will there be notable performance gains)? For you (and others with this question), probably. The increased cache, better cache coherency, and outright speed increase will be what you notice. Being that all the processors for the 13" are dual core, I was unable to find evidence that there is any significant difference between hyper threading moving up and down Intel's CPU line (unlikely, they all use the same basic core).
Related Question
- MacBook – Can a 2009 MacBook Pro use more memory than Apple’s ‘maximum RAM’ figure of 8 GB
- MacBook Pro Retina, questions about 2nd monitor for gaming
- Apple Travel Adapter – Does It Work in India?
- MacBook Pro USB-C Charging – Using Low-Wattage Power Supply Consequences
- MacBook Pro Startup – Booting MBP 15″ 2015 Without Battery
Best Answer
In general, this is a very safe, OS X boots other hardware in general situation.
However, when new hardware is released - often a special build is made and until the next revision or two of software, you can't boot that hardware so you'd need to take a hard drive from the specialized machine to an older one instead of the other way around.
It's far safer to migrate from a Time Machine or target mode or from running OS using file sharing / network. That way each machine has the correct OS and can flag apps or system files for non-transfer when there is a known problem migrating them.