Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
[solved] Removing multipath from F8/9 kernel to fix forced mapper/mpath0 devices
Greetings all. I have a home built desktop running on an ABIT IT7 Max2 MB.
This MB has the standard IDE controller capable of running 4 devices plus an additional HighPoint 473 ata133 raid controller capable of running 4 more.
Currently there is one 40G IDE drive and a CDROM on the original master/slave and two SATA 150 drives attached to the ata133 highpoint controller. (Weird config that a 133 device has a 150 option and sata ports but it does.)
In the BIOS the two drives are left in the unconfigured state. It only allows a JBOD selection if I select both drives to be JBOD'd together so I skipped that to allow them to be seen by the OS as individual drives. I booted into windows XP just to make sure the overall hardware was sane and everything works well with two 320G sata drives and the one 40G ide.
I Then installed F8 and F9 and the installer keeps seeing the two sata drives as a mpath01 device and trying to make them one single 320G device. Since they are going to be data only I decided to just install to the 40G drive and ignore the 320's for now. This seemed to work fine but after rebooting it basically fails with the following:
Uncompressing Linux... Ok, booting the kernel.
Red Hat nash version 6.0.19 starting
device-mapper: table: 253:0: multipath: error getting device
device-mapper: reload ioctl failed: Invalid argument
device-mapper: table ioctl failed: No such device or address
device-mapper: deps ioctl failed: No such device or address
and then it segfaults.
If I boot into rescue mode everything works fine and I see sda, sdb and sdc perfectly fine. The 320G drives are sda and sdb and the 40G drive with the os is sdc. I can even chroot my disk perfectly fine.
I want to see the individual disks so I am thinking that maybe if i can remove the dm_* components from the initrd file then maybe that will be a good workaround.
My problem is removing the modules to be able to run mkinitrd.
Anyone have any ideas or suggestions?
Last edited by Malachite; 09-28-2008 at 09:35 AM.
Reason: Solved and new title
Looks like I found my own answer finally. I will post it here in case someone else runs across this. Reading the man page for mkinitrd didn't give all the solutions. After just typing mkinitrd <enter> I found a new option that appears to be the one I needed. Basically my solution was mkinitrd --omit-dmraid.