Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 245454 - RAID partitions for /boot always both on /dev/sda
RAID partitions for /boot always both on /dev/sda
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-06-23 10:19 EDT by Rolf Fokkens
Modified: 2008-02-14 10:57 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-14 10:57:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rolf Fokkens 2007-06-23 10:19:52 EDT
Description of problem:
When installing F7, I cannot get /boot on a RAID1 device. After the raid device
is made (based on /dev/sda1 and /dev/sdb1) anaconda puts both partitions on
/dev/sda1 and /dev/sdb1. Useless

Version-Release number of selected component (if applicable):
Latest F7 dvd iso

How reproducible:
100% over here

Steps to Reproduce:
1. Use a PC with two SATA drives
2. Boot from the installation DVD
3. Modify the default partitioning in anaconda
4. Create a /dev/sda1 and /dev/sdb1, both RAID partitions
5. Create a RAID1 device for /boot based on the mentioned partitions
6. Experience a sense of surprise when noticing that the newly created RAID1
device is based on /dev/sda1 and /dev/sda2
Actual results:
Silly RAID partition based on one physical disk

Expected results:
Useful RAID partition based on separate phisical disks

Additional info:
Comment 1 Joel Andres Granados 2008-02-14 10:57:17 EST
Juste tested this issue and did not see anything buggy.  The partition /boot was
in sda1 and sdb1 like I specified.  If this issue continues with f8 or f9 please
reopen the bug.

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