Bug 502509 - Your / partition does not match the the live image
Summary: Your / partition does not match the the live image
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-25 14:58 UTC by Traxtopel
Modified: 2009-05-26 16:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-26 14:05:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Traxtopel 2009-05-25 14:58:14 UTC
anaconda-11.5.0.54-1 & pykickstart-1.54-1.

Installing from a liveusb stick which was created from a livecd iso.
LiveCD was created with ext3.

When I run "liveinst" to install.

I select "replace existing Linux system" or "Use entire drive".
In both cases the following error occurs.

"The following errors occurred with your partitioning:

Your / partition does not match the the live image you are installing from.  It
must be formatted as ext3.

This can happen if there is not enough space on your hard drive(s) for the
installation. 

Press 'OK' to choose a different partitioning option."


"Use entire drive" should just nuke everything right?

Comment 1 Jeremy Katz 2009-05-26 14:05:25 UTC
It nukes everything, but autopartitioning doesn't take into account the fs type of the live image that's being installed and is always defaulting to ext4.  So if you build an ext3 live image, that causes problems.

I've pushed a fix for this to master (bbf767d27d7032d1afdd0ba05ad1897e3b5cb56c) although we're still trying to decide if we're going to include it in F12 or not given how late in the game this is.

Comment 2 Traxtopel 2009-05-26 14:29:40 UTC
Thanks for the fix, would love it if you can get it in F11, I hope you mean F11 & not F12?

Comment 3 Traxtopel 2009-05-26 16:13:45 UTC
Ok I see -55 will test.


Note You need to log in before you can comment on or make changes to this bug.