Migration Assistant fails, what to do now?

so, I was trying to upgrade pre unibody 15" MBP to a new UB MBP 13" last night. 10.6.3 to 10.6.5. I was using ethernet.
Everything seemed to be going fine, but after about 1.5 hours it just came to a dead stop for several hours. I had to disconnect since I had work to do.
Now, I don't know how best to proceed? Is there going to be some massive file corruption on the new target device? Is there a way to start the process over again? Should one actually do a CLEAN install now again on the target device so that the HD is not filled up with double the stuff?
Thanks for any guidance.

First using Ethernet isn't the best choice that connection tends to be unreliable. Because you aborted the process you may have damaged the install that is on the new machine so you will need to re-install and then using a Firewire connection use the Setup Assistant to migrate your data, files and applications. If you old MBP doesn't have FW 800 then use a cable like this one, a Firewire 400 to Firewire 800 cable. I would recommend reformatting the internal HD using Disk Utility on Install Disc, remember to set the format as Mac OS Extended (Journaled). Once that has been done then you can let OS X install.
After you have migrated you will need to run Software Update to get the most up to date software for your computer and also use the Application Install Disc that came with the new machine to install iLife.

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 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

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).

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 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 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 did not move user, now Keychains by the old user

There are a lot of posts about migrating to Leopard but I didn't find this particular issue:
I used the Migration Assistant after finishing the installation on my new MacBook (10.5.6). I set it to move one user account, software, documents and everything else (save networking preferences) from my old PowerBook G4 (10.4.11).
Instead of moving the user, it moved everything from that user and put it under a user on the new MacBook. That is to say, it did not create a new user on my new machine which would have had the name of the old user. Now everything is there and seems to work fine, but the Keys still carry the name of old user.
Has something gone wrong or is that the normal way fro Migration Assistant to do things? Is there a problem having the Keys under a different name from the user name?
(I noticed that when I first put Migration Assistant to work during the installation process, it did move entire users, so that the user account would be identical with the old machine in my new machine. However, due to problems relating to Intel and non-intel software I had to reinstall the system, after which I proceded according to what I explained above.)

Jyrki:
I have been using a Mac for twenty years because I considered it simple. But if one has to resort to procedures like described in the link you provided, one might as well use a PC...
That's interesting. I, too, have been using Macs for 20 years, and I found the procedure moving from PPC Mac to Intel to be very helpful. I had a very smooth transition, and I feel right at home on my new Intel Mac. Everything is exactly where it was on my Pismo, and it's great. Incidentally, I once thought of getting a PC and my youngest daughter, whom I raised on a Mac, scolded me soundly
cornelius

Migration Assistant - Failing to Transfer some Files?

I just used Migration Assistant when setting up my new MacBook Pro to pull over the contents of my old (early 2008) MacBook Pro. The Software ran without a glitch and the new machine is functioning normally.
However, when I look in "About This Mac - More Info - Storage", the aggregate memory used by files on the hard drive of my new machine for categories such as "Audio" and "Photos" differs from that on my old machine (about 10-20% less than the space used for these on the old machine). I didn't see any settings to select only a partial transfer, so the process should have pulled over everything, and now I'm worried there may be important files stranded on the old machine. Finding these amongst my library of music and photos could be very time consuming.
Does this mean not everything transferred, or could there be another explanation? I do recall that in iPhoto and Lightroom on the old machine there were placeholders for images that it said were no longer on the computer. Perhaps this is related and these "ghosts" explain the difference in what was pulled over?
Thanks for any advice.
Garrett

If you are migrating to a larger internal HD, then, percentage wise, these files would be taking up less space on your machine. Where are you getting these percentages from?
Finder Menu > Apple Logo About this Mac > More Info > Storage
#only shows disk usage in GB, not as % figures.
"The Software ran without a glitch and the new machine is functioning normally."
I suspect nothing is wrong and all your data was transferred.

Possible permissions issue - i used migration assistant from a backup and now i have multiple issues

