InstallStepError: MigrationAssistantApply failed with code 10

It's notable that during the question stage of the install, David did not see the migration assistant screen (and therefore did not have the option of excluding the troublesome partition). During a stock 7.04 install, this page was displayed as normal.

I also was trying an install of latest Ubuntu (standard Gnome, downloaded 2007-10-01) using manual partitioning.
Disk ID is DISKNAME Ubuntu 7.10 "Gutsy Gibbon" - Beta i386

Machine is a 2K Celeron, 5/8 GB RAM, 6 hard drives and 2 optical drives (yes - a bit silly, but I want to play around a bit)
hda is a 30GB QUantum AS 30, hda1 has WinXP, hda2 did have Feisty but putting in the extra drives I had a fumble fingers and blew it away.
Hence opportunity to try Gutsy. Kubuntu installed OK. Did not like the setup (the menus had all kinds of extra text. Not sure how to report this.)
Then tried standard Gutsy (i.e Gnome version).

Migration assistant presented screen to choose to import documents etc. I decided NOT to do this. However, later on, I get a message that installer cannot UNMOUNT /mnt/migrationassistant partition. I ignored this the first time and got an unbootable system. On a second try, I opened a terminal and did "sudo su" and unmounted /dev/hda1 (the winXP partition) that was mounted on /mnt/migrationassistant. Since there was a copy of this partition on another drive (I'm trying to mirror), I got a second error pop-up and also had to unmount /dev/sda1 that got mounted on /mnt/migrationassistant too.

The install seems to have gone OK, but neither hda1 nor sda1 (the WinXP copy) appear as mounts. Looks like unmounting them took them out of the automatic fstab.

I'll be happy to help out by trying s/w to check installer, but would prefer to avoid full re-install if possible.

Prof J C Nash, Pres. Ottawa Canada Linux Users Group

Matt,

I believe this was caused by poor IFS handling and it should be fixed on the RC candidate images. Can David test again to confirm this?

Thanks!

He's subscribed and should be able to respond when he has the opportunity

I'll download the latest image, burn it and try it tonight.

Evan Dandrea wrote:
> Matt,
>
> I believe this was caused by poor IFS handling and it should be fixed on
> the RC candidate images. Can David test again to confirm this?
>
> Thanks!
>

--
David Mandala <davidm at canonical dot com>
http://www.canonical.com/ Public Key id: 45B2D952
Murphy TX, 75094 +1.214.774.2569 O +1.972.693.4007 C

Tested, with some success, it did ask about migration, I ignored it and
it installed to completion.

It complained three times about being unable to unmount
/mnt/migrationassistant. The first time just before asking if I wanted
to migrate the windows partition, the second just after that screen and
the last time nearly at the end of the install, somewhere in the 90%
range. In all cases I told it to continue the install.

Cheers,

David

DavidMandala wrote:
> I'll download the latest image, burn it and try it tonight.
>
> Evan Dandrea wrote:
>> Matt,
>>
>> I believe this was caused by poor IFS handling and it should be fixed on
>> the RC candidate images. Can David test again to confirm this?
>>
>> Thanks!
>>
>
>

--
David Mandala <davidm at canonical dot com>
http://www.canonical.com/ Public Key id: 45B2D952
Murphy TX, 75094 +1.214.774.2569 O +1.972.693.4007 C

I've been trying to track down the root cause of that in another bug. If you could add set -x to the second line of /usr/lib/ubiquity/migration-assistant/ma-ask, run the installer until you get one of those messages, and then attach /var/log/syslog to this bug report it would be a great help. You don't actually have to commit the install to disk.

Thanks!

Evan Dandrea wrote:
> I've been trying to track down the root cause of that in another bug.
> If you could add set -x to the second line of /usr/lib/ubiquity
> /migration-assistant/ma-ask, run the installer until you get one of
> those messages, and then attach /var/log/syslog to this bug report it
> would be a great help. You don't actually have to commit the install to
> disk.
>
> Thanks!
>

Log attached. The error happened twice, between step four (4) and five
(5) and again between five (5) and six (6). Then I bailed out of the
installer.

Hope it helps.

David

--
David Mandala <davidm at canonical dot com>
http://www.canonical.com/ Public Key id: 45B2D952
Murphy TX, 75094 +1.214.774.2569 O +1.972.693.4007 C

David,

Launchpad doesn't support email attachments as bug attachments yet. You'll need to manually add them using the web interface.

Thanks!

Syslog file from partial install test.

Not sure whether this is the same bug.

Environment: 6.10 installation, trying to upgrade to 8.04 (preserving /home, discarding everything else).

I told the installer to format all partitions except /home, thinking it would realize I was trying to do a clean install, not an upgrade. No luck. The "Ready to Install" page had the following error message:

10 migration-assistant/sda9/users doesn't exist: 10 migration-assistant/sda9/10+migration-assistant/sda9/users+doesn't+exist/items doesn't exist

And then after the install "finished" and I was presented with a desktop, it turned out that none of my partitioning instructions had been followed -- the non-/home partitions were mounted on /target, /target/tmp, etc., rather than /, /tmp, etc., and /home was mounted on /mnt/migrationassistant.

I tried following the "Clean Install Upgrade" instructions on https://help.ubuntu.com/community/Installation/UpgradeFromOldVersion , but that didn't work either -- the same thing happened.

FWIW, I have been trying to upgrade my 6.10 installation for over a year -- to 7.04, 7.10, and 8.04. Every time, the installer (ubiquity) has been broken in a different, show-stopping way. And since 6.10 is no longer supported and I can't get updates for it or even load new packages into it, it looks like I'm going to have to go out and buy a new hard drive to do a from-scratch install of 8.04, and then copy the /home partition.