Find the answer to your Linux question:
Results 1 to 8 of 8
hi every one , Wondering if any of you experienced this During "Centos5.6" Boot .. ! 1)NOT USING MMCONFIG 2)insmod Error inserting `/lib/raid456.ko` -1 File Exist Dell PowerEdge T110 with ...
  1. #1
    Just Joined!
    Join Date
    May 2011
    Posts
    13

    Exclamation insmod Error inserting `/lib/raid456.ko` -1 File Exist

    hi every one ,
    Wondering if any of you experienced this During "Centos5.6" Boot .. !

    1)NOT USING MMCONFIG
    2)insmod Error inserting `/lib/raid456.ko` -1 File Exist

    Dell PowerEdge T110 with 4sata Controllers with Centos2.6.18-238.9.1.el5xen installed .


    Code:
    /boot on /dev/md0
    /  on   /dev/md1
    Regards

  2. #2
    Just Joined!
    Join Date
    Jun 2004
    Location
    Halesowen, West Midlands, UK
    Posts
    71
    That usually means that the module is loaded.Have you checked with "lsmod|grep raid456"?

  3. #3
    Just Joined!
    Join Date
    May 2011
    Posts
    13
    hello Siddly ,
    yes my friend i`ve checked it ..
    Code:
    lsmod | grep raid456
    
    raid456               151137  1 
    xor                    39377  1 raid456
    i found a thread mentioning the issue
    https : // bugzilla.redhat.com/show_bug.cgi?id=512892
    but still cant figure how to eliminate it "specifically rebuilding the initrd"
    Thanks Siddly..

  4. #4
    Linux Newbie
    Join Date
    Dec 2010
    Posts
    146
    Well, that's the QA of Red Hat.

  5. #5
    Just Joined!
    Join Date
    Jun 2004
    Location
    Halesowen, West Midlands, UK
    Posts
    71
    Quote Originally Posted by Saed View Post
    hello Siddly ,
    yes my friend i`ve checked it ..
    Code:
    lsmod | grep raid456
    
    raid456               151137  1 
    xor                    39377  1 raid456
    i found a thread mentioning the issue
    https : // bugzilla.redhat.com/show_bug.cgi?id=512892
    but still cant figure how to eliminate it "specifically rebuilding the initrd"
    Thanks Siddly..
    The URL said the bug couldn't be found, but I can't see your problem.
    It's automatically loading the module as I thought. If that's not the module you want, i.e you have built an updated module you want to use instead, replace the module of the same name in /lib/modules/`uname -r`/kernel/drivers/scsi with your own and run "depmod -a", then reboot.

  6. #6
    Just Joined!
    Join Date
    May 2011
    Posts
    13
    i`v checked the /etc/sysconfig/modules/ and tried to remove is with the help of this URL
    http: //docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Persistent_Module_Loading.html
    but i`m not sure where to place the code
    Code:
    #!/bin/sh
    if [ ! -c /dev/input/uinput ] ; then
            exec /sbin/modprobe uinput >/dev/null 2>&1
    fi
    replace the module of the same name in /lib/modules/`uname -r`/kernel/drivers/scsi with your own and run "depmod -a", then reboot.
    i`d like to know how to proceed with this approach , can u explain a little bit more plz
    Thanks my friend

  7. #7
    Just Joined!
    Join Date
    Jun 2004
    Location
    Halesowen, West Midlands, UK
    Posts
    71
    Quote Originally Posted by Saed View Post
    i`v checked the /etc/sysconfig/modules/ and tried to remove is with the help of this URL
    http: //docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Persistent_Module_Loading.html
    but i`m not sure where to place the code
    Code:
    #!/bin/sh
    if [ ! -c /dev/input/uinput ] ; then
            exec /sbin/modprobe uinput >/dev/null 2>&1
    fi


    i`d like to know how to proceed with this approach , can u explain a little bit more plz
    Thanks my friend
    Give me some more information about what you are trying to do. From my reading of the situation you described:-
    The existing raid456 module is being loaded, but you don't want that.
    Instead you have a different or updated raid45 module you want to use instead.

    If the above is true the existing raid456.ko module exists in /lib/modules/`uname -r`/kernel/drivers/scsi
    You can list it, e.g if your kernel is 2.6.39, "uname -r" (without the "quotes) will return the kernel name.
    slipstream:~ # uname -r
    3.0.0-rc2-smp
    slipstream:~ # ls /lib/modules/`uname -r`
    build kernel misc modules.alias modules.alias.bin modules.builtin modules.builtin.bin modules.dep modules.dep.bin modules.devname modules.order modules.softdep modules.symbols modules.symbols.bin source
    slipstream:~ # ls /lib/modules/3.0.0-rc2-smp
    build kernel misc modules.alias modules.alias.bin modules.builtin modules.builtin.bin modules.dep modules.dep.bin modules.devname modules.order modules.softdep modules.symbols modules.symbols.bin source
    slipstream:~ #
    As you can see both the above commands return the same information.
    Somewhere under /lib/modules/`uname -r`/kernel/drivers there is a raid456.ko module that you need to replace with the new raid45.ko module.
    After replacing the module, "depmod -a" will check and enable the module so that when you reboot your new module will be the one used.
    There is another way but what I described above is the simplest.

  8. #8
    Just Joined!
    Join Date
    May 2011
    Posts
    13
    Hello Siddly ,
    sorry for being too late , Exams stuff

    From my reading of the situation you described:-
    The existing raid456 module is being loaded, but you don't want that.
    Instead you have a different or updated raid45 module you want to use instead.
    well , its by default loads the modules required to read the Disk-array to access the drives , as it reads 2 Raid arrays
    /dev/md0 , /dev/md1, it adds the module twice ..
    after searching the web , i found that its a known bug for the
    mkinitrd-5.1.19.6-68.el5_6.1 version ,
    a normal fix of this bug is being told that the mkinitrd should be recreated with
    Code:
    mkinitrd -v -f /boot/initrd.$(uname -r).img $(uname -r)
    i tried it but in vain .
    a friend of mine , provided me with patch made for a work ground regarding this problem , which was
    updating the /sbin/mkinitrd with the following lines
    Code:
     #only need to add each module once
    case " $(eval echo \${$modlist}) " in
            *" $modName "*)
                return ;;
            *)
                eval $modlist=\"\${$modlist} $modName\"
                ;;
        esac
    1)after making sure that the grub.conf file is also being updated with the exact kernel image being created with mkinitrd
    2) makin sure that the module dosn`t gets add twice
    the problem still persists
    Somewhere under /lib/modules/`uname -r`/kernel/drivers there is a raid456.ko module that you need to replace with the new raid45.ko module.
    this isn`t what i`m trying to do , although i`m not sure if it can resolve the problem.

    ive been discussing this problem on another forum , before i try to to post here in this decent site .
    if u`d like to have a look please see it on

    http : // unix.com/red-hat/160917-insmod-error-inserting-lib-raid456-ko-1-file-exist.html

    thanks My Friend I really do appreciate your help..

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...