Bug 122804 - System unbootable when /boot is a RAID-1
Summary: System unbootable when /boot is a RAID-1
Keywords:
Status: CLOSED DUPLICATE of bug 114690
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-08 08:29 UTC by H. Peter Anvin
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-03-14 19:30:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description H. Peter Anvin 2004-05-08 08:29:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b)
Gecko/20040105

Description of problem:
Anaconda no longer has an option to install LILO rather than GRUB. 
This is completely disastrous when /boot is a RAID-1, which is
otherwise a highly desirable configuration, since it means any drive
can boot the system.

Anaconda will allow you to make /boot a RAID-1, and will offer to
install GRUB on it.  It produces a completely unusable GRUB
configuration which ends with dropping you into the level 2 GRUB shell.

As far as I can tell, there *is no way to make GRUB operate correctly
on a RAID-1 /boot*.

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

How reproducible:
Always

Steps to Reproduce:
1. Install a system with /boot on a RAID-1
    

Actual Results:  GRUB loads and drops you into the level 2 GRUB shell.

Expected Results:  System boots.

Additional info:

LILO handles this correctly, but there is no longer a way to install
LILO at install time.

Comment 1 Peter Jones 2005-03-14 19:30:48 UTC

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


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