Bug 57782 - Anaconda failure with RAID1 devices (kickstart)
Summary: Anaconda failure with RAID1 devices (kickstart)
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 7.2
Hardware: i386 Linux
low
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-12-22 15:42 UTC by Jos Vos
Modified: 2007-03-27 03:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-12-22 16:04:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Anaconda dump file (43.58 KB, text/plain)
2001-12-22 15:43 UTC, Jos Vos
no flags Details
Diff output between non-working (left) and working (right) ks.cfg file (2.23 KB, patch)
2001-12-22 15:45 UTC, Jos Vos
no flags Details | Diff

Description Jos Vos 2001-12-22 15:42:35 UTC
Description of Problem:
Anaconda fails with an error when using RAID1 partitions.

How Reproducible:
With attached ks.cfg file on an i185E-based Supermicro system. When normal
partitions i.s.o. RAID1 devices are specified, the install works ok.

I will attach the Anaconda dump file and the diff output of a working
(non-RAID1) ks.cfg file and a non-working file.

Comment 1 Jos Vos 2001-12-22 15:43:51 UTC
Created attachment 41247 [details]
Anaconda dump file

Comment 2 Jos Vos 2001-12-22 15:45:50 UTC
Created attachment 41248 [details]
Diff output between non-working (left) and working (right) ks.cfg file

Comment 3 Jos Vos 2001-12-22 16:04:13 UTC
I am ashamed of myself... this system has only one disk... (I was installing a
couple of different systems, some with RAID1, which explains a bit...).  Still,
the question is whether there can't be a more elegant error message explaining
this.


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