Bug 888099 - GRUB and RAID sidebar information incorrect
Summary: GRUB and RAID sidebar information incorrect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: install-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Bokoc
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-18 01:01 UTC by Chris Murphy
Modified: 2013-07-29 16:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-29 16:58:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Chris Murphy 2012-12-18 01:01:57 UTC
Description of problem:
Sidebar says RAID cannot construct (assemble) software RAID.


Version-Release number of selected component (if applicable):
Fedora 17/18 (GRUB2)



Steps to Reproduce:
1. http://docs.fedoraproject.org/en-US/Fedora/17/html/Installation_Guide/s1-grub-installing.html


Actual results:
The sidebar titled "IMPORTANT - GRUB and RAID" 


Expected results:
I'd just remove this sidebar, as GRUB can do this, even if it's not clear if anaconda will support boot on md RAID. Presently I can produce a working installation from anaconda for a boot and root on RAID 0, ext4. Outside of anaconda, GRUB has no problem dealing with boot on btrfs raid0, raid1, or raid10.


Additional info:

Comment 1 Chris Murphy 2013-01-03 21:43:46 UTC
Also in draft documentation:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Installation_Guide/s1-grub-installing.html

I can report with F18TC4 that anaconda will create a bootable single mount point (Root), which includes /boot, on md RAID 0, 1, 4, 5, 6. And is bootable by GRUB2.

Comment 2 Jack Reed 2013-01-11 02:37:29 UTC
Thanks for reporting this, Chris. I've removed the admonition.

You can view the commit here: http://git.fedorahosted.org/cgit/docs/install-guide.git/commit/?id=d9e0aa7dfb72202595f250b6b64c3d8e764dcd6d


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