- #MACBOOK PRO MIGRATION ASSISTANT PROBLEMS INSTALL#
- #MACBOOK PRO MIGRATION ASSISTANT PROBLEMS LICENSE#
- #MACBOOK PRO MIGRATION ASSISTANT PROBLEMS MAC#
I abandoned that whole path and selected only Apps for Migration Assistant, which toodled over quite quickly. I was baffled, but I had fooled around with this long enough. I looked at the connection window and for some unknown reason it showed that I was still using WiFi. I quit the process of Migration Assistant and on both machines, turned off WiFi and started over, but still it was transferring at 6MB/sec. While WiFi should have been 10X as fast, I decided to try and kill it off anyway. 524megabits/sec ÷ 8 = 65megabytes/sec but I’m only getting 6.
I went back to the iperf tests that Steve and I conducted on the Netgear Nighthawk X8 and the WiFi speeds were 524megabits/sec when we tested right next to the Netgear. So why was my transfer going at about 1/16th the speed it should be going? The only thing I could figure was that maybe it was ignoring the cables and using WiFi. Both were blinking on all three involved ports. A graphic on the switch says that if both are blinking you’re getting 1000Mbits/sec. My particular switch is from Netgear, and it has a light on ether side of each port. He looked on the back for the blinky lights. Steve studied the switch itself which said it was gigabit. We looked at the Ethernet cables I’d chosen and verified that they said CAT 6 on them (Cat 5 is only 100 megabits/sec). Sure your mileage may vary on this kind of thing, but with pretty recent SSDs on both machines which I personally have measured at 850MB/sec read/write on the slower machine, those numbers just don’t make sense.Īs my data was simply crawling from one machine to the next, Steve and I studied things to make sure I wasn’t misleading myself on what I had actually set up. Dividing by 60, we get that the 125GB should have transferred in 17 minutes, not 4.5 hours. If I’m transferring over gigabit Ethernet, that means I’m transferring at 1 gigabit per second, so I should be able to move 1000 gigabits in 1000 seconds. There are 8 bits in a byte, so we have to multiply by the 125GB by 8 to get the number of gigabits that were transferred. How long it should it have taken? We’ll have to do the math, starting with converting bytes to bits. So back to our 125GB transferred in 4.5 hours.
I’m hopeful this will help some of you in the future. I want to dig a bit further into exactly what I originally did, give you a problem to be solved, and then walk you through what actually worked in the end to give me a successful migration from the 2013 to 2016 MacBook Pro. Forever is defined as 125GB of data transferred in 4.5 hours. I explained that I hooked the 20 Macs up to a gigabit switch hooked to my router and yet the migration was taking forever.
Two weeks ago I told you the story of how I’d tried to use Migration Assistant for the first time to accomplish the task.
#MACBOOK PRO MIGRATION ASSISTANT PROBLEMS MAC#
Your Mac will feel like it did when it was new.Īnyway, since I’d just had the joy of doing that a month ago, I was uninterested in doing that all again on the new Mac. It’s painful and time consuming (think days before everything is back to “just so”) but the advantages of speed and freed up disk space are enormous. I have lauded the benefits of a nuke and pave over the years on the podcast and I’m a huge believer in doing it around once a year.
#MACBOOK PRO MIGRATION ASSISTANT PROBLEMS LICENSE#
You can drag your documents over from a backup or another Mac, but you don’t bring over network settings or license files or any customizations you’ve made.
#MACBOOK PRO MIGRATION ASSISTANT PROBLEMS INSTALL#
For those unfamiliar with the term nuke and pave, that’s when you erase everything, including the operating system, and then install everything from scratch. When I got the 2016 Touch Bar 15″ MacBook Pro, it was only about a month after I’d done an involuntary nuke and pave on my 2013 MacBook Pro.
0 kommentar(er)
