Bug 80538 – Better error message with raid device

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 80538 - Better error message with raid device

Summary:	Better error message with raid device

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	9
Hardware:	i386 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:	Mike McLean
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-12-27 14:38 EST by Féliciano Matias
Modified:	2007-03-26 23:59 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-05-06 15:23:29 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Féliciano Matias 2002-12-27 14:38:43 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
If i select a raid0 device (software) for the root file system in Disk Druid and
/boot is not specified, i get the following message :
- "bootable partitions can only be on RAID1 device".

I think the error message should indicate to use of /boot partition if the user
want a raid0 partition for the root file system.

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


How reproducible:
Always

Steps to Reproduce:
select a raid0 device (software) for the root file system in Disk Druid with
/boot partition not specified.

Comment 1 Michael Fulbright 2003-01-02 18:06:03 EST

Thank you for the suggestion

Comment 2 Féliciano Matias 2004-05-06 15:23:29 EDT

Fixed in FC1.

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