Currently Being ModeratedFeb 4, 2014 4:15 AM (in response to robogobo)
The fact that both are running 10.9 is certainly helpful, though if the one being migrated to is running an older version of 10.9 that could cause a problem too.
The Migration Assistent has a much greater chance of failure if there ever was a PowerPC Mac's data moved over, since it does not take account for the differences of PowerPC and Intel Macs. Instead this tip is required for migrating:
Currently Being ModeratedFeb 4, 2014 4:26 AM (in response to robogobo)
Migration/Setup Assistant via ethernet network either works or it doesn't and all too often it doesn't without providing any useful clues as to why. WiFi is too slow for anything more than a small amount of data. If the new computer is a Mac Mini using FireWire target disk mode is the best solution but since all the other Macs don't have FireWire that means purchasing a Thunderbolt/FireWire dongle which may not be needed afterwards. That’s $30 wasted.
For this reason I've been recommending that users use a USB external drive to back up the old computer and then use it with Setup Assistant to migrate to the new computer. As a brody mentioned, migrating from a PPC to Intel computer is somewhat more problematic. The solution there is to migrate only data or to prune the old computer of incompatible software first.
Currently Being ModeratedFeb 4, 2014 4:43 AM (in response to robogobo)
Both machines are on 10.9.1 and we've NEVER used a PC, haha. I'm setting up the 17th Mac over 18 years. Before 10.9 I had five running like a well oiled machine in the house. I've become an early adopter because I can usually handle the glitches. But it's never been this bad.
I'm currently copying the user folder over manually. I've exhausted every other possibility with Migration Assistant. I should have done it the old fashioned way from the beginning.
Apple needs to SLOW DOWN and make sure their stuff works. They seem to be giving in to the pressure to pump out a new feature every minute. I preferred when they just held back and made sure it just worked. User experience trumps features. 10.9 is the worst version of OS X ever. So many problems. I generally know my way around a Mac better than 99% of the people I know. I can't imagine how bad it must be for newbs.
Currently Being ModeratedFeb 20, 2014 4:01 PM (in response to robogobo)
I agree completely and have run into the same exact problem trying to migrate from a mid 2010 MacBook Pro running Mavericks to a brand new rMBP. I spent an entire weekend just trying to get Migration Assistant to "see" Setup Assistant on the new computer ... the target could see the source but the source just would not see the target. I finally got it working by creating a completely separate private network between the two machines and directly connecting them via Ethernet cable. Now I have the exact same crash reported here. Setup Assistant starts to interrogate Migration Assistant and then Migration Assistant crashes and the old MBP ends up at the login screen again. I've tried booting the old machine in safe mode but it still does the same thing. I'm going to try target disk mode as soon as my thunderbolt-to-firewire adapter arrives. Apple's definitely not making this move easy.
Currently Being ModeratedFeb 20, 2014 4:08 PM (in response to robogobo)
I would either:
1. call APple
2. take it to a genius bar, or
3. do it the old fashioned way - copy over your docs, pictrues etc and just re-enter other stuff. Its not that hard.
One caveat - you need ot make the users/you/library visible.
Currently Being ModeratedFeb 20, 2014 4:59 PM (in response to Grant Lenahan)
I could certainly do it manually but it would take more time than I currently have to devote to it. This is a computer I use to help support the systems I'm responsible for at work and it just shouldn't take days of fiddling to get it up and running. I was able to get the migration to work properly going from Mountain Lion to Mavericks but had issues with the network configurations that were transferred over. I have many specialized network configs set up for specific tasks around the office and for one reason or anther the migration appeared to swich ethernet for wifi settings and I didn't feel like going through all of them to re-enter the proper settings. I thought that perhaps going from the same OS release might clear up these issues so I upgraded the 2010 MBP to Mavericks figuring that it would eliminate one change (common wisdom being to never make more than one change at the same time if you can avoid it). Guess I was wrong ...
Currently Being ModeratedFeb 23, 2014 11:12 AM (in response to CGiannetto)
Just to follow up on my posts to this thread, I was able to get "migrated" using a Thunderbolt-to-Firewire cable, putting my old MBP in target disk mode. Everything transferred over without issue, including all of my network settings (no confusion this time about built-in-Ethernet and WiFi). The new machine (2.6GHz) sure is fast