Bug 129608 - Install to RAID1 (Mirror) fails if mirror is not synced before reboot
Summary: Install to RAID1 (Mirror) fails if mirror is not synced before reboot
Keywords:
Status: CLOSED DUPLICATE of bug 116685
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-10 20:47 UTC by Simon Jones
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:05:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Simon Jones 2004-08-10 20:47:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040626 Firefox/0.9.1

Description of problem:
When installing FC3T1 and using software raid1, if the installer
finishes before the mirror sync's, then when the reboot occurs the
system will fail to boot.



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Start install of FC3 T1, create a big software raid 1 array
2.let installer install a typical 2.2G install
3.let the installer reboot as soon as installed
    

Actual Results:  System refuses to boot

Expected Results:  System would boot normally.

Additional info:

Can anaconda be modified to know when the raid is sync'd and then
allow a reboot, i.e at the end of the install put a notice on screen
showing the raid is syncing.. please wait...

Work around is to look at the log as it installs and wait for the
mirror to be synced then reboot.

Comment 1 Jeremy Katz 2004-08-10 21:15:49 UTC
This is a kernel bug.  The kernel shouldn't mark an array as finished
syncing on boot if it's not actually.

*** This bug has been marked as a duplicate of 116685 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:05:04 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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