Bug 412111 - Install from Live Image fails with ext2 live images
Summary: Install from Live Image fails with ext2 live images
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 8
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL: http://code.google.com/p/eeedora
Whiteboard:
Depends On:
Blocks: F9Blocker
TreeView+ depends on / blocked
 
Reported: 2007-12-05 14:34 UTC by Martin Andrews
Modified: 2008-02-07 21:54 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-02-07 21:45:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Anaconda Exception thrown (40.18 KB, text/plain)
2007-12-05 14:34 UTC, Martin Andrews
no flags Details

Description Martin Andrews 2007-12-05 14:34:58 UTC
Description of problem:
I have created a new Fedora spin 'EeeDora' specifically for the EeePC.  The Live
Image boots fine (very fine).  Live install works in manual mode, but with a
kickstart file (I'd like to make this completely automatic) Anaconda goes
through the installation (writing packages=100%), but gives an exception in the
last stages.  This leaves the machine in an unusable state (if booting without
the Live image)

Version-Release number of selected component (if applicable):
Fedora 8 + all updates

How reproducible: 
Every time - 

Steps to Reproduce:
1.  Run anaconda with live install, and kickstart file
2.  See disks partitioned, and packages written
3.  In finalizing step, Anaconda throws exception 
  
Actual results:
Bootable install

Expected results:
Grub does not load

Additional info:
Exception report from anaconda attached

Comment 1 Martin Andrews 2007-12-05 14:34:58 UTC
Created attachment 278371 [details]
Anaconda Exception thrown

Comment 2 Martin Andrews 2007-12-05 20:09:02 UTC
Of course I meant : 

Expected results:
Bootable install

Actual results:
Grub does not load

Sorry.

Comment 3 Jeremy Katz 2007-12-10 18:50:03 UTC
Actually, based on something that someone just filed... can you try manually
loading the ext2 module and see if that helps?

Comment 4 Martin Andrews 2007-12-12 22:08:34 UTC
I think we've got to the bottom of this on the mailing list.  The issue is that
livecd-creator (and mayflower) has the assumption that the rootfs img should be
ext3 (and called ext3fs.img).  

liveinst block copies the filesystem 8Mb at a time without checking whether the
partition fstypes are the same.  

This can be fixed 2 ways : (a) allow livecd-creator/mayflower to use ext2 images
(which is the route I took); and (b) fix liveinst to copy partitions
file-by-file if the partition fstypes don't match.


Comment 5 Jeremy Katz 2008-02-07 21:45:39 UTC
Fixed things up in git so that the creation works correctly as well as the
installation. 

Comment 6 Martin Andrews 2008-02-07 21:54:47 UTC
Thanks for the fix - I just realized that I didn't explain the reason this was
important : The EeePC has a Flash main drive, which has limited write-cycles :
and a journaling fs (eg: ext3) would tend to wear the drive out quicker than
something like ext2.

Thanks again 
Martin
:-)



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