KS won't partition drives

[Blair Lowe]

I went a bit furthur with this:

After looking over the Software-RAID-HOWTO I expanded the %pre script to
create the raid drives as follows:

This occurs after a successful fdisk partitioning of /dev/hda and
/dev/hdb:


# Make the raid nodes in the kickstart boot environment
mknod /dev/md0 b 9 0
mknod /dev/md1 b 9 1
mknod /dev/md2 b 9 2
mknod /dev/md3 b 9 3
mknod /dev/md4 b 9 4
mknod /dev/md5 b 9 5
mknod /dev/md6 b 9 6
mknod /dev/md7 b 9 7
mknod /dev/md8 b 9 8
mknod /dev/md9 b 9 9


# now define the devices and create them with mkraid:

#hda1 hdb1
#raid /boot --level=1 --device=md0 --fstype=ext3 raid.01 raid.07
cat <<EOF > /etc/raidtab
raiddev             /dev/md0
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda1
    raid-disk     0
    device          /dev/hdb1
    raid-disk     1
#hda2 hdb2
#raid /usr --level=1 --device=md1 --fstype=ext3 raid.02 raid.08 
raiddev             /dev/md1
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda2
    raid-disk     0
    device          /dev/hdb2
    raid-disk     1
#hda3 hdb3
#raid /var --level=1 --device=md2 --fstype=ext3 raid.03 raid.09 
raiddev             /dev/md2
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda3
    raid-disk     0
    device          /dev/hdb3
    raid-disk     1
#hda5 hdb5
#raid --level=1 --device=md3 --fstype=swap raid.04 raid.10 
raiddev             /dev/md3
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda5
    raid-disk     0
    device          /dev/hdb5
    raid-disk     1
#hda6 hdb6
#raid / --level=1 --device=md4 --fstype=ext3 raid.05 raid.11 
raiddev             /dev/md4
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda6
    raid-disk     0
    device          /dev/hdb6
    raid-disk     1
#hda7 hdb7
#raid /home --level=1 --device=md5 --fstype=ext3 raid.06 raid.12
raiddev             /dev/md5
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda7
    raid-disk     0
    device          /dev/hdb7
    raid-disk     1
EOF

# make the raid disks (and DESTROY old data!)

mkraid --really-force /dev/md0
mkraid --really-force /dev/md1
mkraid --really-force /dev/md2
mkraid --really-force /dev/md3
mkraid --really-force /dev/md4
mkraid --really-force /dev/md5

After each mkraid command: an error message says that "mkraid aborted"

/proc/mdstat shows each md device as inactive, and only shows the hda
side of things, but when the command was run, it showed both sides of
the raid.

So I tried raidstart /dev/md0, then I get an anaconda traceback that
indicates that the log file is missing. I think that raidstart is for
RAID level 5, and we are doing level 1.

Why does mkraid abort?

Blair.