Ubiquity's Installation Type Window Totally Unresponsive

Bug #878568 reported by SlugiusRex
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Attempting to install 11.10 on a completely new unformatted disk

Update manager completely mangled my previous 11.04 desktop and corrupted GRUB ~ so I deleted all the disk volumes, and am attempting to install fro scratch.

The "trial" works great, and I am able to get as far as the "Installation Type" window. However, at that point, none of the buttons are responsive; and 'Install Now' reports 'No root file system is defined. Please correct this from the partitioning menu'.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ubiquity 2.8.7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
CasperVersion: 1.287
Date: Wed Oct 19 23:08:45 2011
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.7
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
SlugiusRex (slugiusrex) wrote :
Revision history for this message
SlugiusRex (slugiusrex) wrote :

Here's an image of the Disk Utility program that shows the state of the disk onto which I am attempting to install Ubuntu 11.10.

Revision history for this message
SlugiusRex (slugiusrex) wrote :

The issue is related to the fact that the drive is descried as "Raid Component" in the Disk Utility Image (see comment #2).

I was able to use disk utility to remove this by formatting the drive as empty ~ and was able to continue on with the installation. So I am now happy. However I am very displeased with the installation process. I believe that this drive being flagged as "Raid Component" is what caused the original 11.04 to 11.10 system upgrade to fail; and is also responsible for the USB/DVD installation process to break.

All of the documentation I found on-line says that I should have first seen a Ubiquity screen that displays some nice graphics offering the "Install Alongside / Erase Disk / Something Else" options. But this never happed. Instead Ubiquity went straight to the partition editor screen ~ but that screen was missing the nicely colored partition representation at the top of the screen. Also, none of the buttons worked ~ and the only option was to abandon the installation using quit.

The cause of the problem dates back to my initial installation of Jaunty/Karmic on this machine. At that time the default Windows installation was ditched, and Ubuntu was successfully installed using the pre-Ubiquity installer/partitioner. However, during all the subsequent Karmic -> Lucid -> Natty conversions the problem never surfaced.

Ubiquity should provide a more more elegant for detecting that the partitioner cannot proceed and should give a more useful approach to continuing the installation instead of just forcing the Quit.

Revision history for this message
Billy Hand (billythethird) wrote :

I have the same problem and formatting my disk to empty is not an option. I'm not sure I can use Ubuntu if a blocking bug can go this long without being addressed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
SlugiusRex (slugiusrex) wrote :

Yes, it was a serious problem. Does/did the disk originally have Windows installed with the "Raid Component" option selcted (e.i. from Acer ). If so I don't think that there is a work around that doesn't involve wiping the whole thing?

Ubiquity should provide a more more elegant for detecting that the partitioner cannot proceed and should give a more useful approach to continuing the installation instead of just forcing the Quit.

Revision history for this message
dino99 (9d9) wrote :

This version has expired for some time

Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
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.