Migration Assistant Fails x 4

Brand new Mac Mini, old worn Mac Book Pro. Most recent instructions I found for Migration Assistant were for OSx10.6. Screens are all different but I plowed ahead. Source and Target Macs see each other, connected by firewire, target mac shows list of items to select for transfer, Apps, Data, and something else are selected, but it only indicates like 156k of data to be transferred (not likely). Match ID numbers and click continue. New mac reboots and suspends transfer from Source mac which is left hanging.
I thought this was supposed to be easy?
Craig Mc

Apologies, In one attempt (using firewire) the old mac was in target mode. While the Migration Assistant did provide me with a slightly different screen of options, the results were the same, both computers went to grey screen, and returned to a login screen. I have tried firewire as well as ethernet methods and although presented with slightly different screens, results are identical, both or one machine immediately shows grey screen and then brings up login panel. The only thing that has transferred to date is Safari favorites. I have also tried selecting only 'Documents and Data' versus the whole package, again with same results. I am currently performing a backup on the old Mac Book Pro, and unable to initiate any transfer attempts for another...20 minutes, but will be available to try suggestions in a few minutes. I was considering calling Apple support instead of this forum, but will make reasonable attempts with your help instead.

Similar Messages

HT4796 Migration assistant failed after 90% of the way; where are the files now and how do I get rid of them?

Migration assistant failed after 90% of the way; where are the files now and how do I get rid of them?

Hello. It looks like I recovered all my keywords attached to photos. What I did:
First I located all photos without keywords using a metadata search.
I found that it seemed to be certain groups of photos that had no keywords. I decided to at least get the main keyword on all of those in a particular group, like Canyonlands.
Once I added one of the keywords, the others all showed up magically! I then went to each group of photos and added the main keyword, and the others came along and attached to the photos.
Don't understand why this occurred or why it got fixed, since it was so random. But, I'm glad to have my keywords restored (I had divided flowers by color, etc. so it was a lot of work!)
Thanks for the discussion and help.

Migration Assistant fails with MacPro6,1

I bought a Mac Pro a few months ago and kept getting kernal panic's after running migration assistant from a MacPro1,1 which I have had for about 8 years. I went back and forth with Apple, and they decided it was defective and sent me a new one which took a while to get through the university bureaucracy. I ran Migration Assistant from a MacPro1,1 running OS 10.7.5, and again got a kernal panic on restarting but was able to do a safe-boot successfully ((previous MacPro even this failed). I updated the OS X software and tried to turn off stuff that might be interfering but still get kernal panic's on restarting sometimes. Also received alerts that a variety of system extensions "were not installed properly". Clearly, the system IS NOT that stable so I erased the hard disk and will do a manual restore app by app so no preferences or systems-related software gets transferred.
This problem is very surprising to me since I have never had problems with Migration Assistant before and we have plenty of macs here. I must have tried a dozen times with the first Mac Pro using either the old mac in firewire mode or using the time-machine backup but nothing worked. I wonder if anyone else has seen this and if the new Mac Pro has an issue in this regard.
On the positive side, Migration Assistant probably moved a bunch of obsolete software/files from the 8-yr old Mac which was migrated from an older Mac (and the older Mac was migrated from a an even earlier Mac). A clean install at this point may be worth doing but a hassle.

Your conclusion that Migration assistant fails is not supported by the evidence you presented. You said you got kernel panics AFTER you restarted -- these are not caused by inherent Vice in Migration Assistant, which appears to have completed successfully.
Kernel panic is not ONE problem, it is one of hundreds to thousands of problems, and if you would like help debugging that, you could post a kernel panic log for readers to help you interpret.
Mac OS X: How to log a kernel panic
If you approach Apple for help with this issue, they will check for machine-check reports, run diagnostics, then send you home to erase your drive and re-Install Mac OS X from scratch (which effectively removes third party add-ons in the process).

Migration Assistant Fails during X.4 to X.5 Upgrade

I'm trying to upgrade from X.4 to X.5.
I did an Archive and Install, and Migration Assistant fails.
It firstly fails with some Address Book backup files.
These are located in: david/Library/Application Support/AddressBook/Address Book Backup
With filenames such as: Address Book - 01/02/2008
The error is "File name too long (63)"
I removed the whole folder and tried again, and it failed with 'Invalid Argument'
I ended up restoring X.4 from a disk image.
I then tried installing X.5 on a bootable external FireWire drive with GUID partition map, migrating from the internal hard drive.
This also fails at the same point.
Any suggestions?
Many TIA
David

