Migration Assistant Target disk blues

Hello,
Just bought a new MacBook running 10.4.6, and launched Migration Assistant to bring over some applications from my Dual-500 G4 Powermac running 10.3.9. As requested by Migration Assistant, I connected the computers using firewire, then started up the G4 as a target disk. The bouncing firewire symbol appeared onscreen on the G4, and an orange firewire disk icon appears on the MacBook (with the G4's name).
Still, the Migration Assistant fails to recognize the disk. And when I click on the MacBook's desktop, attempting to open the drive, the computer freezes.
I contacted Apple, who told me the problem might be that my G4 startup disk is a slave. I reconfigured it, so that it's the master. No luck. I also pulled System 9 from the G4's startup disk (in case the MacBook is somehow getting caught up on the first system it finds, and can't make it to OSX). Still no luck. Anyone have any ideas?
Thanks...

Try this link
http://www.whoi.edu/CIS/services/desktop/macintosh/howto/filetransfer.html
You can also try it the other way start up the new mac in target mode and drag your file from the old mac. open the firewire icon and mac a new folder and drag and drop the file you want into the folder so its doing it the other way putting files onto it not taking them off the macbook

Similar Messages

Migration Assistant, Target Disk Mode and Bluetooth Keyboards

Wanted to migrate my iMac setup to a new MBP last night. Kept trying to start up my iMac in target disk mode and it would only boot normally not in TD. Finally realized that my bluetooth keyboard was the culprit in that it wasn't connected once the iMac shut off for the restart. Thankfully I had a wired keyboard; plugged it in and migration went as advertised. Nowhere (that I could find) in the Migration Asst. prompts does it mention anything about needing a wired keyboard to restart as a TD. Did I miss something basic? If not, shouldn't Apple make mention of this to avoid confusion and frustration?
BTW, the new MBP rocks!

Yes, that tidbit of info is buried in a support article, as is some other Migration Assistant documentation. But it would be far better if the app had its own comprehensive, searchable Help built into it, just like most other apps from Apple. Note that when you launch Migration Assistant, there isn't even a Help menu, nor are there any question mark in purple circle icons in its windows to offer context sensitive help.
Basically, that's what I requested in my feedback to Apple.

Migrating in Target Disk Mode

I'm trying to migrate from an old iBook G4 running OS 10.4.11 to my new MacBook Pro running Lion. I understand you cannot do this using Migration Assistant, and I've already missed my opportunity to use Startup Assistant. But I'm told that if I connect the computers in Target Disk Mode (both my computers have FireWire ports), that all my data will migrate automatically (files, applications, bookmarks, Internet settings, e-mail address book, etc.), just as if Migration Assistant had done it. I was under the impression that, in Target Disk Mode, you could only transfer files manually, so this comes as good news. I'd just like someone to verify this, if possible. I'm not a newb, but I do this stuff so infrequently that I'd like some confirmation. Thanks very much.
-Bob

John Holt4 wrote:
Could I just clone my older MacBook directly to the new IMac using something like Carbon Copier Cloner
Probably not; an iMac likely won't work well (if at all) with the version of OSX that was on a MacBook.
I will be using a 800 9pin firewire cable in either case.
Great! That's the fastest.
One thing I have discovered is that I will probably have to name my new computer with a new shortname as I go a message showing both my source and target could not have the same short name?
It's a good idea, but not required, to have different Computer names (per System Prefs > Sharing).
But no, you can't have two user accounts with the same short user name.
Since you've missed the chance to use Setup Assistant, use one of the workarounds in the green box of Problems after using Migration Assistant.

Migration Assistant & Target Disc: Deleted User

It appears that the Target disc I migrated to a G4 from an eMac the user was deleted and now no user has permissions to access the library. The apps won't open and it boots into basic mode. Real strange.
Can anyone help.
Thanks.
Nathan.

jeevescat wrote:
Thanks for your reply.
The migration assistant behaved as usual, I've used it countless times, it came up with the list of accounts, in this instant there was only the one, and all the boxes were ticked to transfer all apps, files etc and all data from this account.
At the end of the transfer the computer restarted, but instead of going straight to the desktop, it ran through the account creation procedure.
All data and apps outside of the user folder have been copied but nothing in the user folder. Thats when I noticed that connecting to the old imac in TDM does not allow access to the data in the user folder,
please clarify that. do you mean that you don't have permissions to open that folder? or do you mean something else?
their is only one account which it is set to automatically log into. There are no passwords or security, file vault is not on and all sharing is enabled, access is fine over a normal network connection.
Any suggestions?

Migration Assistant adn iMac wont recognize Target Disk Mode of iBook

Friend purchased a new iMac 20in and went to use Migration Assistnat to transfer from older iBook. Will call this iBook1
Following directions, he hooked up Firewire cable, rebooted iBook1 into Targe Disk Mode (TDM). New iMac would NOT recognize existance of TDM iBook1. So we began the following sequence of tests to isolate the problem.
1) Using a second iBook2, hooked up original iBook1 in TDM to iBook2. The HD of iBook1 showed up on the desktop of iBook2 as it should, along with all the files inside of it. This verified that the cable was good and that the firewire port on the iBook1 was working as well as TDM on iBook1.
2) We rebooted the iMac, restarted the Migration assitant and placed the iBook2 into TDM and connected them. Migration assistant worked, recognizing the iBook2 as it should. This verified that the iMAc firewire port and Migration assistant was again working fine. We also rebooted the iMac and hooked up the iBook2 in TDM w/o Migration assistant, and again it worked fine.
3) We then tried to connect the iBook1 via TDM to the iMac w/o migration assistant. Again NO RESULT.
No matter what we did, we could NOT get the new iMac to recognize the older iBook1 via firewire TDM. All other connections betwen the computers worked fine. All systems were running 10.4.10. We reset the PRAM, we fixed permisions, still the new iMac would not recognize the iBook1 in TDM.
Any ideas?

