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


 
Thread Tools Search this Thread
Operating Systems Linux Red Hat insmod Error inserting `/lib/raid456.ko` -1 File Exist
# 1  
Old 06-05-2011
Error 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  
Old 06-05-2011
See https://bugzilla.redhat.com/show_bug.cgi?id=512892 for more info and eventual fix Smilie

Rebuilding of the initrd may help.
# 3  
Old 06-06-2011
thanks click , straight to the Point Smilie

but still can`t figure it out Smilie "specifically how to rebuild the initrd"
i`m still new to linux world , almost my 6th month ...


# 4  
Old 06-06-2011
Yes, my bad for beeing so vain Smilie

To rebuild the inird you have to

Code:
# mkinitrd -o /boot/initrd.$(uname -r).img $(uname -r)

Check the new initrd with

Code:
# ls  -l /boot/initrd.$(uname -r).img

Then do
Code:
# cat /etc/grub.conf

and make sure that the the new initrd is there(it will be since you are not changing the version)

If that dosen`t help you should check /etc/sysconfig/modules/ for dublicate entrys for raid456.ko. If there is remove one of them as shown here

23.6. Persistent Module Loading

And rebuild the inird as shown above.

Be very careful with this, you can break things Smilie
# 5  
Old 06-07-2011
click , Sorry for being too late ..
Quote:
Yes, my bad for beeing so vain Smilie

at all brother , you did a great help .
- after backing up the /boot dir i did the following:-
Code:
 ls  -l /boot/initrd.$(uname -r).img
ls: /boot/initrd.2.6.18-238.9.1.el5xen.img: No such file or directory


tried ..
Code:
 ls /boot/ | grep -i initrd
                  May 25 08:19 initrd-2.6.18-238.el5xen.img
                  Jun  6 15:07 initrd-kernel_version.img
                  Jun  6 15:20 initrd-2.6.18-238.9.1.el5xen.img


then ..
[/code]
Code:
# mkinitrd -o /boot/initrd.$(uname -r).img $(uname -r)
usage: mkinitrd [--version] [--help] [-v] [-f] [--preload <module>]
       [--force-ide-probe] [--force-scsi-probe | --omit-scsi-modules]
       [--image-version] [--force-raid-probe | --omit-raid-modules]
       [--with=<module>] [--force-lvm-probe | --omit-lvm-modules]
       [--builtin=<module>] [--net-dev=<interface>] [--with-fips]
       [--without-usb] [--without-multipath] [--without-dmraid]
       [--fstab=<fstab>] [--nocompress] <initrd-image> <kernel-version>

       (ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15)


strange ? i think i missed somthing here !
i tried without the -o option
Code:
mkinitrd /boot/initrd.$(uname -r).img $(uname -r)
Modulefile is /etc/modprobe.conf

make sure its was successful ..
Code:
echo $?
0


Code:
 ls -a /boot/ | grep -i initrd
        May 25 08:19 initrd-2.6.18-238.el5xen.img
        Jun  6 15:07 initrd-kernel_version.img
        Jun  6 15:20 initrd-2.6.18-238.9.1.el5xen.img
        Jun  7 11:38 initrd.2.6.18-238.9.1.el5xen.img

checking the grub.conf file ...
Code:
cat /etc/grub.conf

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/lvm_raid/volroot
#          initrd /initrd-version.img
#boot=/dev/md0
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-238.9.1.el5xen)
    root (hd0,0)
    kernel /xen.gz-2.6.18-238.9.1.el5 crashkernel=320M@32M
    module /vmlinuz-2.6.18-238.9.1.el5xen ro root=/dev/lvm_raid/volroot rhgb quiet
    module /initrd-2.6.18-238.9.1.el5xen.img

after booting up the system the problem was still there
Quote:
If that dosen`t help you should check /etc/sysconfig/modules/ for dublicate entrys for raid456.ko. If there is remove one of them as shown here
i`v checked the /etc/sysconfig/modules/ and tried to remove is with the help of this URL u provided
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

Code:
        exec /sbin/modprobe uinput >/dev/null 2>&1
fi


hoever i`m not sure which mod should i add to the previous code to get it unloaded from the kernel ..
Code:
lsmod | grep -i raid
raid1                  56257  1 
dm_raid45              99529  0 
dm_message             36289  1 dm_raid45
dm_region_hash         46273  1 dm_raid45
dm_mem_cache           39489  1 dm_raid45
dm_log                 44993  3 dm_raid45,dm_region_hash,dm_mirror
dm_mod                101521  21 dm_multipath,dm_raid45,dm_snapshot,dm_zero,dm_mirror,dm_log
raid456               151137  1 
xor                    39377  1 raid456


thanks guys for concern ..


Last edited by Franklin52; 06-07-2011 at 11:02 AM.. Reason: Fixed code tags
# 6  
Old 06-08-2011
Hi,

According the bug report which I`ve posted earlier this is happening because mkinitrd is adding duplicate entries for the raid456 in case you have more than 1 raid. This is bug in mkinitrd. Those entries should be added to /etc/sysconfig/modules/ because there is where modules are listed in order to be loaded on boot. Since one module cannot be loaded twice(this is what the error is telling) you won`t see duplicate modules with lsmod/modprobe. You have to check the files in /etc/sysconfig/modules/ and find 2 identical one then do chmod -x on one of them. This is at least how I understand this bug.

p.s.

Could you run

Code:
mkinitrd -v -f /boot/initrd.$(uname -r).img $(uname -r)

And post the output
# 7  
Old 06-08-2011
well , here you go ..
Code:
mkinitrd -v -f /boot/initrd.$(uname -r).img $(uname -r)
Creating initramfs
Modulefile is /etc/modprobe.conf
Looking for deps of module ehci-hcd
Looking for deps of module ohci-hcd
Looking for deps of module uhci-hcd
Looking for deps of module ext3: jbd 
Looking for deps of module jbd
Found RAID component md1
Looking for deps of module raid5: xor raid456 
Looking for deps of module xor
Looking for deps of module raid456: xor 
Looking for driver for device sdb
Looking for deps of module pci:v00008086d00003B22sv00001028sd000002A6bc01sc06i01: scsi_mod libata ahci scsi_mod libata ahci 
Looking for deps of module scsi_mod
Looking for deps of module sd_mod: scsi_mod 
Looking for deps of module libata: scsi_mod 
Looking for deps of module ahci: scsi_mod libata 
Looking for driver for device sdd1
Looking for deps of module pci:v00008086d00003B22sv00001028sd000002A6bc01sc06i01: scsi_mod libata ahci scsi_mod libata ahci 
Looking for driver for device sdc1
Looking for deps of module pci:v00008086d00003B22sv00001028sd000002A6bc01sc06i01: scsi_mod libata ahci scsi_mod libata ahci 
Looking for driver for device sda2
Looking for deps of module pci:v00008086d00003B22sv00001028sd000002A6bc01sc06i01: scsi_mod libata ahci scsi_mod libata ahci 
Looking for deps of module ide-disk
Looking for deps of module dm-mod
Looking for deps of module dm-mirror: dm-mod dm-log 
Looking for deps of module dm-log: dm-mod 
Looking for deps of module dm-zero: dm-mod 
Looking for deps of module dm-snapshot: dm-mod 
Looking for deps of module dm-mem-cache
Looking for deps of module dm-region_hash: dm-mod dm-log 
Looking for deps of module dm-message
Looking for deps of module dm-raid45: dm-message dm-mod dm-mem-cache dm-log dm-region_hash 
Using modules:  /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/usb/host/ehci-hcd.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/usb/host/ohci-hcd.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/usb/host/uhci-hcd.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/fs/jbd/jbd.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/fs/ext3/ext3.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/xor.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/raid456.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/raid456.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/scsi/scsi_mod.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/scsi/sd_mod.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/ata/libata.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/ata/ahci.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-mod.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-log.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-mirror.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-zero.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-snapshot.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-mem-cache.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-region_hash.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-message.ko /lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-raid45.ko
/sbin/nash -> /tmp/initrd.nf4844/bin/nash
/sbin/insmod.static -> /tmp/initrd.nf4844/bin/insmod
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/usb/host/ehci-hcd.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/ehci-hcd.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/usb/host/ohci-hcd.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/ohci-hcd.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/usb/host/uhci-hcd.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/uhci-hcd.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/fs/jbd/jbd.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/jbd.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/fs/ext3/ext3.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/ext3.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/xor.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/xor.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/raid456.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/raid456.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/raid456.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/raid456.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/scsi/scsi_mod.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/scsi_mod.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/scsi/sd_mod.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/sd_mod.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/ata/libata.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/libata.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/ata/ahci.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/ahci.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-mod.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-mod.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-log.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-log.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-mirror.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-mirror.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-zero.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-zero.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-snapshot.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-snapshot.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-mem-cache.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-mem-cache.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-region_hash.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-region_hash.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-message.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-message.ko' [elf64-x86-64]
copy from `/lib/modules/2.6.18-238.9.1.el5xen/kernel/drivers/md/dm-raid45.ko' [elf64-x86-64] to `/tmp/initrd.nf4844/lib/dm-raid45.ko' [elf64-x86-64]
/sbin/lvm.static -> /tmp/initrd.nf4844/bin/lvm
/sbin/dmraid.static -> /tmp/initrd.nf4844/bin/dmraid
/sbin/kpartx.static -> /tmp/initrd.nf4844/bin/kpartx
Adding module ehci-hcd
Adding module ohci-hcd
Adding module uhci-hcd
Adding module jbd
Adding module ext3
Adding module xor
Adding module raid456
Adding module raid456
Adding module scsi_mod
Adding module sd_mod
Adding module libata
Adding module ahci
Adding module dm-mod
Adding module dm-log
Adding module dm-mirror
Adding module dm-zero
Adding module dm-snapshot
Adding module dm-mem-cache
Adding module dm-region_hash
Adding module dm-message
Adding module dm-raid45