Hi everyone,
I'd say my techie skills are low to medium so bare that in mind and be gentle with me
So 20" dual core died on Friday. poss psu issue which i will fix in due course. In a fit of extravagance I decided this message from beyond the grave from MR JObs was telling me to buy a new quad core on Saturday morning.
Because old imac was dead i used time machine back up via "migration assistant"
intially it could see the back ups but then seemed to spring to life after 20 mins
Got message saying not all content had transferred but reckon most did except for some safari stuff ( paswords etc).
Then i started to get issues with permissions i think.... asked me for passwords every time i tried to move files between folders or to trash or do pretty much anything.
read something about permissions conflicts when migrating from another admin/home account from and old imac
That when i started to activate my over "confident with technolgy" gene - i set HD permission to owned by "me" instead of system and then applied to all enclosed items
oops
now getting lots of dodgy messages eg every driver on the make brings up eeor message sayuing it was incorrectly installed
ran permissions repair - 25 mins later loads of unexpected acls have been corrected though not all -
still getting error messages about a few which i tracked down manually one by one and, sure enough, are still showing as owned by "me" and not system. Corrected them
Noticed at this point all other .kext files in same loaction have two permissions rows for "system in "get info" window = is this the root of my problem since using migration assitant?
still having issues
software updates won't install via the "software update" function but was able to install a couple of them myself direct from apple website.
back ups won;t back up to drive assigned - just keeps saying T|ime machine could not complete the back up even though there is space on freshly formatted external drive
so guys ..
have just created an unholy mess?
should i reassign "system" as owner for everything and then change foders such as documents and music etc to be owned by "me" or is that tooo simplistic?
should i wait till my old mac is brought back to life and re-do my migration ( since deleted the existing back up from old imac so thats not an option)
should i blame it all on apple and get them to sort it out under warrenty
or should i run naked down the street shouting wibble...
all help gratefully received . MY experience of apple products has been seamless over the years until now and I can't help think I have done some thing bad the wife will never forgive me for
HELP ME!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

You may not have created a mess, it's possible you simply don't know where your data is after migrating. Had you followed the Setup Assistant's on-screen prompts when you initially turned on your new system you would be running just fine by now. My guess is you haven't been exposed to Pondini's Lion Setup Assistant tips.
Migration Assistant (MA) and Setup Assistant (SA) are cousins, similar but different. The primary difference is MA creates a new user account which can be confusing to some users. If you successfuly migrated then log out of your existing using account and you should see the new user account. Log into that account then you should see the migrated data. If you do then use Pondini's Transferring files from one User Account to another.
However if you have totally made of mess out of things then I'd start over, this time using the Setup Assistant Tips beginning where he discusses Second Chance.

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!

Oracle Database Migration Assistant for Unicode (DMU) is now available!

Oracle Database Migration Assistant for Unicode (DMU) is a next-generation GUI migration tool to help you migrate your databases to the Unicode character set. It is free for customers with database support contracts. The DMU is built on the same GUI platform as SQL Developer and JDeveloper. It uses dedicated RDBMS functionality to scan and convert a database to AL32UTF8 (or to the deprecated UTF8, if needed for some reasons). For existing AL32UTF8 and UTF8 databases, it provides a validation mode to check if data is really encoded in UTF-8. Learn more about the tool on its OTN pages.
There is a new Database Migration Assistant for Unicode. We encourage you to post all questions related to the tool and to the database character set migration process in general to that forum.
Thanks,
The DMU Development Team

HI there!
7.6.03 ? Why do you use outdated software for your migration.
At least use 7.6.06 or 7.7.07 !
About the performance topic - well, you've to figure out what the database is waiting for.
Activate time measurement, activate the DBanalyzer with a short snapshot interval (say 120 or 60 seconds) and check what warnings you get.
Also you should use the parameter check to make sure that you don't run into any setup-induced bottlenecks.
Apart from these very basic prerequisites for the analysis of this issue, you may want to check
SAP Note 1464560 FAQ: R3load on MaxDB
Maybe you can use some of the performance features available in the current R3load versions.
regards,
Lars
p.s.
open a support message if you're not able to do the performance analysis yourself.

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 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, what to do now?

Similar Messages

Maybe you are looking for