FATAL: Error running install command for binfmt_0000

Thread Tools Search this Thread
Operating Systems Linux Red Hat FATAL: Error running install command for binfmt_0000
# 1  
Old 03-12-2014
FATAL: Error running install command for binfmt_0000


Firstly, I want to say hello to all of you guys. My first post here... I have issue with CentOS and I hope that there is someone who can help or even explain what could cause this kind of situation.
I have installed CentOS 5.7 x86_64 into Hyper-V (Windows Server 2012 R2) environment. After installation, I have installed LIS 3.4, configured CentOS and everything was working perfectly. Then, my system admin rebooted VM's and suddenly when CentOS was booting, I recieve error:

FATAL: Error running install command for binfmt_0000

There were no changes to Hyper-V environment (as admin said). Simply when I reboot CentOS, it lists kernel version and then display this error like million times...
Is there any way to repair this operating system because I have very important software running at CentOS? What could cause this kind of problem?

Kernel 2.6.18-274el5
Red Hat nash version


Last edited by gigolos; 03-12-2014 at 07:19 PM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. What is on Your Mind?

PHP Fatal Errors During SSL Cert Management - PHP Fatal error: xc_fcntl_mutex failed

Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup. However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies

2. AIX

I'm facing problem with rpm command, when running the command and appears this error:

exec(): 0509-036 Cannot load program /usr/opt/freeware/bin/rpm because of the following errors: 0509-022 Cannot load module /opt/freeware/lib/libintl.a(libintl.so.1). 0509-150 Dependent module /opt/freeware/lib/libiconv.a(shr4.o) could not be loaded. 0509-152 Member... (4 Replies)
Discussion started by: Ohmkar
4 Replies

3. Solaris

Install Apache 2.4.20 on Solaris 10 --- Error "ld: fatal: file ab.o: wrong ELF class: ELFCLASS32"

I am following the "Compilling and Installing" guide from Apache > HTTP Server > Documentation > Version 2.4 page The configure running OK: # export CC="gcc -m64" # ./configure \ --prefix=/usr/local/apache2/httpd-2.4.20 \ --with-port=80 \ --with-mpm=worker \ --enable-mods-shared=most \... (0 Replies)
Discussion started by: jhuang
0 Replies

4. UNIX for Dummies Questions & Answers

error while running nm command

I am running nm for a file. the command is nm -f libC.a but it gives below error nm: libC.a: 0654-203 Specify an XCOFF object module. any solution ? Please use and tags when posting code, data or logs etc. to preserve formatting and enhance readability, thanks. (2 Replies)
Discussion started by: yatrik007
2 Replies

5. AIX

Error running the history command

When I try to run the history command from the prompt i get the following error: $ history ksh: cd: 0403-011 The specified substitution is not valid for this command. ON running history with a parameter I get the following $ history -10 ksh: cd: 0403-008 The number of parameters... (6 Replies)
Discussion started by: meetzap
6 Replies

6. Shell Programming and Scripting

make Fatal error: Command failed for target 'exp_inter.o'

I am trying to install Expect 5.43 on my Solaris 10 x86 PC. When I run the make file I get - Command failed for target 'exp_inter.o'. I tried to find the file (find / -name exp_inter.o -print 2>/dev/null) but could not. Where can I get this file from? (2 Replies)
Discussion started by: pazzy
2 Replies

7. Solaris

Gani Network Driver Won't Install - make: Fatal error: Don't know how to make targ...

I attached a README file that I will refer to. I successfully completed everything in the README file until step 4. # pwd /gani/gani-2.4.4 # ls COPYING Makefile.macros gem.c Makefile Makefile.sparc_gcc gem.h Makefile.amd64_gcc ... (1 Reply)
Discussion started by: Bradj47
1 Replies

8. Solaris

Fatal error: Command failed for target `build_crypto'

Dear brothers. i tried so many times to install openssl-0.9.8g in x86 machine. i have done ./config without any error notification. when i execute the make command i am having the same error fatal error: Command failed for target `build_crypto'. i installed c compiler the verson of... (1 Reply)
Discussion started by: sayed_021
1 Replies

9. UNIX for Dummies Questions & Answers

Solaris 9: make: Fatal error:Command failed for target

Hi everyone first of all you should know that I've been working with solaris for a few days only. :) I need to install some programs and I have had the following troubles: 1. When I used /.configure it showed the following message: "no acceptable C compiler found in $PATH" I included... (2 Replies)
Discussion started by: eldiego
2 Replies

10. UNIX for Advanced & Expert Users

Error when running the make command

Hi, Not really sure whether this question should go to this forum but am giving it a shot. I have compiled a simple C program test.c. #include <stdio.h> #include <stdlib.h> #include <string.h> static int a; int test() { a=a+1; return a; } When I run a make command, I get this: ... (2 Replies)
Discussion started by: nattynatty
2 Replies
Login or Register to Ask a Question
MODPROBE.D(5)							    modprobe.d							     MODPROBE.D(5)

