Bug 7513 - Make Raid Device button doesn't appear after fdisk (expert install selected)
Make Raid Device button doesn't appear after fdisk (expert install selected)
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-12-02 12:06 EST by Mark J. Watson
Modified: 2015-01-07 18:39 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-09 09:35:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mark J. Watson 1999-12-02 12:06:25 EST
I have two internal SCSI 18.1G 10,000RPM drives that I wanted to create a
software stripe set across.

/boot 23M Raid 1 (sda & sdb)
/ 17.3G Raid 0 (sda & sdb)
swap Raid 0 (sda & sdb)

When I used disk druid it placed the /boot partition after the / partition
which was beyond the 1024 cyl so it didn't boot. I used fdisk to create the
raid partitions manually under an expert install. After creating the
partitions and pushing the next button the form that was presented didn't
have a MAKE RAID DEVICE BUTTON. I had to hit the reset button and do a
custom install and use the partitions that I created with the expert
install to make the appropriate raid devices.
Comment 1 Jay Turner 1999-12-02 12:09:59 EST
Yes, we are aware of this problem and will be fixing it up in the next release.
There are several issues with the way that the RAID module dropped into the
existing Disk Druid code.  In addition, we should be adding TUI support for the
creation of RAID partitions.
Comment 2 Jay Turner 2000-02-09 09:35:59 EST
This is fixed in the latest cut of the installer.

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