Bug 412111

Summary: Install from Live Image fails with ext2 live images
Product: [Fedora] Fedora Reporter: Martin Andrews <bugzilla.redhat>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 8   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://code.google.com/p/eeedora
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-07 16:45:39 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 235706    
Description Flags
Anaconda Exception thrown none

Description Martin Andrews 2007-12-05 09:34:58 EST
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 09:34:58 EST
Created attachment 278371 [details]
Anaconda Exception thrown
Comment 2 Martin Andrews 2007-12-05 15:09:02 EST
Of course I meant : 

Expected results:
Bootable install

Actual results:
Grub does not load

Comment 3 Jeremy Katz 2007-12-10 13:50:03 EST
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 17:08:34 EST
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 16:45:39 EST
Fixed things up in git so that the creation works correctly as well as the
Comment 6 Martin Andrews 2008-02-07 16:54:47 EST
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