In trying to get a little more life out of my 2009 Mac Book Pro (MBP), I decided to pick up a Solid State Drive (SSD). My original plan was to clone the old drive over to the new SSD, but that plan was eventually discarded in favor of a clean install of OS X El Capitan.
The issues I ran into with the clone attempt were several. First, the new drive was 960GB while the existing drive was 1TB. In Yosemite, I could get into Disk Utility from the option key boot menu. The problem was the disk recovery partition booted from was part of the boot drive’s main partition I wanted to resize. That problem, on top of having to boot into single user mode and run /sbin/fsck -fy a couple of times to fix some problems before I could try to resize, made me give up as I kept getting a can’t unmount or mount error to complete the resize. So I updated to El Capitan on the MBP and was surprised to see that I could more easily resize the partition using the El Capitan version of the Disk Utility and there was not a warning that it did not succeed due to the mount issue. I booted back into El Capitan and saw no issues after the resize. So another Disk Utility session was started with the new SSD connected via a USB adapter. I was able to start the restore from the 1TB to the new SSD. I left this running overnight and through the day, but the process appeared to be stalled and I eventually stopped it. At that point the disk recovery/disk utility boot option would start and get about two-thirds complete, based on the progress bar, before the machine would power itself off. The MBP would still boot OS X El Capitan, but I could no longer access the recovery boot option to try another cloning session via the Disk Utility restore option.
I considered my options and actually booted with a live Gparted disk, but decided against a partition resize even though I had a Time Machine backup I made after the El Capitan upgrade. I also tried Clonezilla, but it did not like the fact that the new drive was smaller than the original and even when I did the expert mode option to allow the size difference, it failed to complete the clone of the main partition. At this point, I am thinking I have a nice SSD drive to use somewhere, but not in my MBP.
On the third effort, I started looking at doing a clean install of El Capitan OS X directly on to the new SSD. I will not try to completely recap that process here, but I leveraged the information at http://mashable.com/2015/10/01/clean-install-os-x-el-capitan/#iPW8YGRnrEqp. I will say don’t get discouraged during the creation of the bootable USB drive using DiskMaker X version 5 and the El Capitan installer application. I felt like it took forever during several of the steps, but it ultimately completed. So I opened up the MBP and swapped the SSD in and booted from the El Capitan clean install bootable USB drive. Again, I would say don’t get discouraged with the speed of this process. The time estimates and progress bars seemed like they were tied to some other universe’s clock.
Once I got past the first reboot of the install process, I was asked if I wanted to transfer any data from another Mac, a Time Machine backup or other source. I tried to chose the option for Time Machine and for some reason the My Book drive of my Time Machine data was not seen. I backed up one step and connected the old 1TB drive via my USB adapter and it was seen. I was given a list of items I would like to transfer or migrate over to the new install and I selected my data and applications only. I went ahead and clicked next a couple of times even though the install was still trying to compute the overall size of applications and my home folder. A few minutes later the transfer of data started and as I type this on my wife’s laptop, I have about six hours left to go on the transfer.
Update: The migration of data and applications completed without any issues and my MBP looks like I just did an upgrade versus a clean install at this point. If the folks in Redmond only got this concept, I would not dread a fresh Windows install to fix the cruft that builds up on their OS’es. As far as the new SSD goes, a reboot that would take about four minutes is now only 30 seconds from clicking reboot until I get a login prompt and application starts are much more responsive. One program, Microsoft Office 2011, did want me to go through the registration/activation process when I opened the program the first time. Luckily, it was installed via an employee purchase program with the registration key delivered in e-mail or I would still not be able to use it. I now keep my software keys in my password keeper, KeePass, to avoid having to sift through e-mails to find keys.