From: Dave Jones <davej@codemonkey.org.uk>
Date: Thu, Jan 30, 2003 at 01:00:41PM +0000
> On Thu, Jan 30, 2003 at 01:42:24PM +0100, Jurriaan wrote:
>
> > umount /dev/md0
> > umount /dev/md1
> > raidstop /dev/md0
> > raidstop /dev/md1
> > dd if=/dev/zero of=/dev/hdi bs=512 count=1
> > dd if=/dev/zero of=/dev/hdk bs=512 count=1
> > fdisk /dev/hdi < /root/fdisk.in
> > fdisk /dev/hdk < /root/fdisk.in
> > mkraid --really-force /dev/md0
> > mkraid --really-force /dev/md1
>
It turned out the kernel I did this with was compiled like this:
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=m
# CONFIG_MD_RAID1 is not set
CONFIG_MD_RAID5=m
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set
# CONFIG_BLK_DEV_DM is not set
and those modules weren't loaded. After recompiling the kernel with all
raid-options on and in the kernel, it works.
It's strange, however, that you can create a raid partition without raid
support until you reboot.
You'd expect to have 'mkraid' say:
'no RAID support in kernel - aborting'
or something like that.
Kind regards,
Jurriaan
--
"Witness the strategy of silence - while the intended victims unravel each
other in pointless, divisive discourse. Oh yes, I have learned much from
Tremorlor."
Steven Erikson - Deadhouse Gates
GNU/Linux 2.4.21-pre3-ac5 SMP/ReiserFS 1x2824 bogomips load av: 0.09 0.13 0.07
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jan 31 2003 - 22:00:24 EST