SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In the earlier versions of kernel 2.4 you could enableboot support and auto detect support under raid. This options is not there any more. Is it still possible because I am doing the exact same setup for a software raid system as I did with Slackware 8 and kernel 2.4.5 and are now using Slackware 9 and it seems the md devices are not detected as with my slackware 8 system.
I recall the kernel option to disable and enable the autodetect feature. But I thought it was on the latest 2.2.x kernels. The 2.4.x kernels I thought always detected md devices if the md support was builtin to the kernel. But my memory could be faulty. If you are starting from scratch, did you remember to set the partition type correctly to raid autodetect? The default bare.i kernel for Slack 9 does have md support included. I do not know about the other kernels though. If you have built custom kernel then make sure the md support for your setup is included in the kernel and it is actually booting.
Once you have actually built the raid device, it should appear in the /proc/mdstat listing upon booting.
I haven't tried that as yet. I still like the comfort of knowing that I have regular maintenance partition to boot from and then setup my lilo.conf to boot the same kernel but with a different root. So I create a 2 GByte regular partition for a maintenance platform. But when I was reading in the recent lilo docs, if I recall, it should support booting the md device. But your error messages are lilo related and not kernel related because the kernel hasn't booted yet. That is what the message is indicating that the lilo boot loader is not loading. You might want to review the lilo docs to see what you are suppose to set the lilo.conf to write to. It may require the MBR of the first bootable hard disk to load the kernel. Once the kernel is loaded it will detect the md device, then the root device should of been passed to the kernel for it to initiate the init system and continue the boot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.