Sponsored Content
Operating Systems Linux Red Hat insmod Error inserting `/lib/raid456.ko` -1 File Exist Post 302530022 by Saed on Sunday 12th of June 2011 08:40:54 AM
Old 06-12-2011
Hold it , i forgot to mention something here , after i add the code u provided , rebuilt the image .
although that the image is being created without adding duplicated modules ( should be workin at this point)
i made sure of my kernel Ver and /etc/grub.conf file , even reinstalled grub but still the same !
it shows the following :-
Code:
 uname -r
2.6.18-238.12.1.el5.centos.plusxen

Code:
at /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.12.1.el5.centos.plusxen)
    root (hd0,0)
    kernel /xen.gz-2.6.18-238.12.1.el5.centos.plus crashkernel=320M@32M
    module /vmlinuz-2.6.18-238.12.1.el5.centos.plusxen ro root=/dev/lvm_raid/volroot rhgb quiet
    module /initrd-2.6.18-238.12.1.el5.centos.plusxen.img

at boot time i cant see the exact kernel version , as it shows
CentOs ( 2.6.18-238.9.1.el5xen)
Centos ( 2.6.18-238-el5xen )
1) why it still showing the insmod Error inserting `/lib/raid456.ko` -1 File Exist if it didn`t add it twice
2) why cant i see my exact kernel version at boot

Regards
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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
GRUBBY(8)						      System Manager's Manual							 GRUBBY(8)

NAME
grubby - command line tool for configuring grub, lilo, and elilo SYNOPSIS
grubby [--add-kernel=kernel-path] [--args=args] [--bad-image-okay] [--boot-filesystem=bootfs] [--bootloader-probe] [--config-file path] [--copy-default] [--default-kernel] [--grub] [--info=kernel-path] [--initrd=initrd-path] [--lilo] [--make-default] [-o path] [--remove-kernel=kernel-path] [--set-default=kernel-path] [--title=entry-title] DESCRIPTION
grubby is a command line tool for updating and displaying information about the configuration files for the grub, lilo, elilo (ia64), and yaboot (powerpc) boot loaders. It is primarily designed to be used from scripts which install new kernels and need to find information about the current boot environment. On Intel x86 platforms, grub is the default bootloader and the configuration file is in /boot/grub/grub.conf. On Intel ia64 platforms, elilo mode is used and the default location for the configuration file is /boot/grub/grub.conf. On PowerPC platforms, yaboot parsing is used and the configuration file should be in /etc/yaboot.conf. There are a number of ways to specify the kernel used for --info, --remove-kernel, and --update-kernel. Specificying DEFAULT or ALL selects the default entry and all of the entries, respectively. If a comma separated list of numbers is given, the boot entries indexed by those numbers are selected. Finally, the title of a boot entry may be specified by using TITLE=title as the argument; all entries with that title are used. OPTIONS
--add-kernel=kernel-path Add a new boot entry for the kernel located at kernel-path. --args=kernel-args When a new kernel is added, this specifies the command line arguments which should be passed to the kernel by default (note they are merged with the arguments from the template if --copy-default is used). When --update-kernel is used, this specifies new arguments to add to the argument list. Multiple, space separated arguments may be used. If an argument already exists the new value replaces the old values. The root= kernel argument gets special handling if the configuration file has special handling for specifying the root filesystem (like lilo.conf does). --bad-image-okay When grubby is looking for a entry to use for something (such as a template or a default boot entry) it uses sanity checks, such as ensuring that the kernel exists in the filesystem, to make sure entries that obviously won't work aren't selected. This option over- rides that behavior, and is designed primarily for testing. --boot-filesystem=bootfs The grub boot loader expects file paths listed in it's configuration path to be relative to the top of the filesystem they are on, rather then relative to the current root filesystem. By default grubby searches the list of currently mounted filesystems to deter- mine this. If this option is given grubby acts as if the specified filesystem was the filesystem containing the kernel (this option is designed primarily for testing). --bootloader-probe grubby tries to determine if grub or lilo is currently installed. When one of those bootloaders is found the name of that bootloader is displayed on stdout. Both could be installed (on different devices), and grubby will print out the names of both bootloaders, one per line. The probe for grub requires a commented out boot directive grub.conf identical to the standard directive in the lilo configuration file. If this is not present grubby will assume grub is not installed (note that anaconda places this directive in grub.conf files it creates). This option is only available on ia32 platforms. --config-file=path Use path as the configuration file rather then the default. --copy-default grubby will copy as much information (such as kernel arguments and root device) as possible from the current default kernel. The kernel path and initrd path will never be copied. --default-kernel Display the full path to the current default kernel and exit. --elilo Use an elilo style configuration file. --grub Use a grub style configuration file instead of lilo style. This is the default on ia32 platforms. --info=kernel-path Display information on all boot entries which match kernel-path. I --initrd=initrd-path Use initrd-path as the path to an initial ram disk for a new kernel being added. --lilo Use a lilo style configuration file. --make-default Make the new kernel entry being added the default entry. --remove-args=kernel-args The arguments specified by kernel-args are removed from the kernels specified by --update-kernel. The root argument gets special handling for configuration files that support separate root filesystem configuration. --remove-kernel=kernel-path Removes all boot entries which match kernel-path. This may be used along with --add-kernel, in which case the new kernel being added will never be removed. --set-default=kernel-path The first entry which boots the specified kernel is made the default boot entry. --title=entry-title When a new kernel entry is added entry-title is used as the title (lilo label) for the entry. If entry-title is longer then maximum length allowed by the bootloader (15 for lilo, unlimited for grub and elilo) the title is shortened to a (unique) entry. --update-kernel=kernel-path The entries for kernels matching kernel-path are updated. Currently the only items that can be updated is the kernel argument list, which is modified via the --args and --remove-args options. --version Display the version of grubby being run and then exit immediately. --yaboot Use an yaboot style configuration file. BUGS
The command line syntax is more then a little baroque. This probably won't be fixed as grubby is only intended to be called from shell scripts which can get it right. SEE ALSO
grub(8), lilo(8), yaboot(8), mkinitrd(8) AUTHOR
Erik Troan <ewt@redhat.com> 4th Berkeley Distribution Thu Jun 21 2002 GRUBBY(8)
All times are GMT -4. The time now is 10:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy