Hi Lucas! Lucas Barbuto schrieb:
I think your problem is the following:NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. EXT3-fs: unable to read superblock EXT2-fs: unable to read superblock iofs_read_super: bread failed, dev=09:01, iso_blknum=16, block=32 XFS: bad magic number XFS: SB validate failed Kernel panic: VFS: Unable to mount root fs on 09:01 -- When trying to mount the root file system. I don't get it. I can mount the RAID partitions under /mnt no problems, I can boot off the RAID device /dev/md1, I just can't mount /dev/md2 as my root file system. Can anyone shed some light on this for me? What do I need to do? I have experimented with the LiLo setup and found that the system will boot up as expected with /dev/hde2 (or /dev/hdg2) as the root file system... why doesn't it like /dev/md2? Thanks in advance.
The kernel booting from a /boot md device doesn´t really boot off /dev/md1 but off one of the bootblocks of /dev/hde and /dev/hdg (which is perfectly good). The kernel doesn´t need /dev/md1 (=/boot) to boot, but only one of the bootblocks to find the kernel image, which is possible on both hde and hdg. The kernel panic occurs as soon as the kernel wants to mount the / filesystem the first time. The reason for this is that at that point, the raid devices (i.e. at least /dev/md2, the others can be assembled later) are not assembled yet.
You have two options: The older one is to make the underlying partitions of /dev/md1 (you didn´t give their name) autodetectable (change partition type to fd).
The newer option is to tell the kernel at boot time how to assemble the needed devices, which you do by inserting the following into the "image" section of your booting kernel in /etc/lilo.conf:
append = "md=2,/dev/hde3,/dev/hdg3"
Change the partitions to those that build up /dev/md2.
The kernel then can assemble its raid, since you compiled at least raid1 into it. You migth be able to use raid in a module at boot time if you load the module through an initial ramdisk (initrd), something Debian usually does not, but SuSE seems to (if yet very badly documented).
By the way: The most importatnt thing missing in your mail is /etc/raidtab or /etc/mdadm/mdadm.conf.
HTH, Norman Schmidt.
--
--
Norman Schmidt Institut für Physikal. u. Theoret. Chemie
cand. chem. Friedrich-Alexander-Universitaet
schmidt@naa.net Erlangen-Nuernberg
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
