Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

A multiple-drive Mac Pro Migration Assistant issue Desktop Macs
If you order a BTO Mac Pro with two internal hard drives, you may want to make a note of this. To make a long story short: Before firing up a new Mac Pro configured with two internal hard drives to run the Migration Assistant, turn it on in Target Disk Mode and rename the empty second hard drive to something other than Macintosh HD. Now, the explanation:

I was setting up a new Mac Pro for a user at one of my clients, and attempted to migrate her from her existing Power Mac G5. The new machine was configured with two internal hard drives, 500GB each. I attempted to migrate her data from the initial Setup Assistant, and everything went smoothly until we got to the actual "Transferring Information" screen -- no time estimate ever appeared in the progress bar, and the drives were not making sounds that would indicate they were being accessed.

I ended up rebooting the new machine via the power button and choosing not to migrate data when the Setup Assistant ran the next time. I made a dummy account and then ran Migration Assistant manually. I noticed that both internal drives on the Mac Pro were named Macintosh HD, and guessed that may have confused Migration Assistant. After I renamed the second drive, the copy proceeded without any problems.

To verify that the identically-named internal drives were indeed the problem, I stopped the migration, set the machine back to out-of-box state (except for the internal drives having identical names), and tried migrating the data from the initial Setup Assistant, and it worked flawlessly. I submitted a bug report to Apple about this, but thought I'd spread the word to possibly save someone else some time figuring this out before it gets fixed by a future version of Migration Assistant.
    •    
  • Currently 2.57 / 5
  You rated: 4 / 5 (7 votes cast)
 
[20,745 views]  

A multiple-drive Mac Pro Migration Assistant issue | 13 comments | Create New Account
Click here to return to the 'A multiple-drive Mac Pro Migration Assistant issue' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A multiple-drive Mac Pro Migration Assistant issue
Authored by: GrahamAJones on Aug 08, '07 08:12:06AM

Hi,

I'm sure this is a valid suggestion. However, I would not advise using Migration Assistant to migrate a non-Intel Mac to an Intel Mac. You'd think that Apple would anticipate the conversion issues, but after having problems with such a migration and talking to Apple Support, they told me that the Migration Assistant was not really suitable for non-Intel to Intel migrations, and using it could introduce problems. This is definitely a major issue for pro apps, but I have a string suspicion it would be an issue for other apps too.

Hope this helps,
Graham Jones.



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: dzurn on Aug 08, '07 09:41:19AM
Did Apple Support tell you where the problem could be? How do we fix any problems if it's already happened?

Thanks

And there's me with half a wall wattled. I mean, what'll I do?

Darryl

---
Madness takes its toll.
Please have exact change.

[ Reply to This | # ]

A multiple-drive Mac Pro Migration Assistant issue
Authored by: GrahamAJones on Aug 09, '07 07:39:59AM

Hi,

It may be entirely a Pro Apps issue, but they said that pro apps install processor-specific support files and even preferences. This is not just Apple either-- Avid also does not support the migration assistant because they have different apps for different processors.

It may be that consumer and business-type apps are not affected by this, but any audio/video pro would be wise to stay away from the Migration Assistant.

Keep in mind that the only reason I was calling Apple support was that I indeed had migration problems.

Hope this helps,
Graham Jones.



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: timkingman on Aug 08, '07 09:57:57AM

I had no problems migrating from a PowerBook G4 to a MacBook Pro. That was my first time actually trying the Migration Assistant, and I was amazed at how well it worked.



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: imageworx on Aug 08, '07 12:05:57PM

I've migrated a dozen PPC to Intels over the last few months without a hitch. Well, one required I extract the HD and use DiskJockey for Firewire (the iMac did not have FW ports).
I think it would be simpler to yank out the 2nd drive, do the migration, then re-install the 2nd drive/sled. Takes all of a minute...(power off first!)

---
To BeOS or Not to BeOS



[ Reply to This | # ]
Another migration issue:
Authored by: Chas on Aug 08, '07 10:35:51AM

I discovered another obscure problem with the Migration Assistant, you cannot migrate from a RAID. I tried to migrate from my old MDD G4 with a two-drive RAID 0 to my Quad G5, the RAID was not recognized in Target Disk Mode. Apparently the RAID only mounts and attaches in the Finder during a normal boot sequence, it cannot be seen in Target Disk Mode.



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: giaguara on Aug 08, '07 03:53:16PM

Another issue with migrating with the migration assistant is that it does not copy over all kext and other files the programs have added in System and Library.

E.g. if you copy Fusion and virtual machines from a previous Intel Mac, it will appear to run normally, but you get odd errors (services appear not running for kext supporting files not having been copied over). Again, uninstalling and reinstalling the application works.
Then again, this happens with many other applications that use an installer.

---
Giaguara



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: neuralstatic on Aug 08, '07 05:06:53PM

this is by design, and really a good idea, imho
dont' want to import old versions of system extensions into new systems.



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: morespace54 on Aug 09, '07 08:06:08AM

agree.

since I had a few issues migrating ppc/intel (imac), I would recommend to only copy "user" files. This way, you shouldn't get *any* problem. I know it's often a pain in the neck to re-install the apps but then (and only then) you can be sure that only *correct* kext will be installed (plus, it gives you the chance to do a little cleanup with all those freewares... ;))



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: percyhanna on Aug 08, '07 04:58:01PM

I migrated from my 17" PowerBook to the first-gen iMac 2 days after it was announced, without a hitch. So migrating from PPC to Intel has been working for over a year and a half.



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: baltwo on Aug 08, '07 05:35:58PM
Hopefully, this will help: Migrating to ICBM (Intel-chip-based Mac)

[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: Tui on Aug 29, '07 01:05:19PM

phillymjs, thank you so much for your report. I have the exact same problem with my brand-new 8-core Mac Pro with 2 internal drives. It is impossible to transfer accounts from a MacBook Pro, or a G4 Titanium PowerBook. The guys at the Apple Centre (Chiang Mai, Thailand) were scratching their heads, but couldn't figure it out. Interestingly, when the technician removed both hard-drives and replaced them with one Seagate drive, migration appeared to work flawlessly. However, he didn't think of doing what you did, but assumed a hardware problem. I will pass on the information.



[ Reply to This | # ]
A multiple-drive Mac Pro Migration Assistant issue
Authored by: Tui on Sep 09, '07 04:01:11PM

I thought I'd add a quick update. I tried out changing the names of the drives, but Migration Assistant still wouldn't let me copy over my account. Even when I removed the second drive and only left the System drive in the machine, migration did not work. I found the only way of transferring my account was to make a clone of the original drive on a firewire drive, and then use Disk Utility for restoring from the firewire drive to the Mac Pro internal HD.



[ Reply to This | # ]