Bug 751587 - Install with software raid does not boot (with /boot on an MD volume)
Summary: Install with software raid does not boot (with /boot on an MD volume)
Keywords:
Status: CLOSED DUPLICATE of bug 750794
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-06 00:25 UTC by Gregory Maxwell
Modified: 2011-11-08 01:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-08 01:19:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gregory Maxwell 2011-11-06 00:25:06 UTC
Description of problem:

Installing F16 (RC5) x86_64 from USB onto a system with two SATA disk, configured several partition, and raid devices for each partition. 

When install completed after reboot I was greeted by No such device <uuid> then the grub rescue prompt.  And ls (hd0,0) etc. just gives me no such partition. I didn't know what more I could troubleshoot from there.

This is the same setup I've used on many F12/F13/F14 systems (I skipped F15)

I tried several times with no luck.

But #fedora-qa was helpful enough to show me the test case for SW raid installs: http://fedoraproject.org/wiki/QA:Testcase_Partitioning_On_Software_RAID

It appears that it directs the user to make a non-raid /boot.  Thats pretty nuts: if my system dies and I lose boot I won't be able to boot!  Makes the raid kinda pointless (okay, it might reduce data loss, but thats what backups are for).

So I really hope fedora hasn't dropped support for this, but at least if it has then the installer shouldn't let you try to configure it!

After switching to a non-raid /boot it worked fine.

Comment 1 Brian Lane 2011-11-08 01:19:33 UTC

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


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