I'm having the same problem connecting my iBook G3 500 in Target Disk Mode to my new iMac, the icon does not show up on the iMac. I have tested the Firewire on both computers with a FW XHD and they work fine. I took the iBook in to work and connected it to an eMac and a ProBook Intel with no problems. Back home tonight and it still fails to show the icon of the iBook in TDM on the desktop of the new iMac. Suggestions on a fix ? Thank you.

Migration assistant can't find target disk

I've just bought a Macbook Pro (Leopard), and am trying to use the migration assitant to move everything from my old Macbook (OS 10.4.11), the way I once did when I upgraded from my old iBook (OSX) to my Macbook. Everything seems fine - I plug in the Firewire 400 to Firewire 400 I used the last time, and start up the Macbook in target mode, getting the Firewire symbol and all. However, the migration assitant on my MBP won't find my MB target disk. At first it says "Waiting for disks to appear", then nothing happens, until I get an error message saying the target computer has no OSX...
I've repaired permissions as well as the disk on the MB with the OSX installation disk, but to no avail. To be fair, the MB startup disk could not be completely repaired, which I'm thinking might be the problem. (However, the MB does work fine otherwise.) I've searhed this forum and googled for it, but haven't found much help anywhere. Any chance anybody here knows why it won't work?

AFAIK, the setup assistant only needs to see a good OS on the computer you're transferring from. The setup assistant uses the migration assistant to do the transfer if you select a user account from the drop-down menu. I used E&I and transferred/migrated from 10.4.11. If transferring from a PPC to an ICBM (Intel-chip-based Mac) peruse http://discussions.apple.com/thread.jspa?messageID=1872713 before doing it.

Target Disk Mode and Migration Assistant

Since FireWire has been removed, what are the best alternatives to Target Disk Mode and Migration Assistant?

