Bug 59833 - Can't create RAID device in Disk Druid
Summary: Can't create RAID device in Disk Druid
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i686 Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-02-13 19:15 UTC by Alexandre Oliva
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-02-20 22:59:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Alexandre Oliva 2002-02-13 19:15:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204

Description of problem:
I have two disks, each with part of a RAID0 device.  I'd like to try make this
partition available to the installed system from within the installer, but I
couldn't do it with Disk Druid.

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

How reproducible:

Steps to Reproduce:
1.Boot installer in `text' mode.
2.Verify that /dev/hda8 and /dev/hdc1 are existing Software R[aid] partitions
3.Choose RAID to create a RAID device out of them
4.Leave the defaults (FS type ext3, RAID level 0, RAID members hda8 and hdc1, 0
spares), and either deselect Format partition or leave it selected
5.Choose Ok

Actual Results:  A window pops up that says `The mount point is invalid.  Mount
points must start with '/' and cannot end with `/', and must contain printable

Expected Results:  It should have left me create the RAID device without
formatting it.  In fact, it should either not require a mount point for a RAID
device, or allow me to enter one.  The `Make RAID Device' window has `<Not
Applicable>' as the mount point, so I can't do that.

Additional info:

Comment 1 Alexandre Oliva 2002-03-10 12:15:11 UTC
Fixed in beta2.

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