modprobe.d - Configuration directory for modprobe SYNOPSIS
/lib/modprobe.d/*.conf /etc/modprobe.d/*.conf /run/modprobe.d/*.conf DESCRIPTION
Because the modprobe command can add or remove more than one module, due to modules having dependencies, we need a method of specifying what options are to be used with those modules. All files underneath the /etc/modprobe.d directory which end with the .conf extension specify those options as required. They can also be used to create convenient aliases: alternate names for a module, or they can override the normal modprobe behavior altogether for those with special requirements (such as inserting more than one module). Note that module and alias names (like other module names) can have - or _ in them: both are interchangeable throughout all the module commands as underscore conversion happens automatically. The format of and files under modprobe.d is simple: one command per line, with blank lines and lines starting with '#' ignored (useful for adding comments). A '' at the end of a line causes it to continue on the next line, which makes the file a bit neater. COMMANDS
alias wildcard modulename This allows you to give alternate names for a module. For example: "alias my-mod really_long_modulename" means you can use "modprobe my-mod" instead of "modprobe really_long_modulename". You can also use shell-style wildcards, so "alias my-mod* really_long_modulename" means that "modprobe my-mod-something" has the same effect. You can't have aliases to other aliases (that way lies madness), but aliases can have options, which will be added to any other options. Note that modules can also contain their own aliases, which you can see using modinfo. These aliases are used as a last resort (ie. if there is no real module, install, remove, or alias command in the configuration). blacklist modulename Modules can contain their own aliases: usually these are aliases describing the devices they support, such as "pci:123...". These "internal" aliases can be overridden by normal "alias" keywords, but there are cases where two or more modules both support the same devices, or a module invalidly claims to support a device that it does not: the blacklist keyword indicates that all of that particular module's internal aliases are to be ignored. install modulename command... This command instructs modprobe to run your command instead of inserting the module in the kernel as normal. The command can be any shell command: this allows you to do any kind of complex processing you might wish. For example, if the module "fred" works better with the module "barney" already installed (but it doesn't depend on it, so modprobe won't automatically load it), you could say "install fred /sbin/modprobe barney; /sbin/modprobe --ignore-install fred", which would do what you wanted. Note the --ignore-install, which stops the second modprobe from running the same install command again. See also remove below. The long term future of this command as a solution to the problem of providing additional module dependencies is not assured and it is intended to replace this command with a warning about its eventual removal or deprecation at some point in a future release. Its use complicates the automated determination of module dependencies by distribution utilities, such as mkinitrd (because these now need to somehow interpret what the install commands might be doing. In a perfect world, modules would provide all dependency information without the use of this command and work is underway to implement soft dependency support within the Linux kernel. If you use the string "$CMDLINE_OPTS" in the command, it will be replaced by any options specified on the modprobe command line. This can be useful because users expect "modprobe fred opt=1" to pass the "opt=1" arg to the module, even if there's an install command in the configuration file. So our above example becomes "install fred /sbin/modprobe barney; /sbin/modprobe --ignore-install fred $CMDLINE_OPTS" options modulename option... This command allows you to add options to the module modulename (which might be an alias) every time it is inserted into the kernel: whether directly (using modprobe modulename) or because the module being inserted depends on this module. All options are added together: they can come from an option for the module itself, for an alias, and on the command line. remove modulename command... This is similar to the install command above, except it is invoked when "modprobe -r" is run. softdep modulename pre: modules... post: modules... The softdep command allows you to specify soft, or optional, module dependencies. modulename can be used without these optional modules installed, but usually with some features missing. For example, a driver for a storage HBA might require another module be loaded in order to use management features. pre-deps and post-deps modules are lists of names and/or aliases of other modules that modprobe will attempt to install (or remove) in order before and after the main module given in the modulename argument. Example: Assume "softdep c pre: a b post: d e" is provided in the configuration. Running "modprobe c" is now equivalent to "modprobe a b c d e" without the softdep. Flags such as --use-blacklist are applied to all the specified modules, while module parameters only apply to module c. Note: if there are install or remove commands with the same modulename argument, softdep takes precedence. COMPATIBILITY
A future version of kmod will come with a strong warning to avoid use of the install as explained above. This will happen once support for soft dependencies in the kernel is complete. That support will complement the existing softdep support within this utility by providing such dependencies directly within the modules. COPYRIGHT
This manual page originally Copyright 2004, Rusty Russell, IBM Corporation. Maintained by Jon Masters and others. SEE ALSO
modprobe(8), modules.dep(5) AUTHORS
Jon Masters <jcm@jonmasters.org> Developer Robby Workman <rworkman@slackware.com> Developer Lucas De Marchi <lucas.de.marchi@gmail.com> Developer kmod 01/28/2018 MODPROBE.D(5)