1. Put old MacBook's hard drive in external USB enclosure.
2. Connect to new Mac, and run Migration Assistant.
3. Migrate just as you would normally.
Speed over USB 2.0 is almost as fast as firewire. An external enclosure will set you back about 15 to 20 bucks.
Seriously, it's not a big deal. I've been doing it this way for years. The only place you have a problem is when the old Mac's drive isn't accessible. In that case, you remove the new MacBook drive, put it in the enclosure, and use SuperDuper to back up your old Mac. You then pop the new MacBook's drive back in the MacBook and re-install OS X, telling it to transfer the old user files into the new installation.

Migration Assistant vs. Target Disk Mode

I'm trying to migrate an account via Target Disk Mode from a PPC G4 tower with multiple drives. Only one of the drives is showing up (number 2 out of 4) and it's not the system drive. Any idea how I can get the other drives to appear? They do not show up in Disk Utility, either.
Thanks!

Any idea how I can get the other drives to appear?
Change the position of the drives in the computer or use another method. Target Disk mode only connects to the master drive on the ATA 0 bus, and on newer Macs, the internal optical drive.
(51389)

Migration Assistant vs Target Disk

Originally I came here because I am unable to get the two Migration Assistants to talk to each other over ethernet - or Airport. They just kept on "searching for other computers" endlessly until timing out....but - *Forget that for now* - I am waiting on getting a Firewire 800-400 adapter since my new Mini has a 800 port - and my iMac PPC G5 is a 400!
What I did find in reading threads is how problematic MA "might" be - and alternatives to it. So what I'm looking for are recommendations based on the following -
I have a huge number of applications on the G5 - a rough guess is 200+ and that 75% of them are Universal. I don't care about moving anything over other than applications. (Files can simply be brought over as needed by shared disk!) I don't care about user accounts (only me), settings, preferences or anything else at all - JUST APPS!
My biggest concern are licenses/installs. I'm not very organized on this point (thinking I would have no issues using MA) so some came by emails, phone, some are in a box, download documentation or manual and many I can't even remember how it came or what I did with them after I bought the apps. If I got a DMG/Install/MPKG/Zip/PKG. file for instance - chances are I installed and deleted it, rather than burning a disk for a hard backup and writing the S/N on the disk... (learned my lesson there).
Now I'm reading that some of my apps won't work via any type of transfer without chasing down the manufacturer for each one with endless nightmares of being put on hold forever! It could literally take months! This is more than a little disturbing as I was hoping I could just run MA, let it sit overnight and do it's thing and have all my tools ready to go.
I thought moving to an Intel box would make my life easier, but it's not right now! LOL
So now I'm just wondering what's the best approach in my situation?

It went fine using MA - everything appears to have moved over.
1. The "info" on apps no longer says if it's a PPC or Uni or anything - just "app"...kind of strange.
On my system older apps still have a "Kind" of things like "Application (PowerPC)" or "Application (Universal)".
Do I now need to do anything? Repair Permissions? I recently saw one thread when RP was causing someone major problems on a Mini!
Repairing permissions isn't the magic bullet that some fee it is. In particular, it won't do anything for non-Apple software.
So far the couple of apps that I have tried are DOA on the Intel box after a MA xfer...meaning the keys didn't come over.
Better than having to reinstall everything!

MIgration Assistant Stalls using FW disk as source? New i7

Hi folks,
Just got my new i7 today and have a Firewire 800 connection to an external drive. When using the migration I chose to migrate from another disk rather than using my desktop as a target. It seem to go along fine until I got to 30 minutes remaining and then it seems to have stalled, The blue progress bar is still revolving, but it is not getting any further. I marked the location with mouse and it has been stuck for over 30 minutes.
I'm not sure what the problem is. The external does not seem to be asleep and the i7 beeps if I press any key on the keyboard as if it is busy. It says it is "transferring files and folders" from the target disk. The i7 is on external power and there is plenty of room on the local HD.
If this fails, what do i do? I suppose I have a corrupted migration?
Jeff

I tried using my desktop as a target disk, and it also failed with 42 minutes left. I wonder if I have a bad hard drive on my new laptop????

Can migration assistant move data from multiple disks (Mac Pro) to a single disk (iMac)

