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.
During all my time with Slackware 11 I've build my raids during install using the "good" old raidtools. It's worked like a charm.
Now with Slackware 12 I no longer have raidtools available during install, so I'm forced to use mdadm instead. So far I like it quite well. It's a heck of a lot easier to get those raids up and running without having to write a lot of stuff in /etc/raidtab.
But!
How do I go about managing my raids now? I've read that mdadm doesn't really need a .conf file, but what happens then if a disk fails and I need to rebuild?
Any and all mdadm tricks are more than welcome. What's considered good practice when maintaining raids using mdadm.
And I have of course added the appropriate information to lilo.conf.
It starts well with the classic lilo menu, where the new generic kernel shows up. I select it, and booting begins. Then after a while it reaches a point where this happens:
mount: Mounting /dev/md0 on /mnt failed
ERROR: No /sbin/init found on rootdev
And then it just sits there.
I never had this issue with Slackware 11 using raidtools and running the exact same raidsetup. I must be doing something wrong, I just can figure out what. It looks as if /dev/md0 doesn't exist during boot, and seeing as / is mounted on /dev/md0, that would indeed be a problem.
But this support for software-RAID should really be added to the Slackware mkinitrd package in the next slackware-current round.
Eric
My german is, to put it mildly, pretty bad, but thank you for the find!
As far as I can see, it looks as if the problem is due to mdadm? /dev/md0 simply does not exist at this point in time, because it hasn't been assembled by mdadm yet?
How this worked with raidtools is beyond me.
I do though agree with you: This REALLY should be fixed as fast as possible.
OK after conferring with Patrick, PiterPUNK and Stuart Winter, this is the verdict:
Software RAID will work out of the box in Slackware (no initrd needed) if the following conditions are met:
- The raid drivers are compiled into the kernel (no modules!)
- The partition types are set to "Linux RAID Autodetect" (type 'fd')
Note that with RAID drivers as modules, the RAID autodetection by the kernel will fail.
OK after conferring with Patrick, PiterPUNK and Stuart Winter, this is the verdict:
Software RAID will work out of the box in Slackware (no initrd needed) if the following conditions are met:
- The raid drivers are compiled into the kernel (no modules!)
- The partition types are set to "Linux RAID Autodetect" (type 'fd')
Note that with RAID drivers as modules, the RAID autodetection by the kernel will fail.
Cheers, Eric
You people simply rock!
Slackware and its community is miles above and beyond what most other distros offer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.