Installer hangs at "Migrate" on eMachines w3080 w/XP on 2nd HD

Bug #96083 reported by datamagik
12
Affects Status Importance Assigned to Milestone
migration-assistant (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

My eMachines w3080

AMD Athlon XP 3000+
512MB RAM, K400 chipset shared memory S3 chrome video chipset

2 80gb HD, trying to install on Master (iirc the Maxtor). I have Win XP on the Slave drive (have been reinstalling successive versions of 7.04)

I'd just installed FreeBSD 6.2 on the primary drive in a 20gb partition and had hoped to add the latest herd of Ubuntu and see if Ubuntu spotted it and would boot that from GRUB as easily as it does Win XP.

The installer gets as far as step 6 of 8 (Migrate Documents and Settings) but even after leaving it there overnight it's still stuck at the progress cursor and the only active button is cancel. Cancel does work so technically the application isn't "hung".

I tried selected both options for the primary drive (both use free space, then erase entire drive)...both "guided" setups. As I type this I realize that I didn't try manual configuration to see if that made any difference (and I suppose I could try without the Win XP drive physically connected). As I'm retrying this again I'm reminded that the steps seem sluggish when I click on the forward button (such as for Time Zone or Keyboard selection steps) it sometimes ignores the click and I have to click again. This is very repeatable on my machine.

Ok so, this bug is repeating, whether I use guided use only free space, guided reformat drive, or manual partitioning. The forward button never becomes active (and the text in that step refers to it as the "next" button).

Regards,

Jay
<email address hidden>

ProblemType: Bug
Date: Sun Mar 25 19:53:45 2007
DistroRelease: Ubuntu 7.04
Uname: Linux ubuntu 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

Revision history for this message
datamagik (debug-datamagik) wrote : Re: [Bug 96083] Installer hangs at "Migrate" on eMachines w3080 w/XP on 2nd HD

To confirm my earlier theory: I disconnected the second HD which
contains Windows XP and again attempted to install 7.04 herd 5.
Without the XP drive the installer did not hang on the Migrate step,
but rather quickly reported finding no suitable OS to migrate.

I now have the machine described in the orginal bug report booted up
with herd 5. Of course I will have to make my OS selection from the
BIOS setup (or modify the GRUB config file).

Revision history for this message
Evan (ev) wrote :

Can you run the installer again from a terminal window with the --debug option and attach /var/log/syslog and /var/log/installer/debug to this bug report? Would it be possible for you to try this with the beta release (http://releases.ubuntu.com/feisty/) instead of Herd 5?

Detailed instructions on attaching debug logs can be found here:
https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs

Thanks!

Changed in migration-assistant:
assignee: nobody → evand
status: Unconfirmed → Needs Info
Revision history for this message
Evan (ev) wrote :

You could also run `sudo apt-get update; sudo apt-get install ubiquity` in a console on the Herd 5 CD to give you the latest version of the installer in lieu of using the one on the daily CD.

Revision history for this message
deisler (dennis-solidstateservices) wrote :

I have just run into this problem. The following workaround seemed to work in my situation. The following information appeared in the Migrate Documents and Settings dialog box: "There were no users or operating systems suitable for importing from."
This option is highlighted by default. When you click Forward, the installation stops responding (hangs). To resolve this problem, you must deselect the highlighted entry. To do this, follow these steps:
1. Press any key a few times such as GGGG. In this scenario, a text box appears.
2. Press Backspace to delete the entries from the text box. (the G's that you entered in step 1)
3. The default "There were no users or operating systems suitable for importing from" entry is no longer highlighted.
4. Click Forward to continue the installation.

Revision history for this message
B. D. White (felixruina) wrote :

I would like to confirm this bug. I'm on an AMD 2800+ with an NForce chipset MB, Windows XP is installed on a 40GB Seagate Master and I was installing Ubuntu Gutsy Beta on a 160GB Maxtor drive. If the debug logs are needed, I will be happy to supply them.

Revision history for this message
kripken (kripkenstein) wrote :

> The installer gets as far as step 6 of 8 (Migrate Documents and Settings) but even after leaving it there overnight it's still stuck at the progress cursor and the only active button is cancel. Cancel does work so technically the application isn't "hung".

I can confirm this exact same bug, on the Gutsy Beta Live CD. After clicking to continue, the cursor spins as if activity is taking place, but nothing happens. Clicking 'cancel' works, however, just as described above.

Revision history for this message
parren (peter-arrenbrecht) wrote :

Same here. Gutsy beta. WinXP and Ubuntu 7.04 on different partitions of same disk.

Revision history for this message
parren (peter-arrenbrecht) wrote :

However, I don't see any "Cancel" button. No button at all.

Revision history for this message
parren (peter-arrenbrecht) wrote :

This does not happen when I first step back into the migration dialog of the wizard (step 6), which was skipped initially (probably due to manual partitioning - see bug #148143). Then I just have to say "Continue" twice in the unmount error dialog.

Revision history for this message
Evan (ev) wrote :

I would appreciate that anyone who is experiencing bugs with migration-assistant run the installer with the --debug option (`ubiquity --debug` in a terminal window) until it hangs or crashes and then attach /var/log/syslog and /var/log/installer/debug to a new bug report following the directions in https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs.

Thanks!

Revision history for this message
parren (peter-arrenbrecht) wrote :

OK, here come the logs. Gutsy Beta. Manual partitioning, root on sda7 (reiserfs). Existing Feisty on sda4 (ext3), Windows XP (ntfs - I think it's sda2). m-a wizard step (6) was skipped automatically and I did _not_ go back to it (otherwise this problem does not happen). First there is a dialog about m-a not being able to unmount /mnt/migrationassistant. I click Continue. Then the installer hangs at "Importing documents and settings...".

Revision history for this message
parren (peter-arrenbrecht) wrote :

And the installer log

Revision history for this message
gronbaek (gronbaek) wrote :

Same problem here. / is at sda6 an is set for format, /home is sda7 and should not be formatted. WinXP is at /sda2 i think. Syslog reports that it's unable to unmount /mnt/migrationassistant. The installer hangs at step 6, as soon as I press Next (or forward, or what it says, I'm seeing this in Danish). I can stop the installer by pressing Cancel.

Revision history for this message
gronbaek (gronbaek) wrote :

And the debug log.

Revision history for this message
gronbaek (gronbaek) wrote :

Incidently, I can force /mnt/migrationassistant to unmount: "sudo umount -f /mnt/migrationassistant/" and the process continues.

Revision history for this message
datamagik (debug-datamagik) wrote :

This bug was fixed in the later beta versions and release and does not exhibit itself on 7.04 or 7.10 release running on the identical system hardware.

Revision history for this message
Andy Brody (abrody) wrote :

I ran into this same problem in the 8.04 Hardy beta. (The symptoms were the same but the directory it couldn't unmount was different.) Upgrading from the CD's ubiquity v1.8.0 to the latest v1.8.4 resolved the issue.

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for posting this bug.

Does this issue occur with Lucid?

Evan (ev)
Changed in migration-assistant (Ubuntu):
assignee: Evan Dandrea (ev) → nobody
Changed in migration-assistant (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.