Bug 110371 - bad raidtab entry: /dev/mdmd0
bad raidtab entry: /dev/mdmd0
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-11-18 16:50 EST by Mike McLean
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-18 17:34:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike McLean 2003-11-18 16:50:20 EST
* Pensacola-re1118.QU3.1
* kickstart install w/ raid

The installed system failed to boot complaining about a lack of raid
device in /dev.  Poking around at the repair filesystem prompt, I
discovered that /etc/raidtab referenced /dev/mdmd0 instead of /dev/md0

Here is the partitioning section of the kickstart:

clearpart --all
part / --size 2048 --grow
part /boot --size 200
part swap --recommended
part raid.01 --size 2048 --grow
part raid.02 --size 2048 --grow
raid /usr --level 0 --device md0 raid.01 raid.02
Comment 1 Jeremy Katz 2003-11-18 17:07:27 EST
2.1 doesn't support --device md0 -- you must do --device 0 to get
explicit devices.
Comment 2 Mike McLean 2003-11-18 17:26:50 EST
according to:
(This is the link you get when you select the 2.1 AS Customization
Guide from https://www.redhat.com/docs/manuals/enterprise/)

'--device md0' should work

Even the 7.1 (and 7.3) customization guide(s) list this as correct syntax.

The installer does seem to handle it fine for the most part, only the
entry in raidtab is broken.
Comment 4 Jeremy Katz 2003-11-18 17:34:11 EST
7.2 didn't support --device at all (the fact that the docs say that it
does to the contrary).  I added the --device n hack for IS in the
initial spin of 2.1 but then improved on it for 7.3. 

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