Stuck in migration assistant

Got a macbook air yesterday with the I-7 processor. I downloaded the new Migration Assistant to the Macbook and connected it to the Air with ethernet via the USB to ethernet adaptor. Proceeded with the migration. All appeared well although slowly until about an hour ago when the progress bar quit progressing. It is stuck at 1 hour 4 minutes to go. This is after 22 hours of transferring data!
The "donor" computer is a Macbook running 10.6.8 and the Air is running Lion which was on the machine when purchased.
What should I do?
TIA
Lewis

Be sure the "donor" hasn't gone to sleep.
Are you using Setup Assistant (when your new Mac first started up), or Migration Assistant (after creating a new user and starting up that app)?

Similar Messages

  • What do I do when my computer is stuck using migration assistant on applications

    I am using migration assistant on a new Mac Air and it says it is transferring my Applications folder but has been doing that for hours. What do I do now?

    Hate to be captain obvious... but do you have a SIM in it? If you do, get a replacement SIM. It may have failed.

  • Migration assistant stuck

    I just received my sweet new 27 inch iMac.  I hooked it up to my old iMac with a Firewire 400 cord and asked the Migration Assistant to transfer my files (approx 750Gigs).  It first estimated 100 hours and the progress bar started, but the was two days ago and the last 24 hours the progress bar has not moved and is stuck on 230 hours with no end in sight.  I'm asssuming I should just stop it and try again, but I'm not sure why it would work the second time.  Is it more reliable to simply create a backup on an external drive and use that to migrate my programs/data?  Also is there any risk to my data in stopping a migrataion midway?  Thanks all.

    Welcome to the Apple Support Communities
    Disconnect the FireWire cable and connect it again, so migration should continue. That's what I did when my migration, using FireWire too, gets stuck.
    If it doesn't work, just restart and migrate again. Maybe one of the computers get stuck during migration and it's not transferring anymore

  • Migration Assistant Progress Bar Stuck Halfway

    Today I bought the new 13" MacBook Pro (baseline).  I updated Migration Assistant on my 2008 Macbook and after that the transfer of content to the Pro seemed to be going smoothly.  However, the progress bar of Migration Assistant has stuck halfway, with an estimated 40 minutes remaining.
    I don't know if this is related to the fact that I forgot to have my 2008 Macbook charging and so it ran out of battery during the process, until I realized it and attached the charger.  When I looked online for an anwer, someone had said to make sure that the "donor" computer didn't go to sleep, so I went and changed the settings on the Macbook so it wouldn't go to sleep.  Nothing happened and I don't know what step to take next. 

    The Migration Assistant is known (by users of this board) to be problematic between PowerPC and Intel. If you succeeded the first time, it may be the problems the second go around even though they are between Intel Macs, is from any Rosetta applications and plugins installed on your older Intel Mac.
    Here's the user tip Kappy and I wrote about migrating between platforms:
    http://discussions.apple.com/click.jspa?searchID=-1&messageID=1872713

  • I'm using migration assistant to transfer files from my wife old net book to new mac air and the pc dropped out during transfer.  Pc now says waiting for mac to connect and has is stuck at transferring information.  How do I get the process to continue?

    I'm using migration assistant to transfer files from my wife old net book to new mac air and the pc dropped out during transfer. I started up migration assistant on the Pc again and now says waiting for mac to connect! New MacBook Air  is stuck at transferring information.  How do I get the process to reconnect and continue?

    Whew, good luck!
    What version of OSX is on the older one?

  • Migrate Assistant Stuck

    Hi again,
    OK, I just ran a clean install and I'm now using Migration Assistant to restore all my files. It's been stuck for almost an hour on Estimated time: 46 minutes on "Transferring files to support applications". I don't know if the progress bar is moving (I just started taking pics), but is this a big deal? Can I just stop the migration assistant and run it again? What comes after "Transferring files to support applications"?
    Thanks,
    Don
    Message was edited by: Don Palm

    All I can do is tell you what I did - YMMV.
    Migration Assistant quit on me with a minute to go. I figured it had done most of it's work, so I did a power off and restarted. 10.5 started and this time I told it to not bother importing any data. It then prompted me to set up and account, which I did. Once the login process finished, I logged out and was pleased to discover that all my accounts were there, so I logged in to my main old account, ran it for a while and found that everything seemed to have been moved. I then deleted the account I had to create to finish the install (above).
    However, if you had an hour to go, it is highly likely that your data was not moved. In that case you will have to wait for Apple to release an update to Migration Assistant so you can move your accounts from your old area.
    Note: I have two OS partitions: One with Tiger (10.4.10) and a clean one for 10.5. I moved accounts from the Tiger partition to the Leopard partition using the Assistant.

  • Migration assistant from TimeMachine stuck on "calculating"

    Hi
    I Have just done a clean install of Mountain Lion on my 2011 iMac and am now trying to restore user info (I.e. files) from a TimeMachine back-up using migration assistant.
    Migration Assistant has spent several hours, apparently stuck, on "calculating" for the size to migrate for the "Users" component.  If I click continue, nothing gets migrated. Have restarted the process, and yet again it has been more than 3 hours and still it appears to be "calculating".
    My questions:
    - is this normal?
    - if so, how long should I wait before giving up?
    I have about 240Gb of music and photos on here that I'm hoping to restore.
    Thanks for any tips!

    Hi ndt,
    That's what happened to me too. Time Machine keeps calculating file sizes when I tried to restore (using migration assistant), after a clean installation of Moutain Lion.
    Yes I already did what Andy did to solve his problem, which is create a new admin and restore from that new account. This is required because Migration Assistant wont restore (overwrite) to an account with same username. Somehow, it gives me an infinite loop of calculating file sizes.
    My solution was re-installing (clean) Mountain Lion. During the installation, use the Migration Assistant that comes with the installation set up program. Do not skip that process. For some reasons, it can calculate the file sizes and restore successfully.
    Hope that is clear.
    Thanks.

  • HT4413 Migration Assistant stuck

    I am using Migration Assistant to transfer data from an old MacBook Pro (2007) to a new MacBook Pro (bought yesterday).  Migration Assistant gets hung up and the estimated time to make the transfer is stuck at 16 hrs and 24 min. Am using Firewire for the transfer. 

    Start over, booting into recovery mode  (CMD+R on restart) and restore the OS. Then, on first boot follow the steps in Pondini's Setup New Mac guide.

  • Is Migration Assistant stuck?

    I'm migrating one MBP to another MBP wirelessly.  The Apple Tech mentioned I would be able to select folders to migrate, since I didn't want to migrate everything. 
    However, the new MBP has been sitting on the screen
    Transferring Your Information
    Starting Migration...
    For 1/2 hour now.  The older MBP says "Your other Mac is ready".  Both have the blue stripped spinning bar animation going. 
    Is something wrong with the migration?  Shouldn't it have already displayed the option to select folders?  Will it ever show progress or some indication it isn't stuck?

    You have some idea what went wrong on that?
    Nope, but since the migration didn't result in anything useful you might as well delete that account and try a different approach:
    Leave the external hard disk "clone" connected to the new Mac. Log in to whatever account you created using Setup Assistant. Go to System Preferences > Users & Groups, and create a new User account with a temporary, "throwaway" name and password. Make sure to check the box "Allow user to administer this computer". As usual, don't forget the temporary account's password.
    Log out, then log in to the temporary account. Using System Preferences > Users & Groups again, delete the first account you created. Select "Delete the home folder" then the Delete User button. The only account remaining will be the one you're using, which will exist for the sole purpose of migrating your old account.
    Close System Preferences and open Migration Assistant - it is in your Utilities folder. Follow the instructions to migrate your previous account from the old MBP.
    When it completes, log out and log in to the newly migrated account. Verify its contents are complete and everything works as you expect. Assuming that is successful, you can eventually delete the "throwaway" account you created earlier.

  • New iMac is stuck on grey apple screen after restart from Migration Assistant

    New iMac is stuck on grey apple screen after startup. It is a 3.4GHz Quad-core Intel Core i5 running OS 10.9.4. The problem occurred after a migration from my older 2009 iMac which is running Snow Leopard 10.6.6. When the restart occurred from Migration Assistant, the new computer will not boot up to the login screen. Disk utility did not solve problem. Followed instructions for a soft reinstall of Mavericks but that also did not solve problem. Any suggestions?

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • Migration Assistant stuck on "Looking for source..."

    I just bought a new iMac today and I am trying to use Migration Assistant to move all my info on my Mac Pro to my new machine. The problem is that the Migration Assistant is getting stuck at the "Looking for source" step, trying to find my old Mac with no success.
    Yes, I've searched for other posts about this issue and I've looked at a number of support.apple.com articles about this. The discussions closest to my problem all have some issue that isn't present for me. Here's a bit of information that may or may not be pertinent to what's going on:
    One support article said that the source Mac had to be running at least OS X 10.6.8. My old mac is running 10.7.5.
    Neither Mac is running with the firewall turned on.
    I did not use Time Machine with my old Mac, and it is turned off on both Macs.
    I have run Software Update on both Macs and everything is up-to-date.
    I also tried setting up a wireless computer-to-computer connection. I created the network on my old Mac, and was able to connect just fine through Finder on my new iMac. Running Migration Assistant, however, I could not see my old Mac's network and, as for clicking on "Other Server" button in the Assistant, I can say I would know how to specify that network's address given the format afp://Server/ShareName/. For the sake of argument, let's say the network's name was "oldMac". I did try entering "oldMac" for "Other Server" and then "afp://oldMac" and neither of those worked.
    One other thing. I do have an Apple TV. I don't see why this should interfere, but I am able to view and play my music and movies on my TV, so apparently the Apple TV can see the old Mac fine as well. And no, the Apple TV was not on while trying to migrate my data.
    TIA,
    bob

    Ok, more updates.
    In my old Mac (Pro) I have several hard drives installed. I was able to create a Time Machine back-up to a non-system HD. I plan on removing this volume and putting it in an external enclosure as soon as I can find the right cables for that enclosure. Meanwhile....
    I saw on one support doc an instruction to open Sharing on the source Mac (my old one, in this case) and make sure the machine had a name specified. I already had done that, but noticed that a specific name based on that was mentioned for other computers to contact it. For example, if my source machine is named "myOldMac", other computers could address is at "myOldMac.local".
    I connected the two computers directly via an Ethernet cable and I ran Migration Assistant again. When I got to the "Looking for source" screen, I clicked the button for "Other Server" and entered "afp://myOldMac.local". This actually found my old Mac. I was prompted to enter the password for the account "root". I changed the name to my account's short name -- "raboyle" not "Robert Boyle" -- and entered the correct password and I actually got a list of volumes to access. In the list were: the hard drives (by volume name), the home folders of the user accounts, and the Public Folders for each user account.
    I tried accessing both my boot volume and the home folder for my primary account, and proceeded to a screen with the following text: "Choose which backup to transfer information from:". The list provided, however, was empty. On the chance that it was looking specifically for a Time Machine backup, I then specifically chose the HD volume with the backup I had just created. Again, the list to choose where to grab my data from was empty.
    So, at least I'm advancing a little bit beyond the "Looking for source" screen ... but then again, since I hit yet another roadblock I can't say whether I've taken one step forward or two steps back.

  • Migration assistant stuck at 4 min. Help

    Trying to transfer from MacBook Pro with Lion to new iMac. Stuck on 4 mins for several hours. Says it is transferring application support files? What do i do?

    akkaneko wrote:
    I just got a macbook pro but there seems to be some problems with the migration assistant.
    I used ethernet cables to connect my macbook pro to my macbook, and it transfered fine for about 3 hours. Right when I thought I was going to be able to use my macbook pro, it got stuck. It says "transferring files to support application" and below that "less then a minute remaining". What can I do?
    PS. I'm running the newest version of leopard on my old macbook.
    Thanks in advance.
    Ignore the estimate and leave it alone, it can take longer than you imagine but it does complete, eventually.
    Ethernet is not particularly fast at this task in my experience.

  • Migration Assistant -- stuck at "Inspecting your computer" for more than 3 hours

    I am in a process of setting up a new Mac Mini 2011.
    I have completed the initial setup. Now I am trying to bring over the profiles & files with Migration Assistant from a Windows 7 system.
    On the Mac side, it was able to find my Windows system, but it has been stuck at the "Inspecting Your Computer..."  in "Select items to migrate" screen for more than 3 hours. Is this normal? Should I waiy a biy longer or start over?
    TIA

    My computers happened the same too. I left the computers for more than 12 hour and did not progress to anything. It only said. "inspecting your computer".

  • Migration Assistant stuck at "less then a minute". HELP!

    I just got a macbook pro but there seems to be some problems with the migration assistant.
    I used ethernet cables to connect my macbook pro to my macbook, and it transfered fine for about 3 hours. Right when I thought I was going to be able to use my macbook pro, it got stuck. It says "transferring files to support application" and below that "less then a minute remaining". What can I do?
    PS. I'm running the newest version of leopard on my old macbook.
    Thanks in advance.

    akkaneko wrote:
    I just got a macbook pro but there seems to be some problems with the migration assistant.
    I used ethernet cables to connect my macbook pro to my macbook, and it transfered fine for about 3 hours. Right when I thought I was going to be able to use my macbook pro, it got stuck. It says "transferring files to support application" and below that "less then a minute remaining". What can I do?
    PS. I'm running the newest version of leopard on my old macbook.
    Thanks in advance.
    Ignore the estimate and leave it alone, it can take longer than you imagine but it does complete, eventually.
    Ethernet is not particularly fast at this task in my experience.

  • Migration assistant stuck on new 15' MBP. Help!

    I've been having a terrible time with the migration assistant. I have a new 15'MBP retina fully loaded. Been trying for days to transfer my old applications, etc from my older 15' MBP. I could not do it through the wifi (tried but it just died after 18 hours). So I hooked up the computers with fw800 (with thunderbolt adapter on the new computer) and that didn't work. Then I backed up my old computer using time machine and am trying to setup new one with that backup but it's been 18 hours and seems yo be stuck. The bar is at the same place it was 8 hours ago. The estimated time went up from 3+ hours to 5 hours, so I guess something is happening even though the bar hasn't moved? I have about 350gb of stuff so I get it could take a while but it's been about 18 hours. What should I do! This is driving me crazy... I need to be up and running for work tomorrow.

    Hello
    try this
    put your tow imac side by side then plug an ethernet cable between us , ethernet logo look like that
    then on each imac desable wifi ( air-port )
    go to system preferences -> network , you should see somthing like that
    select from Configure IPv4 to MANUALY on both imac , then fill info for ehternet exactly as folow
    for 1st Imac
    for 2d Imac
    then try launch again migration assistant , or use file sharing options on old imac
    HTH
    Pierre

Maybe you are looking for

  • Calendar colour changes

    My work calemdar suddenly changed from Green To Purple which clases with onother canendar. Unable to get it back. This seems to be a problem for many people. Any answers??

  • Create multiple deliveries against the same customer return order

    I want to create multiple deliveries against the same Customer return order. But once the RF transaction is run it closes all the lines.  We need to be able to receive multiple times against the same RA number and create different deliveries. Any ide

  • SATA issues with 2.6.18 and Dell Poweredge SC420

    My primary HDD is on SATA. My secondary HDD is on SATA through a PATA --> SATA adapter. Everything works quite nicely under 2.6.17 (any version). Under 2.6.18, my primary HDD is detected just fine, but the secondary is not. It's hard for me to do any

  • Saving metadata from Lightroom erases custom XMP data in DNG...

    Hello,    There seems to be an issue with the way Lightroom applies changes in from the LR catalog to the assets metadata.  The setup is LR 2.5 and there is an orginal set of images that have custom XMP data applied to them via Bridge.  There is one

  • Weird Sapscript output

    Hi everyone! My problem goes like this:  I recently revised a sapscript driver program for the payment advice form, which is working fine in another version.  The problem is, when I copied the subroutine to another version of the driver program, what