It would appear that the Address Book backup file was corrupt. The size indicated was around 180MB, rather than around 10MB! The visible file name looked OK.
Ironically, X.5 was able to copy the file to a new location. It complained about file name length, but copied it and reduced the file size to 9MB. Rather a shame that Migration Assistant doesn't use the same copy facilities.
What has this taught me?
1. BACKUP! Create a disc image of the full hard disc. OK, it's said elsewhere, but it really can't be said too often!
2. Set up an Administrator/admin account. One that's essentially not used, but can access all Applications, networks and settings. If I had done this, I could have migrated this account as part of the installation process, and worried about migrating the main User account separately, using Migration Assistant.
However, I now have a new problem!
For some reason, I can't access the wireless network I've been using. I can see the neighbour's network(!), but not my own. I'm using WEP security.
Any ideas?
Many thanks,
David

HT4796 Does anybody know why migration assistant fails in windows vista?

Does anybody know why migration assistant fails in windows vista?

rank2, welcome to the forum,
PS: Is Europe/Germany as location ok? The rules don't mention how location should look like
That's great, thanks.
"Country Location - Members should denote their country location in their personal profile. Location is important when offering advice, as sales, service, and product options may not be consistent country to country."
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Migration Assistant fails after showing 157 KB or 0 KB to transfer

I spent 4 days trying to get OS X Migration Assistant to successfully migrate between two desktop machines, both running Mavericks 10.9.3.
The two machines were connected by an ethernet cable, and all migrations would fail after 16-24 hours, with the progress bar stalling out at "Less than one minute remaining".
Before every failed transfer, Migration Assistant would inaccurately show "157 KB selected" for transfer if the "Computer & Network Settings" option was checked, or "0 KB selected" for transfer if only the "Applications" or "Documents & Data" options were checked.
I finally realized that the migrations were failing because I was opening and clicking through Migration Assistant on both the source and target machines at around the same time.
The eventual solution was to open Migration Assistant on the source machine first, and click through as far as I could until the source machine was actively looking for other machines on the network.
As long as I waited until then to open Migration Assistant on the target machine, it would correctly calculate the size of the files to be transferred and the migration would succeed.
So, the order in which you open Migration Assistant seems to make a big difference: source first, then target.
My problem is solved, but only after several days of hassle, so I wanted to post this in case other people had a similar issue.
(I tried many suggested fixes that did not work, included reinstalling OS X on the target machine, running disk repair and fixing permissions on both source and target, changing file sharing on the source machine to include the whole drive, trying to migrate Applications and Documents & Data separately, turning off wifi before the transfer, etc.)

Thanks for posting this. I was having the same problem. You saved me hours, maybe days, of frustration!

Migration Assistant fails on non-existent file

Here's an interesting one. I made a bootable clone of my harddrive (with SuperDuper) that works like a champ. Bought a new (much larger) hard drive for my Macbook, installed OS X with no problem, got it all updated. Then went to use Migration Assistant to import my user from the clone, and it fails on trying to copy an invisible file (begins with .) that actually doesn't exist (I have Finder set to show hidden files). This causes the whole import to fail and MA says the user can't be created. Is there any way to tell it to skip this "file"? Other suggestions welcome.

