-
All replies
-
Helpful answers
-
Jun 14, 2013 11:19 PM in response to MinnNurseby mende1,Welcome to Apple Support Communities
Disconnect and connect your Ethernet cable. If this doesn't continue that migration, restart your computer. Maybe your files have been transferred, but if not, you will have to transfer your files again with Migration Assistant
-
Jun 15, 2013 9:22 AM in response to mende1by MinnNurse,Thanks for replying. The ethernet cable disconnect and reconnect didn't work. On the phone with Apple Support now. I'll post back with resolution. Perhaps a restart is required as you mention.
-
Jun 15, 2013 10:29 AM in response to MinnNurseby BDAqua,Have you used Disk Utility to repair both Hard Drives?
-
-
Jun 15, 2013 1:19 PM in response to MinnNurseby Alfred DeRose,Upgraded my MBP two weeks ago and I also thought Migration Assistant was hanging / Cancelled the first run and started again late into the evening. After a couple hours I decided to just go to bed and see what happened in the morning. Come the next morning Migration Assistant was working albeit very slowly. About 18 hours after starting it was done.
I'm fully away about 250 GB in my Home directory will take some time but this still seems a bit out of proportion to me. In the end, it worksed but this of course does not mean there isn't a problem.
Please let us know what Support says.
-
Dec 11, 2013 10:10 PM in response to MinnNurseby tarynitup,I am having the same issue. Migrating data from mac mini to new imac. It has been stuck at 220 hours for at least 9 hours. We started the migration of data over 24 hours ago. The wifi is off on both computers, using an ethernet cable. There is a lot of data on the mac mini, not sure how much but couldn't be that much. What should we do?
-
Dec 12, 2013 5:26 PM in response to tarynitupby tarynitup,I unplugged the ethernet cable and that did the trick. It jumped up to 280 hours, I figured that it was a good sign and went to bed. When I woke up, it was done.
-
Dec 12, 2013 11:57 PM in response to tarynitupby Alfred DeRose,Sounds like you may have had a bad cable. Glad it worked out.