Re: kernel upgrade: mkinitrd: module raid1 not found

From: Clement (clement_at_ans.com.au)
Date: 07/11/04

  • Next message: BetSpace: "dear webmaster" 
    Date: Sun, 11 Jul 2004 23:28:42 +1000
To: debian-user@lists.debian.org

    In case you are still interested in this topic, I have just spent some
    hours on it and found the followings:

    When installing either the stock 2.6.6 kernel-image or tailor compiled
    2.6.6 kernel-image, these error messages appeared but seems to be
    harmless (pls correct me if not):

    cpio: /etc/modprobe.conf: No such file or directory
    cpio: /lib/modules/modprobe.conf: No such file or directory

    With the RAID support compiled in, the error, FATAL: Module raid1 not
    found, sounds a bug to me. It was suppressed by changing, ROOT=probe,
    to ROOT=, in /etc/mkinitrd/mkinitrd.conf.

    My reason to tailor compile the 2.6.6 kernel is because the stock
    kernel-image does not recognize my pair of mirrored ATA disks. The
    stock kernel reported ide_??? (sorry I did not jot it down) and
    ide_detect module not found. I fixed this by compiling the kernel with
    built-in IDE support. I wish the stock kernel can get this fixed some time.

    Regards,
    Clement

    > Hi Justin,
    >
    > Thanks for your help, I got it working now, but it is weird. This is
    what I
    > read at http://www.wlug.org.nz/SoftwareRaid:
    >
    > "The most recent versions (eg LinuxKernel2.6) of the Debian kernel-image
    > packages build a new initrd image upon installation. They should
    > automatically notice if the root device is /dev/md* and arrange for the
    > appropriate modules to be present in the initrd image and loaded
    > appropriately. So if the software raid array is actually your root
    > filesystem when you do the kernel install, everything should just work."
    >
    > and probably that's the problem: since I compiled raid support into my
    > kernel, it didn't have the raid modules and mkinitrd is being too smart,
    > trying to add the raid modules anyway.
    > Sounds like a bug to me.
    >
    > But this is good news too, since root-on-raid now works with raid modules
    > and I can now use a stock kernel again. Problem solved!
    >
    > Thanks
    > Bob
    >
    >
    > "Justin Guerin" <jguerin@cso.atmel.com> wrote in message
    > news:cistron.200406010906.13009.jguerin@cso.atmel.com...
    > > Hi Bob,
    > > You are correct: a raid1 module is not required since you compiled
    it into
    > > the kernel. Actually, because you compiled it into the kernel, no
    module
    > > was built, which is why it can't be found. To fix this error the most
    > > simple way, re-configure your kernel to build raid1 as a module, then
    > > compile again.
    > > On the other hand, since you're building your own kernel, why not just
    > > build in all the components you know you'll need at boot time, and
    build
    > > the rest (ones that you only think you might need) as modules.
    That way,
    > > you won't even have to use an initial ram disk.
    > > But back to fixing your error without rebuilding your kernel: where is
    > > mkinitrd's confdir? It's supposed to be /etc/mkinitrd, and if it's
    trying
    > > to put the raid1 module into the initial ram disk, then it should be in
    > the
    > > config files somewhere, but your grep doesn't seem to have found
    it. It's
    > > possible it's in /usr or somewhere else. If you find it, check to see
    > that
    > > that's not the culprit.
    > > Let the list know what route you decide to take and how it works.
    > > Justin Guerin
    > >
    > >
    > > --
    > > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
    > > with a subject of "unsubscribe". Trouble? Contact
    > listmaster@lists.debian.org 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: BetSpace: "dear webmaster"