Bug 231453
Summary: | kickstart raid install fails with valueerror: md2 is already in the mdList | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Dave Botsch <botsch> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-28 18:53:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dave Botsch
2007-03-08 14:01:48 UTC
The kickstart seems to be doing its own numbering scheme and somehow renumbering stuff it has already numbered or that I have numbered, with respect to the md numbers. For example, if I specify --device=mdx in each of the raid kickstart commands, I'll then end up w. a system that doesn't install and may end up with /dev/md4's partititions (which are /dev/md4 according to /proc/mdstat) attempting to be auto numbered after the fact as /dev/md1 ... clearly this can't work. I seem to have found the solution... before attempting to reinstall w. kickstart, boot up into rescue mode and use fdisk to clear out all partitions. So, the clearpart command in the kickstart file seems to not be doing the right thing when software raid partitions are already present on the disk. |