my /etc/sysconfig/modules/ showing ...
Code:
cat /etc/sysconfig/modules/udev-stw.modules 
#!/bin/sh
MODULES="nvram floppy parport lp snd-powermac"
[ -f /etc/sysconfig/udev-stw ] && . /etc/sysconfig/udev-stw
for i in $MODULES ; do
        modprobe $i >/dev/null 2>&1
done

Quote:
You have to check the files in /etc/sysconfig/modules/ and find 2 identical one
nothing seen as shown above regarding raid456
, or did u mean something els .. ?
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Error inserting a clob file into DB table

Hi all, I am reading control file log from my server and putting it to a variable for j in $(cat $dirname/ctl_file.log) do if then Y=${#fileclob_ctl_file} if then fileclob_ctl_file=$j else fileclob_ctl_file="${fileclob_ctl_file},${j}" fi fi ... (5 Replies)
Discussion started by: Pratiksha Mehra
5 Replies

2. UNIX for Dummies Questions & Answers

insmod error: disagrees about version of symbol module_layout

When I try to insert a simple kernel module I get the following error > insmod: error inserting 'test.ko': -1 Invalid module format > in dmesg I see: disagrees about version of symbol module_layout I have following kernel which I downloaded using apt-get: uname -r 2.6.32-24-generic ... (0 Replies)
Discussion started by: rupeshkp728
0 Replies

3. UNIX for Dummies Questions & Answers

insmod: Invalid module format error

I have open suse kernel kernel 3.1.0-1.2-desktop on which I used kernel source 3.1.10-1.2 downloaded from kernel.org. The module gets built. While loading a kernel module I am getting Invalid module format error with description "first_driver: no symbol version for module_layout" The... (5 Replies)
Discussion started by: rupeshkp728
5 Replies

4. Shell Programming and Scripting

ORA-01756 Error while inserting a file in CLOB field

Hi, Please guide me where i am doing wrong, i am getting ORA-01756:quoted string not properly terminated when i am trying to insert file into CLOB cloumn of Oracle DB. Please find below the code where log file variable is myLogFile. Please let me know where i am doing wrong. ... (0 Replies)
Discussion started by: rajeshorpu
0 Replies

5. Red Hat

ls: /lib/libattr.so.1: no version information available (required by /lib/libacl.so.1)

Hello, I'm experimenting a problem on my rh server. Red Hat Enterprise Linux AS release 3 (Taroon Update 8) 2.4.21-47.ELsmp #1 SMP i686 i686 i386 GNU/Linux It started with a segmentation fault on #id root To resolve it, I've installed coreutils-4.5.3-28.4.i386.rpm But, I... (6 Replies)
Discussion started by: gogol_bordello
6 Replies

6. Shell Programming and Scripting

File exist checking error

Hi all, I have following code: export USERID=user export BATCHHOSTIP=190.113.3.324 remotePath=/home/user fileName=redbook.txt EXIST=`ssh $USERID@$BATCHHOSTIP 'if ; then echo 0; else echo 1 ; fi'` echo $EXIST II run the code from other server. The redbook.txt file is exist in... (1 Reply)
Discussion started by: suigion
1 Replies

7. Solaris

/usr/lib/snmp/snmpdx: can't open the file - Error Messages while rebooting

I have an X4500 server running solaris 10 and when I reboot my system it displays the following errors messages. Could someone help me with this ??? NOTICE: pci8086,1011 - e1000g : Adapter 100Mbps full duplex copper link is up. Nov 8 17:41:46 /usr/lib/snmp/snmpdx: can't open the file Nov 8... (2 Replies)
Discussion started by: bharu_sri
2 Replies

8. UNIX for Dummies Questions & Answers

insmod error - no such device

Hi Everyone, I am relatively new to Linux. After about three months of trying to compile a driver for a ESDCAN card, I finally found a version and kernel that worked. I am running Slackware V12.0 with kernel version 2.6.24.5-smp. When I use insmod to insert the driver file (esdcan-pci331.ko),... (1 Reply)
Discussion started by: Brian-UOIT
1 Replies

9. UNIX for Dummies Questions & Answers

If we need to add a .ko file to your kernel. What we do is use insmod every time you

If we need to add a .ko file to your kernel. What we do is use insmod every time you boot. But if we would like it to load at boot automatically, what would we do? (0 Replies)
Discussion started by: anupa
0 Replies

10. HP-UX

Error: file </tmp/srw25108193> does not exist

Hi Everybody I need help from you guys. I'm getting this message on PC where i'm running Unix User using Reflection in order to get graphically format for Oracle Report Server. What is causing this msg and how to solve it? Regards and thanks in advance. Gege *Error: file... (0 Replies)
Discussion started by: cgege
0 Replies
Login or Register to Ask a Question