I have recently purchased an iMac and need to migrate my apps, data and accounts from a Mac Pro running OSX 10.5.8. Does Migration Assistant accommodate a multi disk set up (I have my OS and apps on one disk and data on another) or does it only recognise one 'target' disk at a time.

yes. I migrated a server frm lion to mavericks following these notes a while back:
OS X Server: Upgrade and migration from Mountain Lion
i do not recall having any problems with it.

Use Mountain Lion Migration Assistant to access Mavericks disks?

Hi,
Maybe this is a stupid question... I have a MacBook Air from work with Mountain Lion on it, and I wanted to use Migration Assistant to import files and settings from my personal Mac (also a MacBook Air). However, my personal computer (the source one) is running Mavericks.
I've connected the two computers with a Thunderbolt cable and booted my personal computer (the source) into target disk mode. The work computer (destination) recognizes the disks on my personal computer but when I run Migration Assistant, it won't bring up my source computer's hard drive.
Is this normal? I can't find any reference to whether it's possible to use Migration Assistant to migrate from a newer OS to an older one.

I don't think your Mac will let you transfer files from a different Mac with OS X Mavericks, because you can damage Mac OS X if you transfer apps and settings.
Instead, transfer your files with an external drive or connect both of them with a Thunderbolt cable (remember that it only works with Mid 2011 and newer MacBooks Air), and put the Mac with Mavericks in Target Disk mode (hold the T key while your MacBook Air is starting up), so you can access to your Mavericks Mac's hard drive from the other MacBook

Migration assistant doesn't "see" Time Machine disk

Just got a new logic board, and they wiped the hard drive. My Time Machine disk mounts, and I can see the files. However, migration assistant doesn't list it as a source. (Yes it's formatted Mac OS Extended [Journaled])
Time Machine recognizes it and wants to use it as a new backup disk, but it doesn't want to show me anything from the old back up. I didn't do a new backup of the "new" computer. I don't back up applications just users.
2.2 i7 MbP 8GB 10.7.4
thanks
DLS

Just back home from a follow-up visit to the Genius Bar on this migration issue (from MacBook Air to new MacBook Pro).
Previous efforts to migrate had taken endless hours and seemed to hang at the 20-mins-remaining mark.
At the store, even after we manually turned off WiFi before connecting the Thunderbolt cable, Migration Assistant seemed to turn WiFi back on and start the migration over WiFi.
In the end, we used the Air (source) in Target Disk mode, which forced the computers to use the Thunderbolt cable. Migration took a little over half an hour, as opposed to 12 hours or more that Migration Assistant was saying earlier when apparently trying to use WiFi.

Migration Assistant from Tiger Mac to new Leopard MBP can't see disk

Hi,
I just bought a new MacBook Pro and am trying to migrate from my Tiger-based (10.4.10) dual 1 GHz Mac (mirrored-drive door) desktop machine. The boot drive on the Tiger machine is actually partitioned into an emergency boot drive of a few GB and my main working drive ("Macintosh HD"). When I run Migration Assistant (MA) on my MBP (after connecting the 6-pin Firewire cable and restarting the Tiger Mac in target disk mode), the MBP sees only the emergency boot-up partition and not the main working partition from which I want to migrate.
I tried MA on my MBP connected to a different Mac with no HD partitions, and it sees "Macintosh HD" just fine, so I think all the new hardware is okay as well as the Firewire cable.
Any ideas?
-Eric

