Currently Being ModeratedMay 17, 2012 8:39 PM (in response to alansky1)
Did you update migration assistant on the old MBP before you started?
Currently Being ModeratedMay 17, 2012 8:53 PM (in response to softwater)
Both machines belong to a friend. I did not personally update Migration Assistant on the old MBP, and I don't know how recently the owner had run Software Update. Since the new MBP was starting up for the first time, it is probably running 10.7.3.
Currently Being ModeratedMay 17, 2012 9:07 PM (in response to alansky1)
Not updating MA on the old machine immediately prior to migrating to a new machine is the most common cause of problems.
If you can cancel the operation safely, I'd suggest you start over.
Currently Being ModeratedMay 17, 2012 9:53 PM (in response to softwater)
Good to know. i've never read about this issue. Since I won't have access to the machines again until tomorrow, and since the transfer does appear to be progressing very slowly, I have little choice but to let it run overnight. I wouldn't want my friend to abort the transfer when I'm not there. Thanks for the helpful information!
Currently Being ModeratedMay 18, 2012 9:57 PM (in response to softwater)
Amazingly enough, the transfer finally finished after more than 20 hours. Everything seems to be working normally on the new MBP. It turns out that Migration Assistant was already up-to-date on the old MBP; and according to the Apple Knowledge Base article on migrating data in Lion, starting the old MBP in target disk mode should have worked the way it has always worked. My friend thinks we should chalk this one up to sunspots, and she may be right.
Thanks for your help!