Hi, I have been trying for a good few days now to try and boot a fully raided debian system with Lilo and a custom compiled kernel. The file system does not have a separate /boot partion. Lilo's configuration file has boot= and root= specified as /dev/md0. The custom compiled kernel has md and raid1 modules statically built, along with ext3, cramfs and associated modules. There is also an initrd. I have experienced various issues but now I have a system where , if I boot off /dev/hdb1 (hda and hdc are in the raid) I can succesfully install lilo with: mount -text3 /dev/md0 /mnt lilo -r /mnt No errors appear and the system appears to boot normally until it attempts to mount the root. At which point it errors and stops with an "attempt to kill init" message. Can anyone give me any pointers? I have tried not to include too much detail here so if you want pastes of any configuration files etc. just shout. Using grub I can get a system to boot fine however when issuing this style of command sequence: root(hd0,0) kernel /boot/vmlinuz-2.4.20 root=/dev/md0 initrd /boot/initrd.img-2.4.20 boot I get an identical error message to lilo. Have I missed something in initrd, I have done nothing fancy with it. Your's banging head against wall and giving up on raided root. Paul - 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