Thanks for the info. I do know something about this (being a HW engineer), but I would have thought that the IDE master/slave jumpers would affect all the partitions on the disk. Since my emergency-boot partition is visible, I take that to mean that the IDE master/slave jumper issue is a non-issue for me.
I don't know if this helps, but here's what Disk Utility reports about the disk (not the volumes residing on it):
Name : ST380021A
Type : Disk
Disk Identifier : disk1
Media Name : ST380021A Media
Media Type : Generic
Connection Bus : ATA
Connection Type : Internal
Connection ID : Device 0
Partition Type : Applepartitionscheme
Device Tree : pci2/ata-6@D/@0:0
Writable : Yes
Ejectable : No
Mac OS 9 Drivers Installed : Yes
Location : Internal
Total Capacity : 74.5 GB (80,026,361,856 Bytes)
S.M.A.R.T. Status : Verified
Disk Number : 1
Partition Number : 0
Now, onto the partitions which I know less about.
Here's what Disk Utility says about the Macintosh HD partition:
Name : Macintosh HD
Type : Volume
Disk Identifier : disk1s10
Mount Point : /
File System : Mac OS Extended (Journaled)
Connection Bus : ATA
Partition Type : Apple_HFS
Device Tree : pci2/ata-6@D/@0:10
Writable : Yes
Universal Unique Identifier : E6E9B335-60D0-3F06-97F9-2A9BAC522106
Capacity : 68.4 GB (73,411,137,536 Bytes)
Free Space : 819.5 MB (859,291,648 Bytes)
Used : 67.6 GB (72,546,123,776 Bytes)
Number of Files : 367,638
Number of Folders : 74,198
Owners Enabled : Yes
Can Turn Owners Off : Yes
Can Repair Permissions : Yes
Can Be Verified : Yes
Can Be Repaired : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : Yes
S.M.A.R.T. Status : Verified
Disk Number : 1
Partition Number : 10
Here's what Disk Utility says about my emergency-boot partition:
Name : Clean Boot
Type : Volume
Disk Identifier : disk1s12
Mount Point : /Volumes/Clean Boot
File System : Mac OS Extended (Journaled)
Connection Bus : ATA
Partition Type : Apple_HFS
Device Tree : pci2/ata-6@D/@0:12
Writable : Yes
Universal Unique Identifier : 4A704075-200F-3CCB-B8ED-E7FEEDB655EC
Capacity : 5.9 GB (6,345,846,784 Bytes)
Free Space : 3.8 GB (4,133,232,640 Bytes)
Used : 2.1 GB (2,212,093,952 Bytes)
Number of Files : 76,846
Number of Folders : 19,664
Owners Enabled : Yes
Can Turn Owners Off : Yes
Can Repair Permissions : Yes
Can Be Verified : Yes
Can Be Repaired : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : Yes
S.M.A.R.T. Status : Verified
Disk Number : 1
Partition Number : 12
I don't know how to determine from the above what the "first" partition would be. I don't know how to post an attachment here otherwise I'd show a screen shot, but when I got into Disk Utility's partition tab, the emergency-boot partition (called Clean Boot) shows up at the bottom of the space indicating all of the HD's space, and Macintosh HD shows above Clean Boot.
So what are my options? Can I repartition w/o loosing Macintosh HD (I'm willing to loose the other partition Clean Boot)? Any way to change the partition numbers?
I was thinking of cloning Macintosh HD to another HD and then migrating from that. Any experience with that?
Thanks, Eric

Migrating Information in Target Disk Mode Wiped out hard drive

I just helped a friend install Leopard on her new MacBook (it came with a drop in disk of Leopard). After the install, I started her previous 3-year old MacBook in target disk mode to migrate over old system settings. During the migration, the new MacBook froze up and forced me to do a hard restart. After restarting the computer, it would no longer recognize the old MacBook that was still in Target Disk Mode.
After awhile I finally decided to pull the hard drive out of the old MacBook and hook it up to my WiebeTech DriveDock. I now get a disk insertion error telling me that the drive is not readable. I have tried DriveGenius, but I cannot rebuild or repair the drive because it doesn't even pop up.
Has anyone heard of the migration assistance wiping out the drive you were attempting to migrate from? And also, does anyone know of a way to fix this?

She backed up with Retrospect a couple weeks ago, so not much would be lost if I wasn't able to resurrect this drive. The feeling of accomplishment from tackling this problem is the only truly important thing that would be lost.

Migration Assistant Target disk blues

Similar Messages

Maybe you are looking for