What was going on here was that the minor number for md0 was not 0. That
allowed everything but booting with md0 as the root fs to work.
Specifying the correct major:minor numeric pair as kernel boot arguments
("root=") did not work, which is probably a real bug somewhere. In any
case, I recreated the /dev/md0 node as 09:00 as the kernel expected, ran
mkraid with a valid raidtab and the "--force" switch, and all of the data
reappeared and md0 boots correctly as the root fs.
Keep in mind that this was a clean, new install without any important data
on it, so I felt free to experiment.
-- Mike
On Sat, 25 Mar 2000, Mike Bilow wrote:
> Unfortunately, the boot floppy fails out with a kernel panic about being
> unable to mount the root filesystem. The ssyslinux.cfg file does
> correctly specify "root=/dev/md0" and the VFS message reports that it
> cannot mount 09:00 because there is no valid superblock. The kernel
> messages up to that point clearly indicated that RAID-1 support was
> running and that the mirror was being managed. If I boot using the
> install set (with the same customer kernel), /dev/md0 can be mounted and
> used. What's going on here?