Yeah, that didn't work so well since SuperDuper ran across repeated errors trying to do so; I suspect it's something to do with the drive. (SuperDuper complains about WD's MyBook, which is what the drive is.) Because SD stops the entire copy operation on single errors, it'd be a painstaking process.
Besides that, I like doing fresh installs of all the bits.

Migration assistant fails to *find* machine

Very simple, thought I'd fire it up before going to sleep and have a baseline to tune from in the morning. No such luck -- just a band-new 10.5.7 MBP seeking to slurp from a couple year old 10.5.7 Core2Duo iMac. I haven't any FW800 small-port cables, but neither on a dedicated point-to-point ethernet nor on the regular network does migration ***'t get past "looking for other machines" stage after specifying who is sending and who is receiving. I presume this is either a sign I shouldn't bother with it or some completely braindead thing done on my part.

Thanks, Pondini, but the Time Machine disk passes the Disk Utility repairs and only the spinning wheel was visible under both the Setup Assistant and the Migration Assistant.
I now have some good news, and some bad.
First the good news: Lion's Migration Assistant offers the option to copy user (and other) files from the previous OSX disk, not just the Time Machine disk. If this option was already in Snow Leopard, then I missed it.
Now the bad news..
I spent several hours reading (Pondini's and others') suggestions to ensure that my Time Machine is as seamless as possible, namely, for the next backup to be incremental. No luck: all user data are copied. Until the interface of Time Machine stops trying so hard to shield us naive users from making decisions on our own, one idea is to keep the iPod and pictures/video collection backed-up by the straight-forward rsync. Then whether Time Machine is really incremental will not matter, and in any case a spare copy of the documents you wrote by hand is nice in case the some blocks of the disk fail.
But I may have been the one who messed it. In Preferrences \ Time Machine \ Options... I excluded all users except the user "Admin" who restored the user accounts. The idea was to test first whether the mildest user will get a full backup. It may be that Time Machine does not look in the history to see if a given file or set of files already have some copy in the past. If a file does not exist in the very last backup, it is saved to the Time Machine disk.
If you're reading this and are keen on an incremental backup, try this: restore your user accounts using a user Admin, but do not start to backup until after the accounts are restored. Will the backup afterwards be incremental?

Migration assistant fails repeatedly

I just bought a new MB and have been trying to transfer info from my old one. I have run Migration Assistant multiple times, but it fails at a certain point. After moving a lot of my info, it eventually hangs and says that "The other Mac is not responding. Make sure that all of your network devices are connected and turned on." It has a button to continue, but that never works. I have no idea why it would quit as I have not touched anything. Any advice would be appreciated. TIA

Perhaps Pondinis' Excellent Information may be of value to you...
Have a look at this Link...
Using Migration Assistant on Lion
From here
http://pondini.org/OSX/Home.html

Migration Assistant fails or freezes every time

2008 iMac running Mavericks to a new iMac over ethernet connection.
I have run software update on both iMacs, I have run "repair disk" and "fix permissions" on both.
Every time i run migration assistant, it never completes. it looks like its running, and the esitmated time left begins to count down, but eventually it just stays at 2hrs remaining, or 2hrs 30 minutes remaining. And I let it run for 15 hours.
I am forced to reboot the computers to get them back, and the new iMac has NO data transferred, and the old Mac remains as is (as expected).
Also, Time Machine fails on the 2008. I have tried to run time machine to more than one firewire drive.
Not sure how to proceed.

Sounds like you've been through the ringer . After Apple replaced FW with Thunderbolt my boss tasked one of the techs and me to investigate alternatives. We both found WiFi useless for anything more than a couple GB of data and even then we experienced too many failures to recommend it. Theoretically migrating with Ethernet should be a good choice but once again we experienced failures we couldn't explain. That led us to recommend users back up via clone or TimeMachine to an external drive and migrate using the external drive.
That should have ended the matter but I've since added a qualifier to that recommendation; a USB external drive may be your best option. We've always known that some FW chipsets were flaky but an additional layer of flakiness has been added with the Thunderbolt/FireWire adaptor.

Migration Assistant fails to recognize a Time Machine disk (itself migrated using Disk Utility)

So I outgrow my Time Machine disk. I listen to the advice (repeated in multiple places) that one can simply use Disk Utility's Restore tab, select the old time machine disk as source and the new one as destination, and click restore to copy block-by-block, then rename the disk.
This works very well. I have indeed been able to use Time Machine on the new disk without losing any of the history.
But now I am in trouble. I am also outgrowing my MacBook disk. I put a larger disk in and install Snow Leopard from scratch. Now Migration Assistant does not recognize the new Time Machine disk (perpetually spinning wheel). Renaming the disk to the old name does not help. M.A. does recognize the old Time Machine disk, but that means manually managing the changes (and giving up on the larger TM disk). I reinstall Snow Leopard and do not miss that time the option to restore from Time Machine, but it still does not see the new Time Machine disk.
How does one convince Migration Assistant to use a Time Machine disk that duly has Backups.backupdb as a root folder and where "ignore ownership on this volume" is not set?

Thanks, Pondini, but the Time Machine disk passes the Disk Utility repairs and only the spinning wheel was visible under both the Setup Assistant and the Migration Assistant.
I now have some good news, and some bad.
First the good news: Lion's Migration Assistant offers the option to copy user (and other) files from the previous OSX disk, not just the Time Machine disk. If this option was already in Snow Leopard, then I missed it.
Now the bad news..
I spent several hours reading (Pondini's and others') suggestions to ensure that my Time Machine is as seamless as possible, namely, for the next backup to be incremental. No luck: all user data are copied. Until the interface of Time Machine stops trying so hard to shield us naive users from making decisions on our own, one idea is to keep the iPod and pictures/video collection backed-up by the straight-forward rsync. Then whether Time Machine is really incremental will not matter, and in any case a spare copy of the documents you wrote by hand is nice in case the some blocks of the disk fail.
But I may have been the one who messed it. In Preferrences \ Time Machine \ Options... I excluded all users except the user "Admin" who restored the user accounts. The idea was to test first whether the mildest user will get a full backup. It may be that Time Machine does not look in the history to see if a given file or set of files already have some copy in the past. If a file does not exist in the very last backup, it is saved to the Time Machine disk.
If you're reading this and are keen on an incremental backup, try this: restore your user accounts using a user Admin, but do not start to backup until after the accounts are restored. Will the backup afterwards be incremental?

Migration assistant fails and eats storage

Mac Book Pro 10.10
While utilizing Migration Assistant between two OS 10.10 machines (old and new) via thunderbolt connection the migration stalled with 1 min to go. I turned off both computers an rebooted them seprately. The new computer displayed the account I had created while in migration assistant and logged in with the appropriate credentials however no files were displaying. I logged out and signed into another admin account I had created before the migration and deleted the account specifically check the box to erase the home folder of that user. At this point I had already noticed that it had eaten 300+ GB of my storage and hoped that deleting the account would give me back the storage. However after restarting several times, running disk utility and emptying the trash, there still seems to be a phantom 300 GB of storage somewhere on the machine un accessible by me. Any insights would be helpful. I would like to get my storage capacity back without having to wipe the entire HD.
Thanks!

So I Found the issue.... It was stored in Private/var/zz/cleanup at startup
I found the profile name (home file) in the cleanup at startup folder and deleted it. System is working and now I have my disk space back.
I followed the directions that Linc Davis suggested in this post: How do I resolve 43+ GB of missing storage on the Macintosh HD?

Migration Assistant fails

i am installing leopard on a macbook. i have a full backup of my hard disk on an external firewire drive, made with SuperDuper. i can install leopard just fine, but when i use Migration Assistant to move all my users, files, settings, etc, it grinds for about an hour and then reports a "file transfer error." none of my data gets transferred. i would gladly move the files manually, and re-load all the applications, but certain apps, like addressbook, itunes, and ical, store their data differently in 10.5 than in 10.4. i have repaired the external with disk utility any number of times, ditto the hard disk on the macbook. i'm really flummoxed.

I'm having the same exact problem. the transfer gets right to the end and then says this:
An error has occurred that prevents the transfer process from continuing. Click Skip to continue through the setup process. To try again click Try Again.
I've done it twice, with the same results. I have 2 accounts on the Super Duper! clone, and one of them (76GB) transfered fine, but the bigger oner (640GB) had the above problem. Any ideas?

Migration Assistant fails me again

It seems every time I rely on Migration Assistant it bites me in the a**.
In the past, it wouldn't recognize certain partitions on an external drive.
This time, I thought it shoud be straighforward. My MacBook went in for repair and came back with a new hard drive. No problem, I thought. I'll just use Migration Assistant to get my files from my iMac (10.4.9, Core 2 Duo).
I booted the iMac into Firewire mode, and it mounted on the desktop of my MacBook, but Migration Assistant wouldn't budge, complaining that the attached disk does not have a partition with OS X on it. Huh???
Nothing I could do could cajole it into recognizing it.
Why does Migration Assistant have so much trouble. If the OS sees the drive, why can't Migration Assistant?
various Mac OS X (10.4.9)

Perhaps Pondinis' Excellent Information may be of value to you...
Have a look at this Link...
Using Migration Assistant on Lion
From here
http://pondini.org/OSX/Home.html

Migration Assistant fails to transfer from PowerPC G4 to MacBook Air

WiFi data transfer on home network server linking PowerPC G4 12" OS 10.5.8 using Migration Assist v 1.2.4 does not link with MacBook Air OS10.8.2 MA v5. Spinning clocks on both, but Air recognizes name of G4 machine. Time machine drive is firewire 800

Apple support: "Sorry, migration assistant WiFi won't work for OS 10.5.8 Leopard to OS 10.8.2 Mountain Lion, you need to buy an adaptor, Firewire to Thunderbolt, and use your Firewire cable and Target Disk mode." So much for the easy button.
Drove to town, bought the adaptor, but apparently not all Firewire is the same, Powerbook G4 firewire port and adaptor firewire dont mate. Out $32 bucks, gas, and lost the time saved up to fix the shower faucet. Grrr
Need ideas; move the Powerbook G4 files to iMac 27 and then to Macbook Air via WiFi and migration assistant? Move to USB external drive and then to Macbook Air in Target disk mode using migration assistant?, can Target Disk mode use USB? or mirror the G4 drive to USB drive? or?
Welcome suggestions . . .

Migration Assistant Fails x 4

Similar Messages

Maybe you are looking for