Installer reports: No root filesystem is defined

Bug #746832 reported by David Klasinc on 2011-03-31
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)

Bug Description

Binary package hint: ubiquity

- disk with Ubuntu Natty already installed

Follow these steps to reproduce:
- start installation
- when you get to the Allocate disk space, select "Erase Ubuntu Natty and reinstall" and click forward
- On next screen click Advanced partitioning tool
- Do nothing and just click Back
- You are back at Allocate disk space, again select "Erase Ubuntu Natty and reinstall" and click forward
- Click Install now

An error message "No root filesystem is defined" will show. From this point on it is impossible to continue the installation. I managed to get around this one time. After the first error I went and manually selected partition that should be used as root and told installer to format it.

If you stay and play around in partitioner and jump back and forth between the screens, installer will crash and die a horrible death.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: ubiquity 2.5.22
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
Date: Thu Mar 31 23:13:22 2011
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

David Klasinc (bigwhale) wrote :
David Klasinc (bigwhale) wrote :

I noticed that I had Alpha3 booted. I tried with Beta1, same thing.

Dave Gilbert (ubuntu-treblig) wrote :

Confirming since it's a clear set of steps, and I saw the same thing going back out of advanced partitioning.


Changed in ubiquity (Ubuntu):
status: New → Confirmed
tags: added: ubiquity-2.5.22
dino99 (9d9) wrote :

natty have reached EOL now

Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers