ubiquity installation failures
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | migration-assistant (Ubuntu) |
Undecided
|
Evan | ||
| | ubiquity (Ubuntu) |
Undecided
|
Colin Watson | ||
Bug Description
Binary package hint: ubiquity
EDIT: I have isolated an error in Ubiquity. Partitioning will fail if drives are mounted. Please insert a warning or automatically unmount drives. The migration manager will fail as well if Windows partitions are mounted.
I had multiple failures during installation. If I was not determined to get Ubuntu running, I would have thrown the CD away.
I am on my 12th install.
1st install- General lockup and installer crashed
2nd install- Tried to import my AIM and Firefox configurations in the migration manager. After 20 minutes of stalling, I aborted installation.
3rd install- After skipping migration, the partitioner failed and automatically aborted.
4th install- Same error as above
5th install- I am very disappointed with the partitioner. It doesn't announce errors until it is too late and it is difficult to create logical partitions.
12th install- Finally, I have figured out what is wrong. I had some of my other drives mounted while installing. As soon as I unmounted and tried again, the installation worked. You may want to include a warning.
Often, the installer stalls, particularly during partitioning. The status bar will freeze at a certain percentage for several minutes before continuing. Most people would be tempted to quit.
ProblemType: Bug
Date: Sat Mar 3 23:21:22 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
Related branches
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| Changed in ubiquity: | |
| assignee: | nobody → kamion |
| status: | Unconfirmed → Fix Committed |
| Colin Watson (cjwatson) wrote : | #1 |
| Colin Watson (cjwatson) wrote : | #2 |
ubiquity (1.3.25) feisty; urgency=low
[ Evan Dandrea ]
* Handle spaces in usernames in migration-
* Fixed list movement bugs on the Migration page. Also, selecting an
item now selects the user as well. (LP: #89414)
* The Migration page now auto-fills the username box, matching the
behavior on the User Setup page. (LP: #89522)
* Stopped the username auto fill on User Setup from clobbering the m-a
username.
[ Colin Watson ]
* GTK frontend:
- Don't reset partition_
causes GTK warnings.
- Add more space around text in question dialogs.
* New partitioner: Allow changing the mount point for NTFS (LP: #90276).
* Automatically unmount mounted partitions if they are on a changed
partition table or they are to be mounted somewhere other than /media/*.
Display an error and allow the user to try to unmount them manually if
automatic unmounting fails (LP: #89605).
* Work around datetime misbehaviour if the system clock is set before the
Unix epoch (LP: #57952).
* Add XS-Vcs-Bzr field to debian/control.
* Automatic update of included source packages: console-setup 1.13ubuntu7,
localechooser 1.37ubuntu1, migration-assistant 0.4.1, partman-auto
62ubuntu6, partman-base 100ubuntu7, partman-efi 11ubuntu3.
-- Colin Watson <email address hidden> Wed, 7 Mar 2007 15:21:48 +0000
| Changed in ubiquity: | |
| status: | Fix Committed → Fix Released |
It should already umount the drives in migration-assistant as I fixed that in a similar bug previously, however I will work a warning dialog into that code for cases where it cannot unmount the partition.
| Changed in migration-assistant: | |
| assignee: | nobody → evand |
| status: | Unconfirmed → In Progress |
migration-assistant (0.4.2) feisty; urgency=low
* Added XS-Vcs-Bzr field to debian/control.
* Mount /home if necessary. (LP: 85222)
* Display an error on unmount failure and prompt the user to continue.
(LP: 89605)
* Put usage statements on stderr. (LP: 89821)
-- Evan Dandrea <email address hidden> Tue, 13 Mar 2007 19:57:19 -0400
| Changed in migration-assistant: | |
| status: | In Progress → Fix Released |
| Colin Watson (cjwatson) wrote : | #5 |
ubiquity (1.4.0) feisty; urgency=low
[ Colin Watson ]
* Use just one progress message for all target-config hooks, to avoid
uglinesses like "Running 32gnome_
* KDE frontend: In the partition create dialog, set the maximum partition
size before setting the value to avoid the value being incorrectly
clipped.
* Disable the intro message for beta.
* Add kboot-installer integration for powerpc/ps3. Explicitly detect the
subarchitecture and select which boot loader to install based on it.
* Automatic update of included source packages: grub-installer
1.20ubuntu3, migration-assistant 0.4.2, partman-base 105ubuntu1,
partman-
1.1.8ubuntu2.
[ Evan Dandrea ]
* When m-a is disabled, don't try to run its apply script. (LP: 89821)
* If migration-assistant cannot unmount a partition, prompt the user
to do it manually. (LP: 89605)
* Added another descriptive label to the Migrate page.
-- Colin Watson <email address hidden> Thu, 15 Mar 2007 03:41:04 +0000
| Ioannis Ramfos (isr81) wrote : | #6 |
I tried to install Karmic after having the (would be) root partition of the installation already mounted. Konsole was running and the current directory was the mounted one.
The installer warned me about the mounted partition and that it would try to unmount it (it informed me of a mounted disk /dev/sda). The installation process reached the final step when I was warned of the mounted partition again (as /dev/sda1 this time) and that a process was using it. Afterwards, a similar warning appeared for the mount state of the whole disk (/dev/sda).
Both times I selected to try to unmount the partitions after closing Konsole.
The installer offered a retry which led to a bug report form and the return to the partitioning step of the installer. I continued at that point but upon validating the partition table, the crash report appeared again and ubiquity crashed and exited.


I've made ubiquity itself automatically unmount partitions and warn if it can't. Evan, could you check out the comment about migration-assistant having a similar problem?