> I just overflew the link you gave. There the partition type "fd" > approach is used, which needs either compiled-in raid functionality or > raid as a module in the initial ramdisk (which is both at least fo Woody > not the standard case; I built a bootable cd with a kernel with > compiled-in raid support so that I could install directly onto a raid). I have raid as a module in the initrd. > If you want the disks to be started by the mdadm call in that script, > then the devices shouldn´t be assembled (or even tried to) by > autodetection before. Try changing the type back to 83/82 or whatever fs > you use. It won't change anything (I had 83 before I noticed I forgot this part), but I understand what you're saying. > What exactly does lead you to the thought that /dev/md0 and /dev/md1 do > not exist? Are the actual entries in /dev issing? If so, why are they > missing again after you made them wit MAKEDEV? When I get the maintenance root prompt, I see that /dev/md0 and /dev/md1 are missing from /dev. When I reboot, they have disappeared again. Although nothing appears in mnttab, I suspect my system may be using devfs: willow# df -k /dev Filesystem 1K-blocks Used Available Use% Mounted on none 5120 2944 2176 58% /dev At boot time, no entries are created in this devfs for /dev/md0 and /dev/md1. How can I create them? I thought loading the md module from initrd would be enough but it looks like it isn't. Sam - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
